So i was able to setup my BlazeLoader environment. Now I get about 10000 build errors, most caused by method duplicates. Did I something wrong or is this normal. And it always says when I run any of the mcp batchs that scalac was not found
Please Help!
I might know what caused that, did you overwrite the vanilla sources with the blazeloader ones or add BlazeLoader as a resource? Also the missing sclac is fine, unless you happen to be writing your mods in scala
This project looks good. I wish the best of luck, and your doing even better by making this compatible with as many mods as possible (or Forge).
Yeah BlazeLoader itself does not modify too many base classes (and several are rarely used), and even those are loaded without actually modding the jar. The forge compatibility should make this usable for a much larger player base.
Awesome!!! *Opens up the installer project* EDIT: Did you change the forge transformed MC classes and added the methods needed by BL to them? or how did you do it?
There are two parts to this:
In the IDE:
I created two run scripts, one for vanilla and one for forge.
I created two Minecraft modules, one with forge and one without forge.
I created two BL modules, one for vanilla (depending on vanilla module) and one for forge (depending on forge module). Both depend on the BL core module, which depends on the BL vanilla (which must remain partially signature-compatible with the forge version, not a big deal).
In the game:
The TweakLauncher uses Version.isForgeInstalled() to determine weather to load classes from /bl_vanilla_classes or /bl_forge_classes. They contain the obfuscated classes for their respective minecraft version.
Forge is loaded on top of BL by adding "--secondaryTweaks cpw.mods.fml.common.launcher.FMLTweaker" to the launch string. By default forge uses "--tweakClass cpw.mods.fml.common.launcher.FMLTweaker", but blazeloader took that slot so forge has to use the secondary tweaker.
I'll try it when I get home and I hope I will figure it out . Btw nice new signature icon! Can I put it in the installer gui?
Sure! Also if you come up with a better one feel free to post it! I just made this one real quick for my signature and FML's mod list. Now BL looks better, considering it is in a list with Forge, FML, and MCP.
I was maybe going to make some when BL is stable but I've never done youtube before. So I would say (and I think @acomputerdog will agree with me) go ahead and make sure to post them on the reddit.
Ok I will get back to you when I upload them... I am just glad I can somehow contribute to this amazing project.
Also I have a twitter @SeamusFD so I will post it there too
I decided toy around with BlazeLoader, but I don't have these files mentioned in the Reddit installation instructions:
Open your .minecraft, go to libraries, and copy the contents of the folders "org/ow2/asm/" and "net/minecraft/launchwrapper/1.9", keeping the entire directory structure, to the folder<MCP_ROOT>/jars/libraries.
After some tinkering around, long story short, I can get "asm-all-4.1.jar" by downloading MC 1.5.2 resources, and I only get "launchwrapper-1.5.jar". Any newer version doesn't even generate the folders for those files. I found the url for "asm-debug-all-4.1.jar" in your "libraries.json" file and can download that. Any ideas on how I can get "launchwrapper-1.9.jar"? Or better yet, both the normal way through the Minecraft client.
Sure! Also if you come up with a better one feel free to post it! I just made this one real quick for my signature and FML's mod list. Now BL looks better, considering it is in a list with Forge, FML, and MCP.
How would I add the blaze loader banner to my signature! BTW it is super awesome looking.
You made that?! I always thought coders could do fancy stuff *looks at himself* EDIT: So with the new Forge compatibility would you be able to make blocks and make them compatible with Forge Mulitpart??
I have not used multipart, but it should be possible.
I was maybe going to make some when BL is stable but I've never done youtube before. So I would say (and I think @acomputerdog will agree with me) go ahead and make sure to post them on the reddit.
And also add them to the wiki in the same location!
I decided toy around with BlazeLoader, but I don't have these files mentioned in the Reddit installation instructions:
Open your .minecraft, go to libraries, and copy the contents of the folders "org/ow2/asm/" and "net/minecraft/launchwrapper/1.9", keeping the entire directory structure, to the folder/jars/libraries.
After some tinkering around, long story short, I can get "asm-all-4.1.jar" by downloading MC 1.5.2 resources, and I only get "launchwrapper-1.5.jar". Any newer version doesn't even generate the folders for those files. I found the url for "asm-debug-all-4.1.jar" in your "libraries.json" file and can download that. Any ideas on how I can get "launchwrapper-1.9.jar"? Or better yet, both the normal way through the Minecraft client. Thanks.
You can install and run the newest version of forge to get them. If it installs launchwrapper 1.8 for some reason then just rename it.
Ha, that's annoying and weird because we haven't had any snow at all yet. btw I can take a look on the thread when you are having power problems!
Maybe we should just change our version back to 1.8, there is almost no difference and then there don't have to be to versions of the wrapper on a client installation with Forge and BL
No problem! and it looks really awesome!
Sweet power is back on!
I switched to 1.9 because forge briefly did, but apparently they switched back.
I might know what caused that, did you overwrite the vanilla sources with the blazeloader ones or add BlazeLoader as a resource? Also the missing sclac is fine, unless you happen to be writing your mods in scala
It should have extracted it. Did it give any errors? (or did your antivirus stop the extractor?)
I just finished the merge, so far everything is working fine and BL even shows up in FML's mod list!Forge compatible version is now on github!
Yeah BlazeLoader itself does not modify too many base classes (and several are rarely used), and even those are loaded without actually modding the jar. The forge compatibility should make this usable for a much larger player base.
There are two parts to this:
In the IDE:
That is it, except BLCore also depends on BLVanilla and vanilla.
Yes, but all the lines should be two-way except for the ones connecting BLCore to BLForge and Vanilla
Dependencies:
Vanila:
This I AMAZING... Great job guys
This is the basic checklist for a full release:
Sure! Also if you come up with a better one feel free to post it! I just made this one real quick for my signature and FML's mod list. Now BL looks better, considering it is in a list with Forge, FML, and MCP.
If not then I would like to volunteer to make some.
Ok I will get back to you when I upload them... I am just glad I can somehow contribute to this amazing project.
Also I have a twitter @SeamusFD so I will post it there too
After some tinkering around, long story short, I can get "asm-all-4.1.jar" by downloading MC 1.5.2 resources, and I only get "launchwrapper-1.5.jar". Any newer version doesn't even generate the folders for those files. I found the url for "asm-debug-all-4.1.jar" in your "libraries.json" file and can download that. Any ideas on how I can get "launchwrapper-1.9.jar"? Or better yet, both the normal way through the Minecraft client.
Thanks.
How would I add the blaze loader banner to my signature! BTW it is super awesome looking.
I have not used multipart, but it should be possible.
Not yet, but that would be great!
And also add them to the wiki in the same location!
Thanks!
You can install and run the newest version of forge to get them. If it installs launchwrapper 1.8 for some reason then just rename it.
Ok thanks
P.S Ohhhh yeah now I look awesome lol
Sweet power is back on!
I switched to 1.9 because forge briefly did, but apparently they switched back.
I don't think 1.9 is being distributed with Minecraft 1.7.2 right now. I've been using launchwrapper 1.8.