Boss strategy · reviewed 2026-07-25
Imaru Boss Guide
Prepare for Imaru in RuneScape Dragonwilds with current health and weakness data, named rewards, a safe learning sequence and co-op checks.
Boss strategy answer
Imaru is recorded in Fellhollow with 14000 HP and a No weakness recorded weakness status. Plan for a long fight and keep the live objective visible because a weakness is not currently recorded.
Boss data card
| Encounter region | Fellhollow |
|---|---|
| Recorded health | 14000 HP |
| Recorded weakness | No weakness recorded |
| Named rewards | Imaru's Head |
Preparation loadout
Bring sustainable food, repair margin and an escape route. Plan for a long fight and keep the live objective visible because a weakness is not currently recorded. Do not copy a build from a different boss merely because both share a creature family: health, arena pressure and weakness records differ.
- Repair the primary weapon and armour before travel.
- Carry a second damage option if the weakness is unrecorded or the live feedback differs.
- Move quest items and unrelated resources into storage.
- Set a nearby recovery point without blocking the encounter area.
Safe learning sequence
- Enter with full health and stamina; observe the opening without committing to a long animation.
- Test the recorded weakness and compare the visible result with the backup weapon.
- Use one attack window at a time until the current pattern is understood.
- Heal only after creating space, then resume with enough stamina to dodge or block.
- After victory, verify the objective and collect Imaru's Head before leaving or resetting the area.
This sequence is deliberately version-safe. It does not claim exact telegraph durations or phase thresholds that the current evidence does not support.
Solo and co-op checks
Solo players should favour repeatable openings over maximum theoretical damage. In co-op, agree on aggro, healing and loot handling before the pull, and make sure every player is inside the encounter boundary. If the boss health or behaviour appears inconsistent, first confirm that clients and the host or dedicated server run the same patch.
For a failed attempt, identify whether the cause was incoming damage, stamina depletion, equipment durability, environmental pressure or an incomplete progression trigger. Change one variable at a time; replacing the whole loadout makes the next result harder to interpret.
Continue planning
Compare this entry with the enemy database, prepare equipment in the combat hub, and check the resource index before committing rare supplies. Record the installed game version whenever a live value differs from this dated page.