How to Fish Bosses

Reported boss trigger ledger

Pufferfish community strategy

Community strategy / Limited confirmation: one player described circling the Grill while shooting and avoiding a direct charge. Read the Pufferfish Boss Guide for the source boundary, preparation checklist and what has not been verified.

Patch 1.0.12's official balance note concerns Piranha—not Pufferfish.

Giant Piranha and Patch 1.0.12

Official / Verified: Patch 1.0.12 says Piranha was rebalanced, but publishes no health, damage or timing values. The reported Forest trigger is Modified Leech. See the Giant Piranha Boss Guide for the exact limits of those two claims.

Final Boss explosive damage in Patch 1.0.12

Official fix in Patch 1.0.12 / Practical outcome needs retesting: the Final Boss should now take damage from explosives when it lands on its tail. This specific wording does not establish explosive damage for every boss, body part, phase or older speedrun route.

Official / Verified in Patch 1.0.11: disabling Friendly Fire does not prevent damage from your own explosives. Leave enough time and space to move away before detonation, and re-verify placement, timing and any escape route before using explosives against the Final Boss, Albatross or another boss.

Community-reported / Unverified: community hitbox reports and older safe positions still need current-build testing. The official notes do not define explosive quantity, placement, timing or a safe standing position, so none are presented as guaranteed strategies.

One co-op player cannot see the Albatross

Community-reported / Limited repeated confirmation: a Reddit report provides one Albatross-specific co-op sample. An earlier Steam report about a co-op boss being invisible only supports limited repetition of the broader boss-visibility symptom; it does not independently confirm another Albatross case or a shared root cause.

When reporting the issue, record:

• who was host and who was client;
• which player triggered the boss;
• whether the invisible player could see a boss health bar;
• whether the boss could attack that player;
• whether that player could deal damage; and
• whether visibility changed after re-entering the session.

No confirmed workaround: reconnecting, resummoning, changing host, restarting the fight or re-entering may be useful observations to record, but the reviewed reports do not establish any of them as reliable fixes.

Before testing a boss route

1. Match the quest state. A correct-looking trigger can still fail when the related hand-in or dialogue has not advanced.
2. Protect progression. Use the platform's normal backup process before experimenting with a save-sensitive fight or hand-in.
3. Prepare for the current difficulty. PATCH 1.0.9 changes creature health and damage on Easy and Hard, so timing from another difficulty is not directly comparable.
4. Test one variable. Change the trigger, position or equipment separately so a successful attempt is reproducible.

Common reasons a reported route fails

• The guide did not state its game version.
• The active quest or prior boss state differs.
• A trigger name is being treated as a conventional lure when it is a special object.
• A co-op host and joining player have different progression state.
• A reward or follow-up step was assumed from a video rather than verified.

Related: Patch notes, Islands, Weapons, Beginner Guide, Multiplayer Known Issues, and Achievements.