modloader

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

info:modloader [2014/12/16 13:06]
mumfrey created
info:modloader [2015/02/13 00:55] (current)
mumfrey
Line 4: Line 4:
 ==================== ====================
  
-**ModLoader** was a simplistic [[ModSystem]] developed by [[people:​Risugami]] primarily to provide support and compatibility for his own mods but also made available to other modders to allow them to also leverage the increaed ​compatibility thus afforded. In the early days of modding, *"base modding"​* (creating mods by simply modifying the game's base code) was the *de facto* modding method and as such compatibility between mods was largely a matter of mods just happening to edit different classes.+**ModLoader** was a simplistic [[ModSystem]] developed by [[people:​Risugami]] primarily to provide support and compatibility for his own mods but also made available to other modders to allow them to also leverage the increased ​compatibility thus afforded. In the early days of modding, *"base modding"​* (creating mods by simply modifying the game's base code) was the *de facto* modding method and as such compatibility between mods was largely a matter of mods just happening to edit different classes.
  
 Amongst the various attempts to create some kind of compatibility layer, **ModLoader** became the most popular and was the modding platform of choice for a lengthy period, its relative stability was also attractive to modders since they could focus update efforts on the *Minecraft* codebase itself and not worry about **ModLoader** changing too much since [[people:​Risugami]] rarely added new features. Larger mods could still utilise "base modding"​ techniques, and use **ModLoader**'​s compatibility at the same time to strike a balance between compatibility and scope. Amongst the various attempts to create some kind of compatibility layer, **ModLoader** became the most popular and was the modding platform of choice for a lengthy period, its relative stability was also attractive to modders since they could focus update efforts on the *Minecraft* codebase itself and not worry about **ModLoader** changing too much since [[people:​Risugami]] rarely added new features. Larger mods could still utilise "base modding"​ techniques, and use **ModLoader**'​s compatibility at the same time to strike a balance between compatibility and scope.

Login