LexManos

Stop being an ass, Warning issued.

We provide both the ad, and direct links for a reason.

Still working out the kinks in the installer for optional mods. For now just delete mods/mod_list.txt and you'll be good. The issue is he ran both 1.10.2 and 1.11 installers.

Entity Registration has changed A LOT in 1.11. I am currently trying to decide how to best address it in Forge.

Err miscounted 2130 it should be up in a few mins, jenkins is being slow.

Right, Abrar filtered out ALL pngs from the installer.... need to work around that. 2139 should fix it.

Update to 1.10.2.

What? Perhaps provide more detail.. like ANYTHING as your post is useless. Post your logs, and perhaps a screen shot. So we can figure out what you're talking about.

This weekend I finialized the 1.11-pre MCP update, and cpw did the Forge update for it. Yesterday I finished the 1.11 release MCP update, bspkrs pushed my work out today. And Jenkins is now running. So ya, this is PRELIMINARY UPDATE. But the more people test and more bugs are reported the faster we get a Recommended Build out.

One of the main goals of this is to determine what Java versions are used by players. This will allow us to better determine what versions we should care about supporting. If, for example, after we get a bit of data and we see like <1% is using Java 6, Forge will probably drop support for Java 6 reguardless of what Mojang does. Gracefully with a 'update your java here, or downgrade Forge' message but none the less. It will help us figure out what is best to move forward with. Right now, the stats are extremely biased, as Mercurius is only in some FTB packs, and a couple personal packs. Most of which have other mods that force Java 8. We are working twards getting this packaged/installed with the normal Forge installer so that we can get the best dataset we can. And I just want to reiterate that user privacy is of UPMOST importance to us in this project and we have taken great care to make sure no personally identifiable information is sent anywhere. As well as giving you all of the options we can to allow you to control either you even report things or not.

Then you haven't been paying attention, 1/2 the tech support issues that aren't mc version mismatches are missing library/dep issues. Not to mention the cluster that is IRC/Forums. There is no reason for a modder to make it hard on the end user. It's super simple to do. https://github.com/johnrengelman/shadow

Or, you could just add a config option to disable the features they dont wont. But this isn't what you asked, you asked to make a LIBRARY a library is not end user facing content, that is a mod. Say you wrote a utility that made interacting with a text file easier for you. That's great, use it in all the mods you want. But to the end user your mod should still just be one file. Having to download 5 different 'libraries' to install one mod is really annoying. This is where shading/fatjaring comes in. You can build that library internally. You could develop with those 5 libraries and when you build you jar have gradle pack them all together and change their package to 'my.special.mods.libraries.{original package}' and those classes would exist and work and you wouldn't have to worry about two mods having two different versions of the library because each mod would have its own copy and use its own copy.

There should be no major lag unless you have something constantly loading and unloading the nether. Such as large machines like this or people running around the nether. Atleast thats what the problem sounds like. Upload your world and I can take a look. You say this world works fine in vanilla but its purely JUST forge that's the issue, NO other mods?

You can build a library, in this case its recommended you shade the library into the final jar to make it easiest on the end user to install it. Trying to split a project into multiple jars would just be annoying to setup. And annoying for the end user.

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.