Draco18s

You also shouldn't be sending the packet yourself.

I don't think anyone uses 1.5.x anymore. 1.6.x is going to be very rare (and there is a gradle version).

Yup, case matters when compiled. Windows doesn't give a shit.

By the way, sending the json file is perfectly acceptable: it had already been serialized and you've already got the code that deserializes it and stores it in a map. Why the conversion to a separate serialized data type?

You CAN still work with old versions, but the download url has changed and the build scripts for all those versions was not updated. A little research cam uncover the new url, and you can insert it into the old build config file (I forget where) and it will work. But again, why?

I don't think that auth server would even have a clue as to whether the person is currently online or not, much less which server they are on.

That's the one. I haven't migrated to 1.8 yet, but I have heard about the method.

The item "moves" every tick because when you modify the stackTagCompound Minecraft sees it as being a new item stack, not the same item stack. I believe there is a method in the Item class called shouldRefresh or similar. You'll need to override that to return false.

Also do this for me: (This is my own resources, I'm interested in seeing yours, open up just enough to show me the compostbin.png)

Go look at the nametag code.

Code?

A texture with a circle drawn on it and rendered so that it always faces the player doesn't require much know how, just a little trig

getInteger(...) is a convenience method wrapped around getProperty(...).getInt()

No, it wouldn't, it just isn't a thing you should be doing.

1) show your render class 2) don't use registerGlobalEntityID

config.set (property) Use your IDE

Or more specifically, you need to wrap the GL11 calls around the render function for the part.

Ah. Well. As long as it is being used correctly.

No.

mo, your RenderTroop constructor.

That's the one. It isn't called "sand" anymore because it now handles any and every block.

The config folder is a Forge thing not a vanilla thing. And just because you're using json not .config doesn't mean it isn't a config file. Add to that the fact that the /assets directory doesn't exist when you distribute your mod.

Proper naming convention would slow that MyClass is a class where myClass is an instance. Or better yet, myLocallyIntelligentName so that you don't HAVE to make the distinction, but Classes should always start with a capital letter and instances a lower case letter.

Pretty sure we mentioned that a couple times... Ah, yes, here:

There is no EntityFallingGravel. It uses the same EntityFallingSand.