Items are currently handled by items.json file under statpacks. However, this is not practical by any means if you'd like to create extensive list of them, as those entries will be rough to work with.
This is why I'd suggest totally different system, and bundle it with new statpack addition: monsters.
This system would operate on items folder instead, and each .json file there would represent item of given - IID would head into file with IID name, not contents of json. This will also make files less heavy nested and will go nicely with new assets folder which will also be added.
Albeit folders wouldn't be possible, as they would require more data than just IID, it will be also easier to manage items and entities categories, as we can add them as prefixes for IDs, for example:
ayer_knife -> weapon_blade__ayer_knife
Of course this will require not going for too long names/too many subcategories, but should do the trick.
Items are currently handled by
items.json
file under statpacks. However, this is not practical by any means if you'd like to create extensive list of them, as those entries will be rough to work with.This is why I'd suggest totally different system, and bundle it with new statpack addition: monsters.
This system would operate on
items
folder instead, and each .json file there would represent item of given - IID would head into file with IID name, not contents of json. This will also make files less heavy nested and will go nicely with newassets
folder which will also be added.Let me visualise the structure:
Albeit folders wouldn't be possible, as they would require more data than just IID, it will be also easier to manage items and entities categories, as we can add them as prefixes for IDs, for example:
ayer_knife
->weapon_blade__ayer_knife
Of course this will require not going for too long names/too many subcategories, but should do the trick.