Skip to main content
PalMods

Silvegis Makes Your Shield Tougher. The Recharge Buff Has a Catch

Aegis Shield cuts incoming shield damage and the wait before recovery starts. Compare all five ranks without confusing a shorter delay with a faster refill.

PalMods Team 6 min read
On this page

The blue bar survives a hit that used to empty it. You duck out of the next attack, and it starts coming back sooner. Those are two separate benefits of Silvegis, and reading them as one vague promise of faster regeneration misses the part you can actually build around.

Aegis Shield reduces damage taken by your shield and shortens the delay before shield recovery starts. At its highest rank, the cuts are 80% and 60% respectively. That is a powerful support slot. It is also narrower than instant refills, health regeneration or permission to stand in every attack.

The useful question is where your defense fails: the hit that drains the shield, or the gap you need before it can recover. Silvegis helps both, but does a different job at each point.

Aegis Shield changes two different parts of a fight#

In an older Reddit discussion, Nimstar7 described a dramatic difference after adding a fully condensed Silvegis. Their question combined the 80% shield damage cut with the shield starting to recover “60% faster.” The reported benefit is theirs; the wording is where it helps to slow down.

For the numbers here, we use the PalMods 1.0.3 game-data snapshot. It records separate effects for shield damage reduction and the time before shield recovery starts. The current English skill description makes the same distinction.

The first effect makes each covered hit take less out of the bar. If an event would otherwise remove 100 shield points, a 65% cut leaves 35 to pay. An 80% cut leaves 20. Your shield capacity has not acquired a new item tier, but the same pool can cover more of that incoming shield damage.

The second effect helps during the pause afterward. A shorter delay means you need a smaller damage-free opening before recovery begins. That can make an otherwise awkward gap useful. It does not tell you that the bar fills at a higher number of points per second once it has started.

What every partner-skill rank changes#

Here is the full progression. The two percentages are reductions from their respective normal values, not two damage bonuses to add together.

Skill rankShield damage cut / start-delay cut
1, no stars65% / 30%
2, one star68% / 34%
3, two stars71% / 40%
4, three stars75% / 48%
5, four stars80% / 60%

The last step improves both halves. Moving from three stars to four changes a nominal 100-point shield hit from 25 points to 20. That is 20% less remaining shield damage compared with the three-star case, even though the displayed damage-cut bonus only rises five percentage points.

The delay also goes from 52% of its normal length to 40%. Keep that comparison separate from the shield hit: it is a time saving, not another twelve points of damage reduction.

These effects scale with the partner-skill rank. Do not confuse perfecting Silvegis's own combat stats with raising these listed values. Its innate Heavyweight passive improves its own Defense; that is a different benefit from the trainer's Aegis Shield effect.

Your equipped shield still sets the size of the buffer#

The Hyper Shield records 1,045 shield capacity in the snapshot. The Ultra Shield records 1,520. An 80% cut leaves one-fifth of the covered shield damage, so the idealized damage budget is five times the original pool.

Equipped shieldCapacity and rank-5 damage budget
Hyper1,045 capacity; 5,225 before the Aegis cut
Ultra1,520 capacity; 7,600 before the Aegis cut

This is a comparison with all other factors held fixed: capacity divided by 0.2. It is not a measured number of boss hits, an armor calculation or a claim about what happens to damage overflowing a broken shield. It shows why reducing incoming shield damage can matter much more than the unmodified capacity number suggests.

It also shows why Silvegis does not make shield upgrades pointless. Ultra has about 45.5% more capacity than Hyper, and that relative gap remains when both get the same Aegis reduction. The support Pal multiplies the value of the pool you equip; it does not erase the difference between the two pools.

Likewise, a slot spent on Silvegis is still a slot you could have spent on movement, damage or another kind of support. If the shield is comfortably surviving the encounter already, decide whether the extra buffer is solving tonight's actual problem.

Shorter delay does not mean a faster refill#

Separate the sequence into the hit, the wait and the refill. Aegis Shield affects the first two through different bonuses. The recovered effect values do not establish a third bonus to the refill speed.

Use a hypothetical ten-second normal delay to make the wording concrete. A 30% reduction would shorten that wait to seven seconds; a 60% reduction would shorten it to four. Ten seconds is an example for the arithmetic, not a claim about the game's actual timer.

You have gained a window in which recovery can start earlier. You have not shown that recovering the same missing shield points then takes 60% less time. Calling both things “faster regeneration” hides that distinction and can lead you to expect a full bar long before the skill promises one.

In practice, look for the pause between attacks and watch when the bar first begins to rise. If you keep taking damage, a better start delay is not the same as continuous healing through the barrage. This is a reason to create an opening, not to discard the habit of avoiding the next hit.

Choose the support for the bar that is failing#

Silvegis protects shield charge. Tetroise Primo reduces weapon and armor durability loss. A weapon needing repair and a shield needing time to refill are different problems, even when both send you out of a fight.

There is a third problem after those: health sustain. Aegis Shield's shield damage cut does not establish the same reduction for direct health damage, and its delay effect is not health regeneration. Nor should you project defensive passives for a fighting Pal onto the trainer's shield simply because both descriptions sound defensive.

The nonstacking condition matters here. Two Silvegis are not a shortcut to adding two copies of the listed reduction. One gives the party its shield role; another support should earn the next slot by addressing a different weakness.

  1. 1Record the actual shield

    Note the equipped item, current charge and Silvegis's partner-skill rank. A changed item pool can disguise what the partner skill did.

  2. 2Separate the hit from the pause

    Compare the charge lost to a similar attack, then watch when recovery starts during a clean opening. They are different observations.

  3. 3Keep the claim as small as the result

    Less shield loss and an earlier start do not prove faster refill, health immunity or safety against every boss move.

Bring Silvegis when the blue bar is the weak link. Let its damage cut buy you room, then use the smaller recovery opening it creates. The dragon's best trick is making a good defensive rhythm more forgiving, not making that rhythm unnecessary.