Oh they're already read from JSON files by the monster and item parsers when using the optxxx() methods to pass to monster/item constructors.Zukero wrote:Thanks, glad you like it.twirlimp wrote: Amazing tool you did there.
I added a few new JSON fields and was wondering how difficult it would be to make them appear in the ATCS gui.
(I don't mind adding them myself if you're busy, since I'm going to help with ATCS eventually)
It shouldn't be difficult to add, but I won't do it in the "official" ATCS until this data is used by the current game code.
In order to code it yourself in a fork, you should look to this places:
- In class com.gpl.rpg.atcontentstudio.model.gamedata.NPC, especially methods parse(Map npcJson) and toJson()
- In class com.gpl.rpg.atcontentstudio.ui.gamedataeditors.NPCEditor, especially methods insertFormViewDataField(JPanel pane) and NPCFieldUpdate.valueChanged(JComponent source, Object value)
As it is an "enum" type of data, you can find inspiration with the Monster Class or Movement Type fields.
They new weapon range property is even shown in the item info in inventory.