Changeset View
Standalone View
binaries/data/mods/public/simulation/data/template_helpers/status_effects/anotherBogus.json
- This file was added.
{ | |||||
"code": "AnotherBogus", | |||||
"statusName": "StatusEffect's name 3", | |||||
"applierTooltip": "Some bogus bonus tooltip describing the effect of the modifiers. This increases the armour permanently." | |||||
wraitii: Move out of template_helpers , directly in data/status_effects | |||||
} | |||||
Done Inline ActionsWe could also store the icon here? Freagarach: We could also store the icon here? | |||||
Not Done Inline ActionsIf you're moving to JSON you should make it so that everything is in JSON, and move these from "template_helpers" to regular "data" folder imo. The damage types json might be put in their own folder after that, dunno. wraitii: If you're moving to JSON you should make it so that everything is in JSON, and move these from… | |||||
Not Done Inline Actions^, only thing we need to worry about is that some info still does need to find its way into entStates and template parameters in the gui, since they can be changed by the sim (techs on statuseffects should be allowed). One could think of making a function in the globalscript returning only all the fixed stuff for the gui, so noone would think of using other data directly from the JS. bb: ^, only thing we need to worry about is that some info still does need to find its way into… | |||||
Not Done Inline ActionsI've moved the icon here too, but indeed, modifiable data should not be stored in JSON, unless we can apply modifications to JSON. Freagarach: I've moved the icon here too, but indeed, modifiable data should not be stored in JSON, unless… |
Move out of template_helpers , directly in data/status_effects