Species Mod JSON Format: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Species JSON supports a variety of parameters to create custom transformations. A "type" of "SPECIES" should be used when creating an entity mod. An "id" field should also b...") |
mNo edit summary |
||
| Line 1: | Line 1: | ||
Species JSON supports a variety of parameters to create custom transformations. | Species JSON supports a variety of parameters to create custom transformations. | ||
'''NOTE - Species Modding is planned to be introduced for build r24.''' | |||
A "type" of "SPECIES" should be used when creating an entity mod. | A "type" of "SPECIES" should be used when creating an entity mod. | ||
Revision as of 05:35, 22 January 2018
Species JSON supports a variety of parameters to create custom transformations.
NOTE - Species Modding is planned to be introduced for build r24.
A "type" of "SPECIES" should be used when creating an entity mod.
An "id" field should also be specified with the name of the transformation. Please see the id naming guidelines elsewhere on this wiki (TODO: Find link and put it here).
A field of "transformedBodyPartDescriptions" can contain definitions for each body part, OR a lua function can be defined for 'getBodyPartDescription'. Usually transformedBodyPartDescriptions is used, unless you need to handle a multi-phased transformation for a particular body part (for instance, growing a small tail, then the tail becoming bigger).
| Return Type | Parameter |
|---|---|
| string | getBodyPartDescription(string bodyPartName, int severity)
todo |
| string | todo
todo |