Lingya formulas: stun length, shield shred and cast rhythm

Lingya (灵压, Spiritual Pressure) is a loadout stat with two formulas attached, and the combat chapter covers where it sits in the wider fight model. This page is the deep-play article: both formulas worked through, the two caps compared, and the placement call that decides whether a fabao collision costs or buys an ability cycle. Every value below is single-source and should be re-checked after a balance patch.

How is total Lingya calculated?

Total Lingya is a plain sum. Add up the Lingya value printed on every fabao currently equipped, and that total is the stat. There is no multiplier, no hidden coefficient and no second input. Lingya cannot be raised by playing more, only by changing what is equipped, so a player who wants the stat is really shopping for fabao with a higher Lingya line.

That definition also settles a common confusion. Lingya is not a hidden power score that summarises the whole build. It is a collision-resolution stat: it applies when flying fabao meet, and the two effects it governs are stun duration and shield removal on that collision. A build with enormous damage and low Lingya is not weak in general; it is weak specifically in the exchange where the fabao meet, which is often the first exchange of the fight.

How does the stun formula scale?

When your Lingya exceeds the opponent's, you extend their stun. The base is 3 seconds, and every 1% of advantage adds 1% of that base, which is 0.03 seconds. The scaling is linear up to the hard cap at 6 seconds, reached at exactly +100% advantage.

Lingya advantage	Stun duration
0% (equal)	3.0 seconds (base)
+1%	3.03 seconds
+10%	3.3 seconds
+50%	4.5 seconds
+100%	6.0 seconds (cap)

What matters is the size of a stun relative to the cadence. A 3-second stun costs most of one ability cycle. A 6-second stun spans nearly two 3.5-second cycles, which means the stunned player loses two chances to answer while the attacker keeps acting. The last 50 points of advantage buy 1.5 seconds, the same amount as the first 50, but at that point the stun has crossed from an inconvenience into a kill window.

How much shield does a collision remove?

The same relative advantage drives shield removal. Base reduction is 20%, and every 1% of advantage adds 1% more, capped at 100% at exactly +80% advantage. Unlike the stun, the shield formula reaches its ceiling 20 points earlier, which matters more than the raw numbers suggest.

Lingya advantage	Shield reduction
0% (equal)	20% (base)
+1%	21%
+30%	50%
+80%	100% (cap)

At +80%, the collision does not damage the shield; it deletes it. For a shield-reliant build that is the single worst threshold in the game, because the defensive layer it is built around simply does not exist in that matchup. It is also the reason a player who loses a shield instantly should read the result as a loadout gap rather than a rotation error: the opponent had +80% Lingya, and no reordering of abilities changes that.

Why does the 3.5-second rhythm decide placement?

Without fabao interference, abilities fire roughly every 3.5 seconds. That cadence is the resource the whole rotation spends. When fabao collide, the collision animation and its resolution eat into the timing of the next ability, so each collision is a withdrawal from the cadence rather than a free action layered on top of it. Placement is therefore not cosmetic ordering; it decides which part of the kit gets to run at full speed.

This is also why two builds with identical stats can feel different. A build that puts collisions early delays every ability behind them; a build that puts collisions late gets several clean cycles first. Neither is wrong in isolation. The correct order depends on where the damage actually is, which produces two strategies.

Should fabao be front-loaded or back-loaded?

Back-loading is the default for most builds, and the condition is explicit: when ability investment is high, placing fabao later in the rotation is more stable. The early abilities fire on the natural 3.5-second rhythm without collision interference, and by the time the fabao come out the main damage has already landed. The collision can then resolve without costing the part of the kit that was carrying the fight.

Front-loading is correct for the opposite distribution. When fabao damage far exceeds ability damage, the collision should happen early so the big fabao hits land before the opponent's defensive layers come online. The resulting delay to abilities is acceptable because abilities are not the win condition in that build. The mistake is mixing the two: front-loading on an ability build spends the cadence before the abilities have had a chance to use it, which is the most common rotation error associated with this stat.

Which cap should you push for first?

Push for +80% before chasing +100%. The shield cap arrives first and removes an entire defensive layer, which is usually the more decisive of the two effects; the extra 20 points from +80% to +100% convert into 1.5 seconds of stun, valuable but narrower in effect. Only spend additional fabao slots on the last stretch if the loadout has room without giving up damage elsewhere.

Past +100%, Lingya buys nothing for stuns, because the cap is hard at 6 seconds; the shield effect is already capped at +80%. That makes +100% the practical ceiling for the stat rather than a milestone to exceed. In a mirror matchup this is the whole fight: identical builds have identical ability and fabao damage, so the higher-Lingya player wins every stun trade and every shield trade, and the stat becomes the tiebreaker.

Which Lingya mistakes cost the most?

• Front-loading on an ability build. It spends the 3.5-second rhythm before the abilities land, and no amount of damage compensates for the lost cycles.
• Treating Lingya as a currency. It is a sum of equipped fabao values. Raising it means swapping or upgrading fabao, not farming a resource with that name.
• Reading an instant shield loss as a play error. It means the opponent holds +80% advantage. The fix is the loadout, not the order of casts.
• Ignoring the PVE trade-off. Against fixed, typically lower enemy Lingya, raw fabao damage is usually the better trade. Lingya is a PVP-priority stat first.

The build library lists rotations that assume one placement or the other; check which strategy a listed rotation was written for before copying it. The glossary keeps the stat's name fixed as Lingya, which matters when a guide from another source calls it something else.