LexManos

Its a crappy texturepack. Thats all we can say for now because you've provided us with EXACTLY NO USEFUL INFORMATION. Seriously we arnt freakin magician's we can't just TELL you whats wrong without any information. It works with vanilla models so it's something on YOUR end that's broken most likely.

1) Wrong Section 2) Update your MC version 3) WRONG SECTION -.-

Coremods are on their own there is nothing we can do to make them work on our end it's purely up to the modders. They are retarded enough to think they NEED a coremod they can fix it themselves.

I'll send it to AdFocus and figure out wtf is up. Thanks.

You don't people adding things to the main menu is bad practice. It causes nothing but spam. Beyond that, you should update to 1.10.2.

Just post a link with a NSFW warning, I can remove it if its an issue. Beyond that, as stated we try and make the ads non-pornographic but ads are ads they sometimes change shit after they have been approved. It's a matter of cat/mouse.

Core mods are a very specific thing in the MC world. You will not get help making a Core mod here. Because editing vanilla classes is BAD and you shouldn't use it. If you are making a Library, or a 'base' version of your mod DO NOT call it a 'Core' mod. Beyond that there is no real reason to split the two into two physical parts. Just have a config option to enable/disable certian parts.

You set the max ram to 1G in the command line, -Xmx=1G You set the 'new object' memory to 5G: -Xmn5G You want to just use the -Xmx argument, not the mn.

Quit abusing the stairs glitch. We've gone over this a million times. Because i'm sick of these 'issues' I've added a config option you can set it in the Forge client config screen. https://github.com/MinecraftForge/MinecraftForge/commit/0f6b16cada5d77e094aa2eedbe2a556b76656997#diff-104a6609a5f1507a6105cb0f12e00921R109

Well, that was a nice debugging session going down the rabbit hole that is Vanilla doors. It's a miracle that they even work in vanilla minecraft as it is. Either way I've fixed it and potentially other block issues: https://github.com/MinecraftForge/MinecraftForge/commit/4694152124e7f72ec0d8482176d3faa6c13be30c

Thats why he asked for screenshots because if what you're saying IS true then it'll work. So give the screenshots.

You don't. 1) 1.7.10 modding is dead, move on 2) You NEVER trust the client.

You have a crappy intel graphics card that is not compatible with modern graphics. Disable the loading screen in config/splash.properties

Hypotheticals are not real issues. Come back with an actual stack trace. I can see what you're trying to say however The ifs themselves should never actually be needed as nothing in the MC codebase should be that shallow.

The current version of Minecraft. Typically it is also custom for us to give leniency for the previous version of Minecraft as well as we fully understand that sometimes mods take a while to update. However you're asking for support on a version that is TWO YEARS out of date. There is no more development for it on Forge's end. There is NO reason modders should be developing for it. If you as a user decide to use it that's great. But don't expect us to help you with it. It's a stupid analogy but it's apt. It's like calling up Microsoft and asking for them to fix your windows XP install. Its not a hard concept, stop being a pain. So TLDR: If you use 1.10.2: Feel free to ask questions here If you don't: Fix your own shit.

Stop getting pissy. It's not supported mean we won't help you. It doesn't mean we're forcing you to stop doing whatever you want to do. Just don't bitch to us when it doesn't work. To keep our sanity and make our limited resources support wise work we only give help to those using the latest version. There is no logical reason we should be forced to help you use old stuff that is outdated.

Dev Time: Re-run 'eclipse' task, or whatever your IDE task is to update the classpath Run Time: Shade the dep in as stated above.

Then you don't have any updates for your mods. Congrats you're up to date!

Using example code from the MC code base is MOST LIKELY a bad idea because it's a decompiled code which is inherantly ugly as shit as compiling is a lossy process. It's better to tech them ideas then to give them code. Exaplain what a function does in a class and any competant programmer will know how to call a function. We are not writing tutorials for people who don't know basic java syntax and the basics of programming.

The wiki has been crap so we've officially switched to the RTDs through github. So start sending PRs to it. As for 'general site designs' to make it cleaner to understand or whatever go through and SPECIFICALLY request things and ping our new web admin, Flamegoat in it. {Not sure if pings work on this sit, but find a way to poke him, or we should make a 'website support/suggestions' sub-forum} As for tutorials, copy pasta is bad so its NOT ACCEPTED in the RTDs. Describe the issue/problem and solution DO NOT GIVE CODE. You want to teach not do it for them. As for tutorials for old versions, you should ALWAYS promote using the latest version of MC. However 90% of Minecraft stays the same between each version. So if you write it as descriptions and not copy/paste code then the tutorials will be fine between versions. Only needing smaller edits to point people at new/changed features in the new versions.

http://wiki.vg/NBT#Examples Directly under the defintion of the hello world example is "Here is the example explained" ..... You should start reading things in hex when working with binary files much more standard way of showing things. That '0 and 11' is not a '0 and 11' it's 0x000B, It's a WORD (2 bytes, 16-bit integer) when when converted to decimal comes out to be 11. Which tells you the length of the next string "hello world" Count it, you'll see its true. Same goes for anywhere else in the spec that states that it's a word.

Nothing in FOrge changed that would cause anything like this from 1.10.0 to 1.10.2 Thats all vanilla changes. The mods on the other hand could have a lot thats changed inside them. My Forge load times are about 15 seconds so it's not reproduceable on my end. You are gunna need to give more details. And/Or try tracking it down to a SPECIFIC build yourself.

Try removing Chisel and reporting it to the authors, Something in their worl gen is causing MC to recursivly loop.

provide your world. claimimg things without evidence is just annoying -.-

There is nothing in Forge that would cause 'ping lag' And that's is a extremely vague term. Beyond that, update to 1.10.2 and supply logs if you want help here.