Simple GUI API
A reusable configuration GUI API with themes, profiles, key bindings, and responsive layouts.
How to use this reference
Section titled “How to use this reference”The table lists user-facing controls found in the documented build. Some controls appear only after a parent feature is enabled. Make one change at a time and use the screen’s save/apply action before testing.
| Setting | Meaning |
|---|---|
| Theme | Selects colors and control appearance. |
| Profiles | Saves, switches, and removes named settings sets. |
| Tabs | Organizes large settings screens by feature. |
| Search | Filters settings by label or description. |
| Key registry | Provides shared key-binding controls. |
| Responsive layout | Adapts columns and scrolling to screen size. |
| Definitions | Declares typed entries and defaults. |
| Callbacks | Connects change, save, and cancel behavior. |
Choosing values
Section titled “Choosing values”Begin with defaults, then change the smallest number of settings needed for the goal. Performance-related distance, count, rendering, or concurrency limits should be raised gradually. Automation timing should be conservative on multiplayer servers. Visual colors should be tested against both bright and dark scenes.
Saving and profiles
Section titled “Saving and profiles”If profiles are available, duplicate or create a new profile before a large experiment. Give it a descriptive name such as “Single player” or “Server low impact.” Finish the save/apply action and reopen the screen once to verify persistence.
Reset strategy
Section titled “Reset strategy”When the cause of a problem is unclear, record the current values, reset only the relevant category, and test again. Avoid deleting the entire configuration first: a category-level reset preserves unrelated preferences and provides better diagnostic evidence.