LexManos

It is not slander to correct you when you are wrong. Just because you can't accept the corrections and fly off the handle is no reason to report the thread for slander. Either way I will lock this thread move on with your life.

Get rid of any coremods you have in your setup they are broken.

Do not create coremods.

1) Stop installing/using coremods 2) You installed a old version of Baubles, not the 1.10.2 version.

Select the version you want in the launcher profile. Select the profile -> Edit Profile -> Version

I know what I'm doing, and why i'm doing it. You guys shoulnt use it no. Its how I felt like designing my code. If you don't want to do it nothing is forcing you to. Its meant to be a reference of what to register in each event not HOW to register it. No, you can do it however you want this is just a answer of how to use these events and a few examples of other registry related Forge features. You can layout your code and do it however you want. Just register the right things at the right events.

https://github.com/LexManos/VoidUtils/blob/master/src/main/java/net/minecraftforge/lex/voidutils/VoidUtils.java Simple example of how to do it right.

1) Don't make coremods 2) Don't mod for 1.7.10 anymore, seriously, update 3) Don't make 1.7.10 coremods -.-

You're decompiling the minecraft code incorrectly, what JVM setup are you using?

Limiting your usage of a finite global resource pool is always a good idea. You don't have to go overboard and make things super complex but if you have 20 different things that are functionally the same but with different textures, then why not use 1 item.

Logs.

Or, what you COULD do is just remove the update tick from the world's list and do nothing with it. Like I did and it works fine.

The answer is you can't. Vanilla doesnt have this feature you'd have to write a mod to add it.

/** * Register the mod entity type with FML * This will also register a spawn egg. * @param entityClass The entity class * @param entityName A unique name for the entity * @param id A mod specific ID for the entity * @param mod The mod * @param trackingRange The range at which MC will send tracking updates * @param updateFrequency The frequency of tracking updates * @param sendsVelocityUpdates Whether to send velocity information packets as well * @param eggPrimary Primary egg color * @param eggSecondary Secondary egg color */ public static void registerModEntity(Class<? extends Entity> entityClass, String entityName, int id, Object mod, int trackingRange, int updateFrequency, boolean sendsVelocityUpdates, int eggPrimary, int eggSecondary) { instance().doModEntityRegistration(entityClass, entityName, id, mod, trackingRange, updateFrequency, sendsVelocityUpdates); EntityRegistry.registerEgg(entityClass, eggPrimary, eggSecondary); } Reading helps... Its straight forward. Also UPDATE to 1.10!

Yes, but you're doing it wrong. Stop using Global IDs. As for the eggs, There are extra parameters for registering a mod entity with a egg. We do it in a generic way without having to us Global IDs by using the entity name.

Do NOT use global IDs, this is PURELY a legacy ModLoader compatibility function. And update to 1.10+

If you do custom models you could probably get away with doing it during the Register<Item> event. Or the ModelRegistryEvent's As I said, the model reigstry isnt a normal registry do it doesnt get its own event, but you could bundle it together with Item. As thats where you're creating your item. Or if you want, do it in init, it really doesnt matter as long as its after the Register event. @Draco, It was publicized when created, it was announced on twitter, it even had a page in our docs, don't get all snippy because you didn't see it.

No. We specifically added the 'RegistryEvent.Register<Type>' events to clean up this confusion. Create and register your items/blocks in THIS EVENT ONLY. The ModelRegistryEvent is for registering Models as they are not standard FML controlled registries.

1GB is not enough for Pixelmon. And this what he describes is cpu/gc lag. So more ram might help.

Those are the logs, or atleast a form of them from the installer. He needs to grant access to the internet for his installer.

Telling people to update their OS is not a valid solution here on the forums, Most people here wouldn't know how to do it. And could harm their computers if they tried. Just tell them to disable the loading screen like the EAQ's say -.-

The tool works fine, you dont need to build it yourself you can find it here: http://files.minecraftforge.net/maven/net/minecraftforge/remapper You should just be able to point to your project directory, IT DOES need gradlew.bat to be there. And then it should detect a few things and let you select the update that you want. This isnt the magic bullet tho, it wont do a 1.8.0->1.10.2 update for you as it wont do renames. But you can use it to convert to SRG names and remap after the update. Or if someone has gone in and made a custom SRG for the updates you could use that.

Yes, but you have to use the internal config object that is created by the manager. The GUI is part that I haven't gotten around to doing quite yet. Using the GUI system is really easy it just needs to be glued together. https://github.com/MinecraftForge/Mercurius/blob/master/1.9.4/src/main/java/net/minecraftforge/mercurius/binding/ModConfigGui.java#L40 being the example of how to use it in this style setup.

java.lang.UnsupportedClassVersionError: invtweaks/forge/asm/FMLPlugin : Unsupported major.minor version 52.0 You should go yell at InvTweaks to atleast throw a useful error. You need java 8.

Just a note, this is my test suit for this. Not the best but shows all the different data types and sub-categories: https://gist.github.com/LexManos/ca57c1f29365bf492f207e4aa1a7865c