nodecore-cd2025/mods/nc_api_active/init.lua

-- LUALOCALS < ---------------------------------------------------------
local include, nodecore
    = include, nodecore
-- LUALOCALS > ---------------------------------------------------------

nodecore.amcoremod()

include("limited_abm")
include("aism")
include("soaking")
include("ambiance")
Major rebuild of item_entity. This created a ton of dependency inversions, which necessitated moving a number of API functions up into higher layers, and restructuring dependency lists for a number of mods. BOLO: non-deterministic load errors due to missed dependencies. 2020-01-05 11:42:22 -05:00			`-- LUALOCALS < ---------------------------------------------------------`
NC API dependency simplification. Treat all API mods as a "layer", and use the new nc_api_all registration to indicate that a mod depends on the NC API (which ALL NC mods assume they do). This means that each non-API mod does not need to worry about which API mods it really needs and which it does not, nor will they need to be updated for any internal API restructures. This is a game, not a modpack, so all mods will be loaded anyway, and we only care about order. That means that we don't really need to worry about having excess dependencies because any mod we don't actually need will be needed by something that's loaded anyway. If somebody wants to reuse a component elsewhere, they're likely to need to do some work to untangle it anyway, because of the amount that NodeCore mechanics interact and interdepend. 2020-01-05 12:59:12 -05:00			`local include, nodecore`
			`= include, nodecore`
Major rebuild of item_entity. This created a ton of dependency inversions, which necessitated moving a number of API functions up into higher layers, and restructuring dependency lists for a number of mods. BOLO: non-deterministic load errors due to missed dependencies. 2020-01-05 11:42:22 -05:00			`-- LUALOCALS > ---------------------------------------------------------`

NC API dependency simplification. Treat all API mods as a "layer", and use the new nc_api_all registration to indicate that a mod depends on the NC API (which ALL NC mods assume they do). This means that each non-API mod does not need to worry about which API mods it really needs and which it does not, nor will they need to be updated for any internal API restructures. This is a game, not a modpack, so all mods will be loaded anyway, and we only care about order. That means that we don't really need to worry about having excess dependencies because any mod we don't actually need will be needed by something that's loaded anyway. If somebody wants to reuse a component elsewhere, they're likely to need to do some work to untangle it anyway, because of the amount that NodeCore mechanics interact and interdepend. 2020-01-05 12:59:12 -05:00			`nodecore.amcoremod()`

Major rebuild of item_entity. This created a ton of dependency inversions, which necessitated moving a number of API functions up into higher layers, and restructuring dependency lists for a number of mods. BOLO: non-deterministic load errors due to missed dependencies. 2020-01-05 11:42:22 -05:00			`include("limited_abm")`
			`include("aism")`
			`include("soaking")`
			`include("ambiance")`