[1.7.10] Custom Events/ASM

[thatsimplekid]

Hello all,

I am trying to implement a custom event (FML Event) into my mod (event, not handler), and have gathered that I need to use ASM for this. However, when looking at the code of other mods (Namely IC2) I cannot seem to figure out how to do this.

It would be greatly appreciated if someone could point me in the direction of an open source mod, or any documentation that would help me.

Thanks in advance,

~ ThatSimpleKid.

 

p.s. I do already have an understanding of Java Bytecode

[thatsimplekid]

Basically I want to be able to push/handle my own event. The event is a custom event class that I have created (extending Event from cpw.mods.fml.common). However, when I setup a handler and push my custom event on the FML event bus, nothing happens.

[Draco18s]

Show the code, you're likely doing something wrong.

 

I did this exact thing just the other week.  I created an event, set up a handler as normal, then posted it to the Forge event bus.  Things went peachy.  My only issue was that I had to modify CustomOreGeneration to do it.

(Which I did a PR for and had accepted!)

[thatsimplekid]

EDIT: Don't worry, it now seems to work... Not sure what I did to fix it, but it's all good now... Thanks for the help anyway! 

 

In Main.java

 

 

...
@SubscribeEvent
   public void addTile(OxynetEvent.loadEvent event){
      System.out.println("RECEIVED EVENT");
   }

@Mod.EventHandler
    public void init(FMLInitializationEvent event) { // TileEntities, Events, Renderers
       FMLCommonHandler.instance().bus().register(this);
    }
...

 

 

 

and in OxynetEvent.java:

 

 

 

...
public class OxynetEvent {


public static class loadEvent extends Event {

}

}

 

 

 

 

and on a tile entity update method (for testing) i have:

FMLCommonHandler.instance().bus().post(new OxynetEvent.loadEvent());

[Draco18s]

There you go then.

 

I do suggest moving your EventHandler functions out of your main mod class (I use a single EventHandler class that deals with all of them--with a second client-sided one for client-side stuff--other people use one-class-per-event).