LexManos

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....

1.8 is nowhere NEAR the latest version And you've failed to do what the big red text at the top of every page tells you to do and post your log. So, Locking this with the only advise you'll get: Update to 1.10.2

Proptip when doing language files, spaces in the key is not advised, it can mess with a lot of parsers. And just doesn't fit the standard programming practices. CamelCase: someNameHere Or Underscores: some_name_here

update to 1.10.2

this is the exact reason it was made, to allow you to serialize ANYTHING with a single interface instead of having to specialcase every type of item.

Speed, and compatibility. Beyond that you should update to be up to date. Bitching about old versions is not going to be supported here.

Actually for the most part, they are using it correctly they just dont have the replcements in place for some of them yet. You need to look for the alternatives, when it comes to Block it's MOSTLY IBlockState stuff.

Use the installer, and post logs. 1) There is no reason NOT to use the installer if your server designed in fucked up then fix the server. 2) There is ALWAYS a log, SOMETHING ALWAYS happens when you try running the server. But again, as stated we do not support 1.7.10. If you want support update your shit.

1.9.4, 1.10, and 1.10.2 all are 99.99% compatible with eachother so we have decided to force load the ones that state they are specfically for that version on the others. This is the power of reobfusicating to SRG names. I work hard to make this work. If you MUST keep your version to a specific version, then you can set your compatiblity to something that ISNT the default [MCVER] So, [MCVER,MCVER] would work to hardcode it to one version.

Yes, update the server.

First off, writing a Clojure adapter is a fun academic experiment but its not worth the effort to make a real mod in. Trying to do anything in the real world with it is inadvisable. And calling a system retarded because you have no idea what the hell you're doing is NOT a way to make friends. The EventBus in Forge is HIGHLY optimized in a way that lets us run whatever the hell we want without any performance impact of the rest of the system. At the end of the day, the Event bus is just an array of IEventListeners. Whatever the implementation of that IEventListener is we dont give a shit. If you want to do your static method crap you could easily just write a IEventListener that calls a static method. This shouldnt have to be explained as its obvious if you take 10 seconds to look at the system. But ya, have fun with your Clojure toy, i'd advise you drop it, or put in a modicum of effort before calling shit retarded. On top of that you're developing or 1.8.9, we're on 1.10, get with the times. That being said, you do bring up ONE good point, There is no technical reason we don't allow static methods as event handlers. It's mainly a legacy from when we originally moved from Guava's EventBus {Which doesnt support it} to our own. I've got a proof of concept edit already, only like 4 lines of code changed. I'll push it up if cpw cares enough about it.