Patch 0.05.005 rebalances FEARNAUGHT by party size
The official patch gives a directional result rather than a formula. Solo and two-player teams should face an easier version after the rebalance, while a four-player party should face a harder one. That makes party size part of the encounter plan, but it does not reveal multipliers, breakpoints, or an exact difficulty score.
A squad should choose its active party size in the planner and assign recovery, movement, and boss-readiness responsibilities before entering. Solo players cover every responsibility themselves, so a simpler plan and earlier retreat threshold can be useful. Neither approach depends on a guessed class ranking or damage requirement.
Holy Shield cooldown scales with the number of players
Holy Shield is the named FEARNAUGHT ability in Patch 0.05.005. Its cooldown now scales with player count. The post does not publish the cooldown at one, two, three, or four players. It also does not explain every shield condition, interaction, or visual cue.
Read the live shield state and communicate what the group can actually see. Preserve movement space while the squad confirms the current behavior. A client display bug was fixed in the same patch, so old recordings may show missing or incorrect shield information that should not be treated as the present interface.
Enemy spawn timing also scales with party size
The rebalance changes enemy spawn timing alongside Holy Shield cooldown. This means the encounter's pressure can change with group size even when the room and boss name are the same. The patch does not identify every enemy involved, publish a schedule, or promise a fixed spawn order.
Assign one player to keep the wider arena picture when the party is large enough, and name who takes over if that player is forced away. In solo, use the longer Penetrator interval only when that enemy is actually present and the live game confirms the situation. Do not combine separate patch lines into a guaranteed FEARNAUGHT spawn composition.
Client health, title, and shield status were fixed
Patch 0.05.005 fixes FEARNAUGHT's health bar, title, and shield status for clients. Before the fix, the host and clients could receive different or incorrect information. Current co-op calls should use the patched display, while any remaining mismatch needs a current version check and a new report.
This interface fix matters because a plan built on a bad health or shield state can fail even when communication is clear. Confirm that every player has the same game version, then compare visible states. The patch adds disconnect reasons for version mismatch and other session failures, which helps separate an interface disagreement from a connection problem.
Prepare around responsibilities, not a secret formula
Before the encounter, agree on movement calls, recovery ownership, the person watching additional enemies, and the condition that triggers a retreat or regroup. Check what resources remain without publishing a required quantity. Weapons and spells should have declared jobs so several players do not spend the same kind of answer at once.
The cannon has faster rotation and a larger projectile hitbox against bosses in the same patch, but that does not make it a required FEARNAUGHT counter. A party may not have it, the arena may demand another response, or a later build may adjust equipment. Use current options and keep at least one fallback.
Current evidence limits
No checked official source provides FEARNAUGHT health, damage, phases, shield duration, spawn interval, loot, drop rate, or a best composition. The page will not convert relative party scaling into invented numbers. It also will not assign the 0.05.006 Day 3 departure fix to FEARNAUGHT because that hotfix does not name the boss.
The build stamp remains part of every recommendation. If a later patch changes Holy Shield, spawns, or party scaling, the new record becomes current and this page should be revised. Patch 0.05.005 remains the dated source for the rules listed here, which lets readers distinguish a current claim from an old strategy that lost its version context.