-
Notifications
You must be signed in to change notification settings - Fork 0
Selection and Plugin Types
Patrice LECUYER edited this page Jul 30, 2026
·
1 revision
A group's selection type controls how many plugins the player may choose in it.
| Type | Meaning |
|---|---|
| SelectExactlyOne | The player must select exactly one plugin. |
| SelectAtMostOne | The player may select one plugin, or none. |
| SelectAtLeastOne | The player must select at least one plugin. |
| SelectAny | The player may select any number of plugins (including none). |
| SelectAll | All plugins are installed; the player cannot deselect them. |
A plugin's default type tells the manager how the option should behave/appear. It can also be made dynamic through dependency patterns.
| Type | Meaning |
|---|---|
| Optional | Optional; not selected by default. |
| Required | Always installed; cannot be deselected. |
| Recommended | Suggested to the player (selected by default). |
| NotUsable | Cannot be selected (e.g. a missing requirement). |
| CouldBeUsable | Usable only under certain conditions (warns the player). |
Plugins can set flags when selected, and steps/options/conditional installs can be shown or applied depending on flags, installed files, or game/mod dependencies, combined with And/Or operators. This is how you build branching, conditional installers. See FOMOD Format and User Interface (Conditional Installs).
XIMOD Architect · MIT License · A Rust port of Wenderer's FOMOD Creation Tool, published with permission.
Using XIMOD
Reference
Project