From dc3df3edd5843bde0c1335d6a8e460b2c832aa48 Mon Sep 17 00:00:00 2001 From: Foghrye4 Date: Sat, 17 Jun 2017 08:12:18 +0300 Subject: full project files --- javadoc/cpw/mods/fml/common/Mod.EventHandler.html | 184 ++++++++++++++++++++++ 1 file changed, 184 insertions(+) create mode 100644 javadoc/cpw/mods/fml/common/Mod.EventHandler.html (limited to 'javadoc/cpw/mods/fml/common/Mod.EventHandler.html') diff --git a/javadoc/cpw/mods/fml/common/Mod.EventHandler.html b/javadoc/cpw/mods/fml/common/Mod.EventHandler.html new file mode 100644 index 0000000..c16d246 --- /dev/null +++ b/javadoc/cpw/mods/fml/common/Mod.EventHandler.html @@ -0,0 +1,184 @@ + + + + + +Mod.EventHandler (Forge API) + + + + + + + +
+ + + + + +
+ + + +
+
cpw.mods.fml.common
+

Annotation Type Mod.EventHandler

+
+
+
+
    +
  • +
    +
    +
    @Retention(value=RUNTIME)
    +@Target(value=METHOD)
    +public static @interface Mod.EventHandler
    +
    Marks the associated method as handling an FML lifecycle event. + The method must have a single parameter, one of the following types. This annotation + replaces the multiple different annotations that previously were used. + + Current event classes. This first section is standard lifecycle events. They are dispatched + at various phases as the game starts. Each event should have information useful to that + phase of the lifecycle. They are fired in this order. + + These suggestions are mostly just suggestions on what to do in each event. + +

    These are the server lifecycle events. They are fired whenever a server is running, or about to run. Each time a server + starts they will be fired in this sequence. +

    + The second set of events are more specialized, for receiving notification of specific + information. +
    +
  • +
+
+
+ + +
+ + + + + +
+ + + + -- cgit v1.2.3