It's sad to see so many people still using 1.7.10...
But I like the idea! This is a good thing to see how many people use which MC version, and which Java version (seriously, 1 guy is already using Java 9...).
There are various ways you can pass a
World
object. For example, you can use
setWorldObj
on the
TileEntity
to set the world.
You can get a
World
object from
Minecraft#theWorld
(GUI), or your own
TileEntity
's worldObj. You can also pass in the
World
reference to
Block#createTileEntity
and
TileEntity#hasCapability
to reduce the chance on NPEs.
You shouldn't, as there's no reason not to. 1.11 will be out soon, which will make 1.8 not supported by Forge anymore. So update to 1.10.2 now, or 1.11 later.
There is currently no mapping for INDEV afaik, so you either have to make your own, or deal with obfuscated names.
P.S. Lex is not the creator of MCP, but the creator of Forge.
if (event.getSide() == Side.CLIENT) {
I'm checking if the side is the Client, so I don't have to worry 'bout that.
Doesn't matter. Java still needs to load the class "in case the class gets called". It doesn't exist on the server side, so it crashes with a ClassNotFoundException
. Putting that code in a proxy will solve that issue.
Forge caches every version of Minecraft and Forge in your user folder. If you make a separate folder for your second mod with the same Forge version, it actually uses the same JAR file with the Minecraft and Forge source.
It is because of this:
You actually have called the folder
minecraft.textures.gui
. This is 1 folder and not 3 folders underneath each other. If you make the folders separately, like your other folders, it will work fine from Eclipse.
This is not true. Forge supports Java 6 and later.
For now, Forge does support Java 6. However, cpw is reworking FML and he is going to use a lot of Java 8 features, which will make Java 8 a requirement in the new FML, which he hopes is going to be in MC 1.11 or 1.12.