718
edits
Kernelmethod (talk | contribs) m (Add info about the "Requires" attribute for the <option> tag) |
Kernelmethod (talk | contribs) m (Add a brief note about submodule-management) |
||
Line 38: | Line 38: | ||
|- | |- | ||
| <code>Type</code> | | <code>Type</code> | ||
| Affects the widget that is rendered for the option, and the values that it can take on. | | Affects the widget that is rendered for the option, and the values that it can take on. The following widget types are currently supported: | ||
* <code>Checkbox</code> | |||
* <code>Slider</code> | |||
* <code>Button</code> | |||
* <code>Combo</code> | |||
* <code>BigCombo</code> | |||
Each of these types has custom attributes that are specific to them; refer to the base game's <code>Options.xml</code> for a reference. | |||
|- | |- | ||
| <code>Default</code> | | <code>Default</code> | ||
Line 68: | Line 74: | ||
} | } | ||
</syntaxhighlight> | </syntaxhighlight> | ||
=== Enabling and disabling XML === | |||
Options are not natively supported by the game for conditionally enabling or disabling behavior in XML. For example, there isn't a way to configure the game only to merge into an object's blueprint if a given option is enabled. For possible solution to this problem, check out the [https://github.com/kernelmethod/QudMods/tree/main/SubmoduleManagement submodule-management] mod. | |||
{{Modding Navbox}} | {{Modding Navbox}} |