LexManos

Logs

'freezing' is never easy to diagnose, but, no it typically isnt caused by Forge. There is not much I can recommend beyond sitting down and going through your mods one by one to see which ones causes the freezing. Play the game, when you see freezing, take a mod out, if you play past where it would normally freeze for a while add the last mod back in. And see if you can track it down to a single mod, or multiple mods that is causing it.

Casing is always an issue, paths are not lcased anywhere, The main issue is that windows users dont understand that paths should be case sensitive, because they are not in the windows folder structure.

What can you do to not screw things up? DONT reference items or blocks by ID, ONLY reference them by object. There are new static functions that are basically Block.getByID(int)/Block.getID(Block), and the Item equivelents, DONT use those functions. And yes, the 4096 block limit is still in effect, You can only have 4096 blocks loaded at once time.

Thats the thing, we dont KNOW the full path attempted, as thats all hidden behind resource packs. And any resource pack could hold the information. People just need to know there resource pack structure.

Alright guys, yes we know that 1.7 is out, but where is Forge..? Well, If you do not know, Forge is built off the work the people over at Minecraft Coder Pack (MCP) do. They deobfusicate Minecraft from the randomly changing 'so.f' names to the reasonable 'Block.field_1234_f' names which allows us to have a more stable code base for us to work against. This is also the data that allows us to do the run time deobfusication which allows for mods to potentially work across Minecraft versions {Prime example 1.6.2->1.6.4}. However, due to the large amounts of changes inside Minecraft at a code/strucutre level this update will take a bit more time. The Mojang blog likes to boast "more than half a million lines of code changed over 1,104 commits". So you can kind of see where the trouble comes in... While that is going on, I am working with AbrarSyed {Forge Essentials} on creating a new, more streamlined build process for the end modders that will allow them more control over how things work and fix a lot of the issues that we are having on certian modder's systems with the current python scripts we use. You can check out that progress over at the ForgeGradle github. Combine that with the fact that quite a few of us in the Modding community are getting ready for Minecon next week and have real life, it'll take a little bit. However I assure you that we are working on it as best we can. As always you can keep an eye on our progress on our Github. Also, if anyone out there knows there stuff when it comes to gradle, help for AbrarSyed would be greatly appreciated. Feel free to comment here if you would like to help. As it sits however, 1.7 will be a rather large update for quite a lot of mods. As I said before, Minecraft has changed a lot. Which means Mods themselves will take a while to update. We are trying to get Forge out as soon as we can for mods to start, but don't expect any major mods to be updated until possibly December. You can however, still play older versions of Minecraft all you want. Many mod packs are still out there ready to be used! So fear not your enjoyment will continue!

Log out of the forums, we're looking into it but PHP seems to be borking up.

The 1.7 update for Forge itself is waiting for MCP to update. Which will take some time due to the massive internal changes to Minecraft. While that is happening, We are re-writing the entire build process to try and speed it up, and structure it better to Gradle: https://github.com/MinecraftForge/ForgeGradle Aside from that, mod will take a while to update, so there is no rush. Just stay tuned and you can see what we're doing.

1) IDs are going away 2) We already have that in place, modders dont use it.

Your mod pack is broken, it's missing require libraries, tell the mod pack author.

If you use the Forge installer, it will show up as a 'version' Just select it.

it's trying to run the javac --version command, by java I ment the jdk, sorry.

Try without any mods and post a full log.

Don't use MagicLauncher, just use the normal MC launcher and Forge's Installer.

Typically these errors are caused by users with non-latin characters in the name. This one is caused by you not having java in your PATH.

Mods will change yes, but that happens at every update. It is a biig change, but mods will adapt, and those that don't will die. Nothing to different.

https://github.com/MinecraftForge/Installer

No, Forge doesn't have a standard naming policy, aside from the things that we name. It is up to the modders to agree on the naming policy themselves. I understand the debate as it sits, however, this is purely a debate between modders, Especially in the manor that GT has decided to go. The wiki is created by the communitty not us. But ya, the answer is no, unless I get a large group of modders who aproach me with a actual standard they ALL have agreed on. When it comes to the oredict, either you use the names that other people use, or your shit wont be found.

Don't use glow it makes you look stupid. Anyways you run the jar just like you runa ny other jar, by doing 'java -jar {jarname}.jar' And give us the logs.

Poked overmind about it, his theory was it had soimething to do with sessions derping up. Try logging out of the forums and then going to the wiki. We are looking into switch forum software as this one is eating the server alive.

Add more ram when you run it from the command line.

And the installer prints NOTHING to the console while it runs? Seems odd considering I made it print shit... But anyways, I'll leave this to a MagicLauncher bug. Our installer downloads needed files and if that fails the launcher should garentee the files exist.

run it without any options. extract will extract it, downloading nothing. help *should* show the help but meh But ya just run it without any options and click 'install client'

Interesting those logs make it appear that the installer is not downloading the launcher wrapper, and lzma libraries. Which it should be and does on our end. Try running the installer from the command line and see if it spits anything out. Either way, Magic launcher should add download support Verify that the libraries are there.

minecraft_server is the vanilla minecraft server jar and will not load mods without editing minecraftforge_universal is the jar containing all of our edits and running it will run minecraft_server, but with our changes. The tutorials you've been watching are old, they have merged the two jars manually, this is a bad thing to do and you shouldn't be doing it.