LexManos

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.

1) Classes start with upper case 2) You're not defining any extra states in your block.. go look at all the examples in vanilla minecraft it's straight forward.

They will run on whatever version you tell it to run on. Dev with 1.10.2. 1990 was having issues because it was a build that 1/2 dissapeared when we switched servers, everything should be fine now.

Update to atleast 1.9.4.

FPS always takes a hit when using redstone as it requires the entire chunk to be re-rendered, multiple times. Nothing in Forge causes any major drop tho. So you're gunna need to be more specific then 'omfg my fps goes down!'

1) Why do you have a bunch of arguments that screw things up? 2) Disable the loading screen as described in the EAQs.

You came here complaining that you had no idea what was going on when the error message clearly stated what the problem was. And tried to say it was our fault {by coming here} 10 seconds of debugging on your end would of saved us all a lot of time and hassle. You obviously didnt put in that effort. Which is why I mock you. Hopefully that'll make you put in a small amount of effort in before you bring it to others next time.

I know this is hard for you, but we have to go all the way back to first grade. The number 2, is LESS THEN the number 7. So you need to update!

This is NOT a Forge issue. Either A) you're installing things wrong. or B) The mods are broken. So for right now you should do a few things: 1) Make sure you're getting mods from legit sources (Protip: If the site is some shit like Minecraft#.com then its NOT LEGIT) In this endevor state EXACTLY WHERE you're getting your shit from 2) Make sure you're installing it correctly. I'm not sure how this is confusing its literally just put this file in the mods folder. 3) POST YOUR GOD DAMN LOGS AS REQUIRED BY THE EAQS AND BIG RED MESSAGE AT THE TOP OF THE FORUMS!

1) Why does your URL container {}? Thats not a valid url 2) Your json is broken. See the red errors when you view the page 3) You need to use the raw links.

No because they dont exist. The new launcher came out during 1.6, so we have only created the new jsons for 1.6+

FML will construct any @Mod it finds. It will also apply any @Instance it finds. If it finds a @Instance with no modid inside a class with a @Mod it will assume that it wants its own instance. Calling new ClassName() yourself creates a extra instance of your class that is never used because that field would be instantly replaced by FML to the instance that FML created.

you can call add trade multiple times stop trying to be 'smart' and making this complicated

This has nothing to do with arrays or anything. Just call addTrade as much as you want with every trade.

Its just how you import the project into your IDE. Either way these files are needed for your project to run correctly. As they are the libraries that Forge/Minecraft use. There is nothing wrong here, move along.

Gradle project vs normal i think....