Guide · Animation

Parallel animations (blinking, ears, hair physics)

Parallel animations in Yes Steve Model (YSM) allow you to run continuous background effects like blinking, ear twitches, or tail wagging alongside standard player actions. These animations loop independently of the main movement states, bringing your character to life without getting interrupted when the player walks, sprints, or attacks.

What are Parallel Animations and Where Do They Go?

In a standard animation setup, playing a walking or attacking animation overrides the idle animation. Parallel animations solve this by running on separate, independent tracks that loop continuously regardless of what the character is doing.

Just like your core movement animations, all parallel animations must be placed inside the main.animation.json file. They are ideal for subtle, constant motions such as blinking eyes, swaying tails, twitching animal ears, or breathing effects.

You can also embed molang expressions inside parallel animations to dynamically show or hide armor pieces and accessories based on specific in-game conditions.

The Two Categories: pre_parallel vs. parallel

YSM divides parallel animations into two distinct groups based on how they interact with main animations (such as walking, running, or swinging a sword): pre_parallel and parallel.

The pre_parallel category has a lower priority than main animations. If both a pre_parallel animation and a main animation try to move the exact same bone, the main animation will completely overwrite the pre_parallel movement. This is useful for background idle twitches that should stop when a limb is actively being used.

The parallel category has a higher priority than main animations and uses a special additive blending system. Instead of overwriting or being overwritten, it layers its movement on top of the main animation. This makes it perfect for animations that must always be visible, such as blinking or secondary physics on hair and ears.

Available Animation Names and Priority Order

You can define up to eight tracks for each category inside main.animation.json. All sixteen parallel tracks play on an automatic loop and run independently of the main animation state.

Within each group, priority is determined by the number at the end of the name. A higher number always has a higher priority than a lower number (for example, pre_parallel7 has higher priority than pre_parallel0, and parallel7 has the highest priority of all).

Lowest Priority (Overwritten by main animations):
pre_parallel0, pre_parallel1, pre_parallel2, pre_parallel3,
pre_parallel4, pre_parallel5, pre_parallel6, pre_parallel7

Highest Priority (Blends on top of main animations):
parallel0, parallel1, parallel2, parallel3,
parallel4, parallel5, parallel6, parallel7
You do not need to use all eight slots in order, but keeping them organized (e.g., parallel0 for blinking, parallel1 for ears, parallel2 for armor visibility molang) makes your project much easier to maintain.

How Special Additive Blending Works

Understanding why the parallel0 through parallel7 tracks are special requires looking at how YSM combines bone movements. Normally, when a higher-priority animation plays, it completely replaces the bone values of a lower-priority animation.

The parallel category instead uses additive blending, which adds rotation values together rather than replacing them. For example, suppose Animation A bends an arm by 10 degrees, and a higher-priority Animation B bends the same arm by 25 degrees. Under default behavior, Animation B overwrites Animation A, resulting in a 25-degree bend. With YSM's special blending on parallel tracks, the two movements stack together, resulting in a combined 35-degree bend.

This special additive blending only applies to bone rotations. It will not blend position (translation) or scale values—those will still follow standard priority replacement rules.

If you animate a bone's position or scale inside a parallel0-7 track, it will completely override the position or scale of that bone in your main walking or attacking animations. Stick to rotation keyframes when layering movements on shared bones.

Questions

Which animation file should contain parallel0 or pre_parallel0?

They must be placed inside your model's main.animation.json file, alongside standard animations like idle and walk.

Should I use pre_parallel or parallel for blinking eyes?

Either works if your main animations don't touch the eyelid bones, but parallel0 is generally preferred. Because parallel tracks have the highest priority, your character will continue blinking even during full-body animations.

Why is my parallel animation breaking the position of my character's arms during a walk cycle?

The special blending system on parallel0 through parallel7 only adds rotations together. If you included position (displacement) or scale keyframes in your parallel animation, they will overwrite the main animation instead of blending with it.

How can I constantly check a molang condition to hide armor?

Create a looping parallel animation (such as parallel0) in main.animation.json and put your molang visibility scaling or bone toggling inside it. Because parallel animations always run, the molang check will be evaluated continuously.

Next: Player main animations (idle, walk, run, jump...) →

More in Animation

A
Armor AnimationsArmor animations allow your custom Yes Steve Model (YSM) character to visually display gear or change its appearance whenever the player equips armor. By controlling bone scaling through specific animation names, you can dynamically show or hide custom 3D armor pieces for specific items, item tags, or any equipped armor in general.
A
Arrow and projectile animationsCustomizing projectiles allows your character model to fire unique arrows, tridents, snowballs, or even modded projectiles with their own 3D geometry and animations. Starting from YSM version 2.5.0, the legacy arrow system was expanded into a universal projectile system that supports almost any thrown or shot entity in Minecraft. This guide covers how to set up projectile files in your model configuration, use animation controllers, and support older YSM versions.
A
Extra Animations in the Animation WheelExtra animations allow players to trigger custom emotes, dances, or poses on demand using the in-game animation wheel. All wheel animations must be stored in a dedicated file named extra.animation.json to be recognized by the Yes Steve Model mod.
A
First-Person Arm Animations and Mod CompatibilityYes Steve Model (YSM) lets you bring your custom character's hands to life in the default first-person view. Since version 2.5.0, you can add dedicated first-person arm animations and configure your model to work smoothly with third-party first-person camera mods. This guide covers how to register these animations, understand bone limitations, and prevent your model's head from blocking the player's view.
A
Hand Condition Animations (Items in Hand)Condition animations in Yes Steve Model (YSM) are specially named animations that play automatically when certain in-game triggers occur, allowing you to create responsive actions without touching complex animation controllers. Hand condition animations specifically control how your character's arms react when holding, using, or swinging items.
A
Model Selection Screen Animations (gui, hover, focus)Since version 2.2.2, Yes Steve Model supports custom preview animations inside the in-game model selection menu. You can make your character pose, react to mouse hover events, or celebrate when selected by adding specific animations to your model files. This adds a polished, interactive feel before a player even equips your model.