All Yes Steve Model Commands (/ysm and /ysmclient)
Yes Steve Model includes built-in commands for managing player models, handling server permissions, and debugging animations. Most server commands start with /ysm and require OP permission level 2, while client-side creator tools use /ysmclient. Every command supports in-game auto-completion for player names and model IDs.
Loading, Setting, and Disabling Models
These main commands work on both singleplayer and multiplayer servers to control which models are loaded and worn by players.
Use /ysm model reload whenever you add or edit model files to refresh the server and automatically re-sync all models to connected players.
You can force a player into a specific appearance using the set command. If you do not want to specify a texture name, enter a hyphen (-) as the texture_id to apply the model's default texture. Setting the optional ignore_auth parameter to true lets you assign restricted models even if the player does not own permission for them.
Since version 2.5.2, administrators can temporarily turn off a player's custom appearance. Setting /ysm model disable to true hides the YSM model and returns the player to their vanilla Minecraft skin.
/ysm model reload
/ysm model set <player> <model_id> <texture_id> [ignore_auth]
/ysm model set Steve default - true
/ysm model disable <player> [true | false]Managing Player Model Authorization
On servers where certain models are locked behind permissions, operators can control who is allowed to equip restricted models in the YSM GUI.
The /ysm auth command grants or revokes access to specific models or unlocks the entire server catalog for a specific player.
/ysm auth <player> add <model_id>
/ysm auth <player> remove <model_id>
/ysm auth <player> all
/ysm auth <player> clearPlaying Animations and Running Server Molang
You can trigger animations or run Molang scripts on any online player from the server console, command blocks, or admin chat. This is ideal for server events, cutscenes, or testing how an animation looks on someone else.
Use /ysm play to force a specific animation on a target player, and run the stop variant to release them back to normal movement.
If you need to change a variable or trigger logic in multiplayer, /ysm molang execute runs a Molang expression directly on the specified player (note that the server command will not print the output value to chat).
/ysm play <player> <animation_name>
/ysm play <player> stop
/ysm molang execute <player> <expr>Exporting Models and Checking Server Connection
Model creators who want to package their folder-based models for distribution can use /ysm export to compile a model into the proprietary .ysm file format, optionally attaching extra notes or metadata.
For regular players having trouble connecting to a server's model list, /ysm ping tests the connection between client and server. It requires no OP permissions and helps resolve the error message stating that the server mod and client version are inconsistent.
/ysm export <model_id> [extra_info]
/ysm pingUsing the Client Debug Screen (Alt + B)
Model creators need to see how variables and animation controllers behave in real time. YSM provides a custom on-screen debug overlay specifically for this purpose, controlled by client-only /ysmclient commands.
Open the custom debug screen by pressing Alt + B (in versions 2.3.0 and newer, you only press it once; in 2.2.2 and earlier, press it twice).
Since version 2.5.2, you are no longer limited to debugging yourself: look directly at any entity using a YSM model and press Alt + B, or run the debug selector command to lock the debugger onto a specific entity.
/ysmclient debug <selector>Watching Molang Variables and Controllers
Once your debug overlay is open, you can pin live Molang values and controller states to your screen so you can watch them update frame-by-frame.
Since version 2.4.0, the /ysmclient watch shortcuts are the fastest way to monitor variables and animation controllers, or clear the screen when you finish testing.
If you only need to check a value once without pinning it, /ysmclient molang execute evaluates the expression and prints the result in your chat box (since 2.5.2, this runs on whichever entity you are currently debugging).
For advanced timing diagnostics, the full molang watch command lets you choose whether an expression is calculated pre (before animations update) or post (after animations update), and lets you give each watched entry a custom name.
# Quick watch commands (since 2.4.0)
/ysmclient watch var <expr>
/ysmclient watch state <controller>
/ysmclient watch clear
# One-time evaluation printed to chat
/ysmclient molang execute <expr>
# Named pre/post animation watches
/ysmclient molang watch add [pre|post] <name> <expr>
/ysmclient molang watch remove <name>
/ysmclient molang watch clearQuestions
Why can't normal players on my server use /ysm commands?
Almost all /ysm commands require OP permission level 2. The only exception is /ysm ping, which any player can run to test client-server connectivity.
How do I set a player's model using its default texture?
Run /ysm model set - and put a single hyphen (-) in place of the texture_id argument.
How do I fix the 'server mod and client version are inconsistent' error?
Run the command /ysm ping in chat. It requires no special permissions and checks the communication link between your client and the server.
How do I open the Molang debug overlay to see my watched variables?
Press Alt + B once (in YSM 2.3.0+) or twice rapidly (in YSM 2.2.2 and older). In version 2.5.2+, you can also aim at another YSM entity while pressing Alt + B to inspect their variables.
Next: How to Install Yes Steve Model and Use Custom Models →