Clothing JSON Mod Format: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 19: | Line 19: | ||
|'''getSlot''' | |'''getSlot''' | ||
Which [[Clothing slot|slot]] the clothes exists in. | Which [[Clothing slot|slot]] the clothes exists in. | ||
This should almost certainly be a literal string -- changing this value during run-time will lead to unknown results. | |||
|} | |} | ||
Latest revision as of 02:10, 30 December 2017
Entity JSON supports a variety of parameters to create custom objects. JSON definitions can specify each as programmable (LUA) or literal values.
(All Entity JSON parameters are also supported!)
Note that clothing uses a type of 'CLOTHING' instead of 'ENTITY'
| Return Type | Parameter |
|---|---|
| boolean | isVulnerableToMasculineTheft
If true, this item can be lost in situations where masculine clothes are lost (currently only the thief scene). |
| boolean | isConcealableClothing
If true, this item can conceal a transformation in the slot it is in (true for most clothing items). |
| string | getSlot
Which slot the clothes exists in. This should almost certainly be a literal string -- changing this value during run-time will lead to unknown results. |