crashlog..not sure what it means

[firstarchon]

http://pastebin.com/fc2Y7de1 I was trying to add a config using the new gui flowing a forge tutorial and its crashing. I don't really know what in this is important but I was wondering if it contains any clues about where/what the problem is.

[TheGreyGhost]

What dieSieben said.

 

FYI this link might help understand what proxies do.

http://greyminecraftcoder.blogspot.com.au/2013/11/how-forge-starts-up-your-code.html

 

-TGG

 

[firstarchon]

package com.FirstArchon.RedStoneium;
import com.FirstArchon.RedStoneium.handler.ConfigurationHandler;
import com.FirstArchon.RedStoneium.proxy.Iproxy;
import com.FirstArchon.RedStoneium.reference.Reference;
import cpw.mods.fml.common.Mod;
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;

@Mod(modid = Reference.MOD_ID , name = Reference.MOD_NAME ,version = Reference.VERSSION, guiFactory = Reference.GUI_FACTORY_CLASS )



public class RedStoneium {

@Mod.Instance(Reference.MOD_ID)
public static RedStoneium instance;

@SidedProxy(clientSide = Reference.CLIENT_PROXY_CLASS , serverSide = Reference.SERVER_PROXY_CLASS)
public static Iproxy proxy;



@Mod.EventHandler
public void preInit(FMLPreInitializationEvent event) {
ConfigurationHandler.init(event.getSuggestedConfigurationFile());

}

@Mod.EventHandler
public void Init(FMLInitializationEvent event) {

}
@Mod.EventHandler
public void postInit(FMLPostInitializationEvent event) {

}
}

package com.FirstArchon.RedStoneium.reference;

public class Reference {
public static final String MOD_ID  = "RedStoneium";
public static final String MOD_NAME = "Redstoneium";
public static final String VERSSION = "1.7.10-1.0";
public static final String CLIENT_PROXY_CLASS = "com.FirstArchon.RedStoneium.proxy.ClientProxy";
public static final String SERVER_PROXY_CLASS = "com.FirstArchon.RedStoneium.proxy.ServerProxy";
public static final String GUI_FACTORY_CLASS = "com.FirstArchon.RedStoneium.client.gui.GuiFactory";



}

package com.FirstArchon.RedStoneium.proxy;

public interface Iproxy {

}

package com.FirstArchon.RedStoneium.proxy;

public class CommonProxy implements Iproxy {

}

package com.FirstArchon.RedStoneium.proxy;

public class ClientProxy {

}

package com.FirstArchon.RedStoneium.proxy;

public class ServerProxy extends CommonProxy {

}

 

these are all the classes that effect the proxy. I didn't change any of this for a while though. I changed the Guifactroy to take advantage of the new config options in 1.7.10 and then it wouldn't start anymore.

[TheGreyGhost]

I'm pretty sure this isn't right... where's your implements?

public class ClientProxy {

 

As a matter of interest, why the extra complication of IProxy?  Client and Server extending Common, with public static CommonProxy proxy, will work just as well and be less complicated?

 

Also, Capital letters in your Mod ID and package names is going to cause you grief sooner or later.  Packages should always be lower case by convention, and I've seen quite a few subtle bugs arise because the Mod ID had upper case letters. 

 

-TGG

 

 

 

[firstarchon]

oops that was  it that should have been

public class ClientProxy extends CommonProxy

I don't fully understand it myself because I'm following a tutorial. as I uderstand it  commonproxy is a implementation of iproxy. common will be what server and client have in common. client and server proxies inherit the contents of common and then you add whatever u want to them.

[Draco18s]

oops that was  it that should have been

public class ClientProxy extends CommonProxy

I don't fully understand it myself because I'm following a tutorial. as I uderstand it  commonproxy is a implementation of iproxy. common will be what server and client have in common. client and server proxies inherit the contents of common and then you add whatever u want to them.

 

You don't actually need IProxy or ServerProxy.  IProxy here is pointless and generally speaking your "server" proxy is actually the Common proxy.

[TheGreyGhost]

I don't fully understand it myself because I'm following a tutorial. as I uderstand it  commonproxy is a implementation of iproxy. common will be what server and client have in common. client and server proxies inherit the contents of common and then you add whatever u want to them.

This link might help you understand how Proxy works

http://greyminecraftcoder.blogspot.com.au/2013/11/how-forge-starts-up-your-code.html

 

-TGG

 

[firstarchon]

I'm following a tutorial by Pahimar and I think he is having it done this way for a reason I just don't know what that reason is yet.

[Mitchellbrine]

What the IProxy? It's just his way of doing things.

 

You just need 2 classes, the common proxy (or server proxy) and the client proxy, which extends the common proxy. That's all. You don't need any fancy interfaces, just use the common proxy. IProxy is just a waste of space.

 

Granted, very little space, but it's still a waste of space.

[Draco18s]

Ok, I'll grant that that is a valid point.

[TheGreyGhost]

Actually IProxy (or rather Proxy as an interface, I prefixes are stupid) has a reason. If you need to access @SideOnly(SERVER) code you need a separate ServerProxy to be 100% correct.

Then you have Proxy and ServerProxy and ClientProxy implement that. The concept of a "CommonProxy" I find rather weird and stupid. Proxies are designed to access side-specific code, not common code.

It's not weird or stupid at all. 

ClientProxy = code for {client+integrated server} only

ServerProxy = code for dedicated server only

CommonProxy = code for both {client+integrated server} and dedicated server

Seems very logical to me.  Purely a matter of taste whether your common code goes in a CommonProxy base class or stays in your Mod class.  If there's no code in CommonProxy you may as well use IProxy instead of CommonProxy (but not both as per OP code).

 

-TGG