FANDOM


(Created page with "Here is a quick update: The plugin mechanism is finished, and a large part of the API too. I'll now work on the basic recipe handlers (crafting table, alloy forge, trader) to ...")
 
 
Line 5: Line 5:
 
If finished, I'll provide the documented sourcecode of the API and the integrated recipe handlers (as an example on how to use the API) on GitHub. I won't provide the other parts of the sourcecode, because they are internal modules of the plugin and not part of the public API and no recipe handler should depend on them (if you need them for some reason, I'll provide them of course, but referencing internal code from the recipe handlers indicates design issues with either the handler or the addon itself).
 
If finished, I'll provide the documented sourcecode of the API and the integrated recipe handlers (as an example on how to use the API) on GitHub. I won't provide the other parts of the sourcecode, because they are internal modules of the plugin and not part of the public API and no recipe handler should depend on them (if you need them for some reason, I'll provide them of course, but referencing internal code from the recipe handlers indicates design issues with either the handler or the addon itself).
   
Currently you don't have to contribute your own handlers, because I plann to (re)write them by myself. But as Sam pointed out before the plugin mechanism with the API is no longer bound to NEI or the LOTR Mod - you can write recipe handlers for other mods if you want (to example for TC if necessary, I don't know how much NEI support it has).
+
Currently you don't have to contribute your own handlers, because I plann to (re)write them by myself. But as Sam pointed out before the plugin mechanism with the API is no longer bound to NEI or the LOTR Mod - you can write recipe handlers for other mods if you want (to example for TC if necessary, I don't know how much NEI support is there for it).

Latest revision as of 22:00, February 3, 2018

Here is a quick update: The plugin mechanism is finished, and a large part of the API too. I'll now work on the basic recipe handlers (crafting table, alloy forge, trader) to test the API and the plugin mechanism.

I created an abstraction layer over the recipe handlers of NEI, so you can build your own recipe handlers without to reference a single part of NEI. There are several reasons why I decided to create this abstraction layer, the two main reasons are that I don't like the way you have to manage recipe handlers with NEI and that I added features that needed this abstraction layer. Furthermore my recipe handler API should be more clear (I hope), more powerful and especially it's documented in detail.

If finished, I'll provide the documented sourcecode of the API and the integrated recipe handlers (as an example on how to use the API) on GitHub. I won't provide the other parts of the sourcecode, because they are internal modules of the plugin and not part of the public API and no recipe handler should depend on them (if you need them for some reason, I'll provide them of course, but referencing internal code from the recipe handlers indicates design issues with either the handler or the addon itself).

Currently you don't have to contribute your own handlers, because I plann to (re)write them by myself. But as Sam pointed out before the plugin mechanism with the API is no longer bound to NEI or the LOTR Mod - you can write recipe handlers for other mods if you want (to example for TC if necessary, I don't know how much NEI support is there for it).

Community content is available under CC-BY-SA unless otherwise noted.