Config Overview
FioMenu is not one single menu file format. The project is split into several YAML families, and each family has a different job.
Main YAML families
| Folder or file | Purpose |
|---|---|
config.yml | global plugin behavior, integrations, debug, storage, join events, Bedrock detection |
animations.yml | item and text animation definitions |
placeholders.yml | FioMenu-owned placeholder utilities |
sounds.yml | reusable menu sound sequences |
translation.yml | language profiles and translation keys |
fio_menus/*.yml | Java inventory menus and related runtime menus |
bedrock_fio_menus/*.yml | Bedrock form menus |
fio_menus/dialog/*.yml | Java dialogue layouts |
fio_menus/prompt/*.yml | prompt-based input examples |
How these files work together
The bundled examples show this common pattern:
- A Java menu is defined under
fio_menus/. - That menu may point Bedrock players to a Bedrock form using
menu.bedrock: "<id>". - The menu may use
%...%placeholders, translation keys, sounds, and animations. config.ymldecides whether integrations and Bedrock detection are active.
Source examples worth studying first
If you want to understand the current build from real YAML instead of assumptions, start with these files:
fio_menus/example.ymlfio_menus/settings.ymlfio_menus/profile.ymlfio_menus/dynamic_menu.ymlfio_menus/warps.ymlbedrock_fio_menus/example.ymlbedrock_fio_menus/settings.ymlfio_menus/dialog/dialogue_main.ymlfio_menus/prompt/chat_prompt_ex.ymlfio_menus/prompt/anvil_prompt_ex.yml