LexManos

You have a 1.7.2 mod in your 1.6.4 instance.. fix that.

Just because someone tells you no, does not mean they are being 'aggressive'.

Due to the nature of things such as Optifine and Shaders mod, it is tightly knit to your graphics card and computer hardware. So what works for your friend may not work for you as you have different hardware. Does the system work without ShadersMod? If so, then I would advise you go to the ShadersMod devs and ask them to help you figure it out. As the log tells us nothing.

There is always a log, it's in the developer console in the launcher. If it never shows you the launcher again.. guess what.. that's why you have 'visibility'option in the profile!

It's been out long enough there is no excuse for modders to not have updated. OMG you use a billion mods and your limited resources are taken up.. For shame! So... re-writing how the entire ID system and all related things work breaking all compatibility over the network, file saves, player data, etc... because you want more ids... NEVER ask for support with old systems, it's your choice to use old versions. We do not support nore endorse it. You.. want... a backporting... tool.. How exactly do you expect such a tool to work.... Seriously.... As for backporting in general, no, if you want new features/fixes/functionality UPDATE thats what updates are for. Not our problem if you don't feel like updating to another MC version. And then when vanilla tries to read said data, because it physically cant store the numbers you're talking about it either overflows, reads missaligned, throws a negative bound error, or whatever side effect of whatever system was in place. Yes, very.. Not to mention screwing over compatibility with anything else out there for minecraft. It would, but what happens to ID 5000 or 33000... Ya, no, if you want new features, fixes, tools, update to the latest version. If you want to use your old stuff that's fine, just have to work within the limitations of the system in place.

Because there are A LOT of them, and hooking into them is not free. It's rather expensive. HashMaps are slow, esp on strings.

You can, either use a ISpecialBlockRenderHandler or a TileEntityRenderer. 'Normal' blocks do not have any of that extra metadata so we can't pass it into them.

You don't need to be a 'coding ace' you just need to know the BASIC of programming in java. Sorry but you're not gunna get help here if you're not gunna try. {Also we're not here to teach you basic java, there are plenty of places to learn that on the net} As for MCreator, it's a shame that something like that exists, but you would have to talk to its author if you are running into any issue with it. And yes, we no longer allow editing of the vanilla .jar file, as there is NO reason to do it. Hell we don't even have to do it, so no mod should ever need to.

Set your JAVA_HOME correctly.

Thats actually defined by the Forge's Jenkins server. It holds the private information like username, sshkey, paths, and the like. And it's passed into gradle using an init script. But the basics of deploying to a maven repo are there. And remember, maven repo's are just flat file repos. All the metadata is in the files themselves. So whatever method you need to be able to write a file to the server gradle probably supports and would work with maven.

Its rahter difficult to do, and would cause issues. Something like that typically has to be built into the engine itself.You could probably simulate it on the client side by intercepting and canceling like 1/2 the entity tick events. But it'd probably cause sync issues with the server. I'd be interested in seeing if you find a solution that works without major issues.

1) 1.5.2 is old and no longer supported so we're not gunna help you there 2) No way in hell are we gunna help you with a fucking cracked launcher.... Are you dumb?

1) Just as a note we NEVER back port anything, once Forge has officially moved on to a new version of Minecraft the previous version is locked and will no longer receive updates. So asking for them is well.. stupid... 2) The ID management that you're speaking of is a Mod issue, not a Forge issue. We assign ids to free things. It's up to the mods to claim ids that have already been assigned to them before anyone else claims a 'free' one. Either way, this is all fixed in 1.7, so well, update. If its mods holding you back, drops the mods, or hound the authors to update. 1.7 has been out LONG enough for ANY modder to update just fine.

No, we do not backport things. Combined with the fact that we do not support 1.6.4, everyone should be modding for 1.7.2. We will not encourage/support those who develop for WAY outdated things.

One of your mods is not dedicated server compatible. Cant really tell by the log, but It may be the aeslibcore thing. But try removing mods to seewhich one it is.

1) we dont support 1.6 anymore, update 2) One of your mods is horribly broken, get rid of it.

Logs

You can, there is already a event for 'special' spawns such as determining child zombies or spider jockies. Just use that.

If you're using a mod pack its there responsibility to walk you through installing there pack. {Or have a installer or whatever they feel appropriate} We support Forge here. If you're JUST installing forge, then use the installer it's fairly simple. If you are running into issue, ALWAYS post you log files.

Update to 1.7.2. We no longer support 1.6-

Yes it did. You just dont get the source code in your project anymore.

There are ALWAYS logs. Do not post again without your logs or you will be banned and the thread closed.

Mods are sorted aplhabetically. Beyond that, you could do a coremod. But in reality, it's bad practice to edit other's classes, its better to go to the mod author and get fixes that way.

The Java class path is first found wins.