Base mod for 1.8

[browndunce]

Sorry about this nub question, I am aware that you guys probably get this question at least once a week. I have a basic knowledge of Java, but not of modding Minecraft, so this is very foreign to me as of right now.

 

The Basic Modding tutorial (http://www.minecraftforge.net/wiki/Basic_Modding) is a bit outdated for 1.8. The base mod for 1.8 is located in the page source, but it is not very helpful This is what it says verbatim.

import cpw.mods.fml.common.Mod;
import cpw.mods.fml.common.Mod.EventHandler; // used in 1.6.2
//import cpw.mods.fml.common.Mod.PreInit;    // used in 1.5.2
//import cpw.mods.fml.common.Mod.Init;       // used in 1.5.2
//import cpw.mods.fml.common.Mod.PostInit;   // used in 1.5.2
import cpw.mods.fml.common.Mod.Instance;
import cpw.mods.fml.common.SidedProxy;
import cpw.mods.fml.common.event.FMLInitializationEvent;
import cpw.mods.fml.common.event.FMLPostInitializationEvent;
import cpw.mods.fml.common.event.FMLPreInitializationEvent;
//import cpw.mods.fml.common.network.NetworkMod; // not used in 1.7

@Mod(modid="GenericModID", name="Generic", version="0.0.0")
//@NetworkMod(clientSideRequired=true) // not used in 1.7
public class Generic {

        // The instance of your mod that Forge uses.
@Instance(value = "GenericModID")
public static Generic instance;

// Says where the client and server 'proxy' code is loaded.
@SidedProxy(clientSide="tutorial.generic.client.ClientProxy", serverSide="tutorial.generic.CommonProxy")
public static CommonProxy proxy;

@EventHandler // used in 1.6.2
//@PreInit    // used in 1.5.2
public void preInit(FMLPreInitializationEvent event) {
	// Stub Method
}

@EventHandler // used in 1.6.2
//@Init       // used in 1.5.2
public void load(FMLInitializationEvent event) {
	proxy.registerRenderers();
}

@EventHandler // used in 1.6.2
//@PostInit   // used in 1.5.2
public void postInit(FMLPostInitializationEvent event) {
	// Stub Method
}

If you copy this verbatim, but don't have the proxy classes, it may be possible for the mod to work for single player, but not for multiplayer. As such, make sure the proxy classes are created as described in the next section.

 

That's a lot of imports and annotations, no? The import list will only get longer with each additional tutorial you follow. Generally, Eclipse will handle imports for you, so I will not explicitly say to add import statements.

 

There '''WILL''' be an error when you copy this code. CommonProxy should be underlined red. This is because it will be created in the [[#Proxy Classes|Proxy Classes]] section.

 

Now that we've got that out of the way, you'll notice that there are a lot of @annotations and import statements (which will only get longer as you continue to mod and add more content to your mod); This is the absolute basis for creating a Mod for 1.8, But it won't do anything (at least, not yet).

 

However, I can not find this proxy section that it is talking about. Can you guys explain to me what this "proxy section" is and how I should implement it to have a base mod for 1.8?

 

P.S. What is Lex's full name? I can only find "Lex Manos", and that doesn't work for verification

[Draco18s]

http://www.minecraftforge.net/forum/index.php?action=profile;u=5

 

And don't bug him unless you have to. He does not maintain the content of the wiki pages, so there's no point in complaining directly to him, he will tell you "it is a wiki, if the information is wrong or missing, fix it."

 

The page says to "view the page source to see a1.8 proxy" just above the section you quoted.

I don't know why the "Proxy Classes" section is commented out, but you can view it if you click on one of the edit buttons.

[Ernio]

https://github.com/TheGreyGhost/MinecraftByExample

 

If you are asking "what is proxy?" - think of it as a way to reference things that are not there.

Some of fields/methods/classes are marked with SideOnly - that means thay will be loaded only by given side (Client.jar or Dedicated.jar). On other side they will be not loaded to VM which will result in NoClassDefFound when trying to access them with common code. That's why there are proxies - proxy will be setup for given side and can safely call SideOnly methods. All calls should be redirected there.