Custom Animation Wheel and Config Menus for YSM Models
Starting from version 2.3.0, Yes Steve Model (YSM) allows model creators to expand the standard animation roulette wheel with nested sub-wheels and interactive configuration panels. By editing the ysm.json file, you can organize extra animations into categories and let players toggle model parts or adjust values using sliders, checkboxes, and radio buttons.
Understanding the Enhanced Animation Wheel
In older versions of YSM, the animation wheel was limited to a flat list of extra animations defined inside the extra_animation field of your ysm.json file.
Since YSM 2.3.0, you can add sub-menus and configuration buttons directly to the wheel. This matters because complex models often have dozens of emotes or toggleable accessories (like hats, ears, or weapon states) that no longer fit cleanly on a single wheel.
All of these features are configured in your model's ysm.json file using three main fields: extra_animation, extra_animation_classify, and extra_animation_buttons.
Linking Sub-Wheels and Buttons in extra_animation
Everything starts inside your existing extra_animation object in ysm.json. Standard animation slots (like extra1) still work the exact same way, but the # symbol is now used as a special prefix to trigger sub-wheels or config menus.
Depending on whether you place the # symbol in the key or in the value, YSM will behave differently:
- Standard Animation: Pair an animation key with a display name (e.g., "extra1": "Wheel Animation 1") to play that animation normally.
- Config Button (Value starts with #): If the value starts with # (e.g., "extra2": "#button1"), YSM looks inside extra_animation_buttons for an entry with a matching id and adds a clickable configuration button to that slot.
- Sub-Wheel Category (Key starts with #): If the key starts with # (e.g., "#category1": "Test Category"), clicking this slot opens a sub-wheel defined in extra_animation_classify with a matching id.
- Return Button (Added in 2.3.1): Using the fixed key "#return" (e.g., "#return": "Back") creates a wheel slot that acts just like a back/return button.
{
"extra_animation": {
"extra1": "Wheel Animation 1",
"extra2": "#button1",
"#category1": "Test Category",
"#return": "Back Button"
}
}Creating Sub-Wheels with extra_animation_classify
To prevent your main animation wheel from becoming cluttered, use the extra_animation_classify array to group related animations into sub-menus.
Each object inside extra_animation_classify requires an id (which matches the text after the # in your main extra_animation key, without the # itself) and its own nested extra_animation object.
Inside the nested extra_animation object, you assign animation keys like extra0, extra1, and extra2 to their display names, just like on the main wheel.
{
"extra_animation_classify": [
{
"id": "category1",
"extra_animation": {
"extra0": "Animation 1",
"extra1": "Animation 2",
"extra2": "Animation 3",
"extra3": "Animation 4"
}
}
]
}Adding Interactive Settings with extra_animation_buttons
When a wheel slot's value points to a button ID (such as "extra2": "#button1"), clicking the light-blue config section on the wheel opens a side panel. You define the controls inside this side panel using the extra_animation_buttons array.
Each button entry needs three properties: an id (matching the name after #), a name (any display name you want shown on the wheel/header), and a config_forms array containing the UI controls.
These UI controls directly modify Molang variables on your model, allowing players to customize appearances in real time without switching models.
{
"extra_animation_buttons": [
{
"id": "button1",
"name": "Custom Settings",
"config_forms": [
// UI form components go here
]
}
]
}Config Form Types: Range, Checkbox, and Radio
Inside config_forms, YSM supports three types of interactive UI components. Every component links to a Molang variable in its value field—you must provide a variable name, never a complex expression.
1. Slider ("type": "range"): Lets players smoothly adjust a number between a minimum and maximum value. Use step to control the increment, and min / max to set the boundaries. For example, linking this to v.player_size lets players scale the model.
2. Toggle Switch ("type": "checkbox"): A simple on/off switch that toggles a Molang variable (such as v.neko to show or hide cat ears).
3. Single Choice ("type": "radio"): Displays a list of mutually exclusive options defined in a labels object. When the menu opens, YSM reads the variable in value (e.g., v.type): if it equals 0, the first option is selected; if 1, the second is selected, and so on. Each key in labels is the display text, and its value is a Molang execution statement (such as "v.type=0;") run when clicked.
"config_forms": [
{
"type": "range",
"title": "Size",
"description": "Change the player size",
"value": "v.player_size",
"step": 0.1,
"min": 0.2,
"max": 5
},
{
"type": "checkbox",
"title": "Toggle Cat Ears",
"description": "Show or hide the cat ears",
"value": "v.neko"
},
{
"type": "radio",
"title": "Select an Option",
"description": "Test the effect",
"value": "v.type",
"labels": {
"Option A": "v.type=0;",
"Option B": "v.type=1;",
"Option C": "v.type=2;"
}
}
]Complete ysm.json Configuration Example
Here is how all three sections fit together inside ysm.json. You can copy this structure into your existing file and replace the IDs, display names, and Molang variables to match your model's animations.
{
"extra_animation": {
"extra1": "Wheel Animation 1",
"extra2": "#button1",
"#category1": "Test Category",
"#return": "Back Button"
},
"extra_animation_classify": [
{
"id": "category1",
"extra_animation": {
"extra0": "Animation 1",
"extra1": "Animation 2",
"extra2": "Animation 3",
"extra3": "Animation 4"
}
}
],
"extra_animation_buttons": [
{
"id": "button1",
"name": "Custom Config",
"config_forms": [
{
"type": "range",
"title": "Size",
"description": "Switch player size",
"value": "v.player_size",
"step": 0.1,
"min": 0.2,
"max": 5
},
{
"type": "checkbox",
"title": "Toggle Cat Ears",
"description": "Switch cat ears on or off",
"value": "v.neko"
},
{
"type": "radio",
"title": "Choose the Option",
"description": "Test the effect",
"value": "v.type",
"labels": {
"A": "v.type=0;",
"B": "v.type=1;",
"C": "v.type=2;",
"Custom Label": "v.type=3;"
}
}
]
}
]
}Questions
Which version of YSM do I need for sub-wheels and config buttons?
Sub-wheels and custom configuration buttons require YSM 2.3.0 or newer. The special #return wheel slot requires YSM 2.3.1 or newer.
What is the difference between putting # in the key versus the value in extra_animation?
Putting # at the start of a key (like "#category1": "Label") opens a sub-wheel defined in extra_animation_classify. Putting # at the start of a value (like "extra2": "#button1") attaches a settings button from extra_animation_buttons to that animation slot.
Can I put a Molang expression in the 'value' field of a slider, checkbox, or radio form?
No. The 'value' field in config_forms must strictly be a single Molang variable name (such as v.player_size, v.neko, or v.type). Expressions are not allowed there.
How does the radio button know which option is currently selected when opening the menu?
YSM reads the numeric value of the Molang variable specified in 'value'. If the variable equals 0, it checks the first option in 'labels'; if it equals 1, it checks the second option, and so on.