GUIs and Tooltips
GUIs and Tooltips
Section titled “GUIs and Tooltips”Wonder extracts GUI definitions to config/wonder/guis/ and tooltip fragments to config/wonder/tooltips/.
Default GUI files:
| File | Purpose |
|---|---|
wonder_main.conf | Main Wonder hub with channel selector, trade, results, history, and cancel actions. |
wonder_trade_party.conf | Party-based trade picker. |
wonder_trade_pc.conf | PC-based trade picker. |
wonder_history.conf | Paginated Wonder history view. |
wonder_status.conf | Queue, result, summary, pool, and admin status view. |
Wonder loads GUI definitions from config/wonder/guis/ on startup. There is no runtime GUI reload command in the current code path.
Tooltips
Section titled “Tooltips”Default tooltip fragments:
| File | Purpose |
|---|---|
party_pokemon.conf | Tooltip for Pokemon the player is about to submit. |
result_pokemon.conf | Tooltip for the ready result item. |
history_pokemon.conf | Tooltip for Wonder history entries. |
Unlike GUIs, tooltips are reloaded through /wonder reload.
Selector System
Section titled “Selector System”Wonder tooltip fragments can target structured data through selectors like:
result.payload.displayData.nameresult.attributes.formhistory.attributes.iv_total
Wonder also registers custom selector and MoLang support through WonderTooltipSelector and WonderTooltipMolang, so tooltip conditions can react to Wonder-specific payload fields.