Documented available RegistryEvents

docs/concepts/registries.md

@@ -23,6 +23,8 @@ public void registerBlocks(RegistryEvent.Register<Block> event) {
 
 The order in which `RegistryEvent.Register` events fire is arbitrary, with the exception that `Block` will *always* fire first, and `Item` will *always* fire second, right after `Block`. After the `Register<Block>` event has fired, all [`ObjectHolder`][ObjectHolder] annotations are refreshed, and after `Register<Item>` has fired they are refreshed again. They are refreshed for a third time after *all* of the other `Register` events have fired.
 
+`RegistryEvent`s are currently supported for the following types: `Block`, `Item`, `Potion`, `Biome`, `SoundEvent`, `PotionType`, `Enchantment`, `IRecipe`, `VillagerProfession`, `EntityEntry`
+
 There is another, older way of registering objects into registries, using `GameRegistry.register`. Anytime something suggests using this method, it should be replaced with an event handler for the appropriate registry event. This method simply finds the registry corresponding to an `IForgeRegistryEntry` with `IForgeRegistryEntry::getRegistryType`, and then registers the object to the registry. There is also a convenience overload that takes an `IForgeRegistryEntry` and a `ResourceLocation`, which is equivalent to calling `IForgeRegistryEntry::setRegistryName`, followed by a `GameRegistry.register` call.
 
 Creating Registries

docs/conventions/loadstages.md

@@ -6,8 +6,15 @@ There are some other events that are important too, depending on what your mod d
 Each of these stages occurs at a different point in the loading stage and thus what can be safely done in each stage varies.
 
 !!! note
+
     Loading stage events can only be used in your `@Mod` class, in methods marked with the `@EventHandler` annotation.
 
+!!! important
+
+    Many objects that were previously registered in loading stage event handlers (Blocks, Items, Recipes, etc.) should now be registered via [RegistryEvents][registering].
+    This is to pave the way to being able to reload mods dynamically at runtime, which can't be done using loading stages (as they are fired once upon application startup).
+    RegistryEvents are fired after Pre-Initialization.
+
 ## Pre-Initialization
 
 Pre Init is the place to let the game know about all the blocks, items, etc that your mod provides.
@@ -41,4 +48,6 @@ Common actions to preform in postInit are:
 ##Other Important Events
 
   * IMCEvent: Process received IMC Messages
-  * FMLServerStartingEvent: Register Commands
+  * FMLServerStartingEvent: Register Commands
+
+[registering]: ../concepts/registries.md#registering-things