In whatever files we define a module id, we'll run a few extra lines of code that load a module file from the database, or create it if need-be.
Configs will be saved in one standard area (db, or json file.)
Configs will be read and written to in a standard way.
Why? To allow easier editing of modules in a way that should only need one universal staff-panel for.
In whatever files we define a module id, we'll run a few extra lines of code that load a module file from the database, or create it if need-be. Configs will be saved in one standard area (db, or json file.) Configs will be read and written to in a standard way. Why? To allow easier editing of modules in a way that should only need one universal staff-panel for.