LexManos

What launcher are you using?

You're not initalizing the items whenever you want, you're doing it whenever the class is referenced. Which could be in placed you have no idea. Such as when other mods re running and then FML is like "Where the hell are these items coming from!?" And it screws up the registry and things go to hell... Its also a level of indirection magic that makes your code harder to understand. Technically YES you could write things like this, but you shouldn't as it has a lot of downfalls.

Creating items in static constructors is typically a bad thing to do. Just setup your items normally in your init methods.

Developing for 1.7.10 is not supported. Update. Beyond this 'expanding data types' is a rats nest that isn't worth going down. Looking at your old posts, there is no reason you need to expand biome ids. There are only ever 256 possible biomes per chunk. Fits perfectly in a byte.

Commands shouldn't be localized. They should return text components that are localized automatically on the client side. Hence why the server side I18N is deprecated.

Hey folks!!!! Great news. The contest was a hit and we've turned out some amazing new designs and logos. From everyone on the Forge team I want to say thanks for participating and giving us some awesome things to work with. With that said though you all aren't reading this to see me say thanks so lets get down to the important stuff, like you know, who the hell won. So without further distraction I present you our winner: By: PitchBright Now with every new thing something old must pass. So with that I'm also happy to announce that here is the next while we will also be updating the forums, website, and a few other things, to match our new branding. Thanks again to everyone who submitted entries to the contest. Cheers TheTrotter

Oh dear god, start removing all those coremods.

Read the comments. Deprecated methods happen all the time.

No there isnt.

And I dont know who you think you are to call a mod shit and say it should never be released or encouraged... The idea of modding is allowing people to work creativly on whatever they want to do.... I am LexManos, the lead developer of the most popular modding api for the Minecraft environment. I have over 4 years of experience working with Minecraft mods and the community. As well as over 20 years of development and modding experience in non-Minecraft realms. THAT is who I am. The ability for mods to kill the client SILENTLY was removed because people like YOU abused it for egotistical and petty reasons which harmed the end user and purposefully sent users to the wrong place for the cause. I have NOT removed any functionality. I have NOT hindered any mod in any way. You can still stop the process of you wish. I simply force the log to capture the correct cause so that the end user, and us here doing support, know how to handle it.

Note: For runtime compatiblity with the most users, you should STILL have Java6 as your target. Most of the J7 features can be compiled to J6 specs.

Either way we dont support hiding the cause. So you're out of luck, however just make your information as clear as possible as it will be printed directly above the trace.

This is the exact reason we added the security manager, so that people CAN'T exit minecraft "without extra log lines" If minecraft closes, you NEED to know why. And if any mod is trying to HIDE from explaining why then that is a shit mod and should never be release/encouraged. We don't prevent the stop functionality, we just add a stacktrace so you know WHO stopped it. Just use the systems in place.

That's already a thing. Biomes can specify what 'flowers' they want to have in their biome for bonemealing so if its not how you like it, either write a mod, or ask the mod author nicely to increase the ratios.

Also, DO NOT run fundemental aspects of your code based off string comparisons of registry names. Seriously... Set a field for the opaquenss and use that...

There is no support here for 1.7.10. Update.

We do not support 1.7.10 here any more, update to 1.10+

We load both

The client side doesnt care about your custom constructor. It just gets told you have a entity on the server so it creates a new one using the World constructor. And then makes it read from NBT. So As stated, there is no real reason to use custom constructors for entities, make sure your data is stored and sent to the client.

1) Stop using 1.7.10 2) Stop using coremods.

Start by removing these files and yelling at their authors for being morons.

Do not use either CCC or NEI. They are coremods and have been replaced by better mods that do not screw with the internal code of Forge/Minecraft. Go get JEI.

.... what? You can't just run two different versions of minecraft in the same game.... how do you expect that to work?

This was a temporary bug with our cleanup of a vanilla registry issue. This has been fixed for a while. Provide logs and make sure you're on the latest version.

Stop using 1.7.10.