Your first campaign build ends sooner than you expect. The Backwaters explicitly requires a fresh SHRIMP platform for each new world, so the platform that just survived a boss is not the one you automatically take into the next domain. Treat every return to the hub as a new loadout decision: choose a body whose weak stat matches the next problem, choose an element with a purpose, and rebuild from the drops inside that world.
This guide is bounded to the Windows launch build released on August 27, 2026 and checked on August 28. It follows the connected first-clear loop through the hub, upgrades, elemental stones, pearls, bosses, and extraction. It does not claim a full recipe chart for all elemental fusions or a complete seven-world walkthrough; the available launch footage reaches the later campaign but ends before a verified final clear.

The altar is the real start of every world
The campaign is not one long roguelite run. After the opening domain, the Backwaters tells you that each new world needs a fresh platform and points you to the SHRIMP altars around the hub. The Steam page lists 11 platforms, each with different strengths and play styles. That makes the altar a world-by-world draft rather than a cosmetic selector.
Use this order before entering a portal:
- Read the new world assignment. The hub dialogue identifies the environmental problem and gives you the next campaign direction. Do not enter the nearest side portal just because it is active.
- Inspect the platform card. Compare its starting speed, handling, armor, and offensive profile with the problem that stopped the previous attempt. A high-damage platform can still be a bad answer to a boss that repeatedly leaves your effective range.
- Choose the base element deliberately. Fire, Ice, Light, Dark, Wind, and Earth are the six launch classes. Your first element shapes the early abilities; a later elemental stone can turn it into a fusion.
- Confirm the selected platform at the altar. The platform change and the world portal are separate interactions. If the destination loads with the wrong body, you finished the portal interaction but not the altar decision.
One launch-day run demonstrates why this reset matters. A platform with maximum firepower cleared ordinary enemies quickly, but low handling and speed remained noticeable. The next hub visit was used to correct movement instead of blindly rebuilding the same damage stack. That is the useful habit: carry the diagnosis forward even though the old platform stays behind.
Upgrade the problem you can name
Level-up choices often raise one or two stats while lowering another. Read the entire card before accepting it. A green increase is not automatically an upgrade if its penalty removes the stat keeping the current weapon usable.
| What is failing now? | What to protect or raise | What to stop buying | Readback after the choice |
|---|---|---|---|
| A moving boss repeatedly leaves your range | Speed, boost, and enough armor to survive a failed approach | More firepower on a shot that rarely connects | You can close the gap without spending the whole attack window travelling |
| The weapon hits hard but feels difficult to place | Handling and the stat shown on the weapon or upgrade card | Tradeoffs that reduce handling for damage you already have | Your next burst lands without a wide correction or overshoot |
| Side enemies interrupt every boss attempt | Reliable fire rate or area control, then defenses | Single-target greed while the arena is filling | You can clear a side lane and return to the boss before the next major attack |
| One arena pattern nearly removes the health bar | Armor, vigor or health-facing options shown by the current card, plus movement | A minor damage gain that does not reduce the number of boss cycles | The same mistake no longer ends the attempt immediately |
Do not turn this into a permanent stat tier list. The launch footage shows drops that combine values such as firepower, fire rate, handling, dexterity, trajectory, speed, armor, vigor, body, boost, and luck in different packages. The correct comparison is the current platform plus the current weapon plus the next arena. When firepower is already capped, another damage-positive card may be worth less than a modest movement repair.
Pickups also require close positioning in the launch build. Players reported that the interaction point could feel lower or narrower than expected, and the developer said the hitbox height would be increased. Until a patch changes it, approach the item itself and watch for the interaction response rather than assuming the drop was collected from nearby.
An elemental stone is only half the class change
The class flow has two visible confirmations. First, the game announces that an elemental stone has spawned and instructs you to absorb it. Later, a fusion stone appears and the new fusion name is shown. If you saw only the first message, do not write the fusion into your build plan yet.
Three same-element cases are visible in the verified launch run: starting Light and completing the stone sequence produced Light+; repeating Ice produced Ice+; repeating Wind produced Wind+. Those observations support a safe rule for a focused first clear: if you want the strengthened version of the class you already understand, keep the second element the same and wait for the fusion readback.
Mixed fusions are real—the Steam achievements name Crystal, Fossil, Magma, Glacier, Solar, Steam, Blast, Demon, Sand, Lunar, Aurora, Lightning, Abyss, Smog, and Blizzard—but the achievement list does not state their ingredient pairs. Do not spend a run following an unverified recipe copied from a title-only list. If you experiment, record three things before replacing the ability: the starting element, the absorbed element, and the fusion name that actually appears.
A practical fusion test looks like this:
- enter the world with a base ability you can already use under pressure;
- keep one weapon slot reliable while testing the elemental ability;
- absorb the announced stone only when the arena is safe enough to read the result;
- do not call the build finished until the fusion stone appears and the HUD shows the new ability;
- use the next ordinary enemy group as the test, not the domain boss.
This separates a failed recipe from a failed execution. If the expected fusion name never appears, the ingredient sequence is the question. If the name appears but the ability misses, the problem is positioning, range, energy, or the chosen platform—not the recipe.
Pearls, masks, NPCs, and exits are four different jobs
Several interactables use similar portal imagery but advance different states. Mixing them together is the main reason a productive exploration session can feel like no progress.
| Object or message | Its job | What proves it worked |
|---|---|---|
| Mask and shrine objective | Advances a local world objective and can lead toward the domain encounter | The objective text changes or the next encounter activates |
| Mirror, bell, color, or shape puzzle | Provides exploration progress and can award a pearl | A puzzle completion response or pearl pickup appears |
| Named SHRIMP or side portal | Handles a character quest, platform unlock, or optional otherworld route | The NPC dialogue changes, an achievement unlocks, or a new portal opens |
| Post-boss exit portal | Extracts the current platform from the campaign world | The game says the domain boss is defeated and tells you to enter the portal |
Pearls are not generic experience. In the observed Sunken Polis route, the player identifies three pearls as the puzzle requirement and later meets an NPC who offers to take a pearl to open another portal. That is an optional transaction, not the same as the domain extraction. Before spending, check whether your current objective still needs a pearl count and whether the NPC is opening a side destination rather than the campaign exit.
Mirror puzzles deserve a separate control check. The reflectors themselves rotate; aiming the SHRIMP at a fixed mirror does not replace rotating the object. Trace the beam one reflector at a time and stop after each successful contact. When a fourth mirror is not lighting, return to the previous mirror and confirm its outgoing beam rather than changing every piece at once. The verified run eventually used the mirrors as a chain, but it does not establish one permanent color/shape solution for every world, so this guide does not invent a universal code.
Boss fights punish the same three mistakes
The launch campaign changes arenas and bosses, but the failed attempts point to three recurring errors.
Tunnelling the health bar while adds own the arena
The first observed boss becomes harder when side enemies are allowed to keep firing. Stop attacking the boss long enough to clear a lane, then return to damage. Area attacks are valuable here because they control the approach while still touching the boss. The success signal is not maximum damage per shot; it is a predictable side of the arena from which you can read the next boss cue.
Building damage for a target you cannot reach
The electric eel encounter exposes slow builds. The boss moves away, while a large beam or surrounding attack punishes a late approach. If you spend the whole window chasing it, buy speed and survivability before more damage. Enter the next attack cycle from a position that lets you close diagonally or from cover, land the short burst you already own, then disengage before the global pattern resolves.
Standing in the arena without identifying the shelter
Later encounters use large attacks that make the safe space the real objective. If the question becomes “where am I supposed to hide?”, stop shooting and read the geometry: holes, height changes, walls, or the side opposite the incoming effect. A run that finds a repeatable shelter can win with average damage; a run that ignores the shelter spends upgrades trying to out-stat a positional mechanic.
After the kill, wait for the explicit message that the domain boss is defeated and the portal can be used. Loot inspection and weapon comparison belong after that readback, not while surviving enemies are still active. If the message never appears, one add may remain, the boss state may not have registered, or the session may have hit the launch co-op problem described below.
Use extraction stamps to locate the campaign state
Steam’s 60-achievement list includes seven campaign extraction stamps. Their unlock-rate progression and the observed launch run align in this order:
- Primeval Canyon
- Hotrock Spires
- Sunken Polis
- Grand Ice Shelf
- Whirlshaft Tower
- Abyssal Tunnels
- The Void
Use the achievements as readbacks, not as walkthrough steps. An extraction stamp proves that the world ended successfully; it does not prove that every pearl, side quest, SHRIMP unlock, or fusion inside it was collected. The verified RogueHeavy footage reaches the first five named regions and begins the later campaign route, but the recording ends before a verified final extraction. That is why this article stops at a reusable campaign method instead of supplying made-up Abyssal Tunnels or Void directions.
The developer describes the main campaign as roughly three to four hours, with completionist play extending it. Your first clear can take longer because puzzles, optional NPCs, weapon comparisons, deaths, and co-op interruptions all sit outside the fastest extraction line. Do not use a stream duration as a promised campaign length.
Launch-day co-op locks are not secret objectives
As of August 28, players have reported a boss dying while the host remains outside an invisible barrier or loses the ability to interact. The developer asked for the affected world, boss, and host state, including whether the volcano hermit was involved. No confirmed universal fix was posted in the readable thread.
If this happens, separate a bug from normal progression before abandoning the run:
- check whether the “domain boss defeated” message appeared;
- confirm that no surviving enemy or objective marker remains inside the arena;
- have the host test the menu and interaction input while clients stop moving through the barrier;
- capture the world name, boss, who hosted, whether the host was inside or outside the arena, and whether the exit portal existed;
- if the host still cannot interact, treat it as a failed session state and report it rather than searching for an undocumented lever.
Quitting to the menu was the only action an affected player said remained available, but the thread does not prove what progress that preserves. Do not promise that quitting, re-hosting, or changing platforms will recover the same checkpoint until a current patch or developer note confirms it.
Run the same eight checks before every portal
- Read the current world assignment in the Backwaters.
- Select a fresh SHRIMP platform whose weakness does not repeat the previous failure.
- Choose one of the six base elements and decide if you are testing it or relying on it.
- Keep a dependable weapon while the rest of the build is still changing.
- Read both the gains and penalties on every upgrade card.
- Track masks, puzzle responses, pearls, NPC transactions, and the exit as separate state checks.
- Confirm the elemental-stone and fusion-stone messages independently.
- After the boss, leave only when the game explicitly marks the domain defeated and the exit portal is active.
The video below was independently verified through YouTube metadata as Shrimp Game Overkrill!! and Going Godzilla mode in Beastlink by RogueHeavy, published on August 27, 2026. It is a commentary-heavy launch stream with breaks and no chapters, not a clean full walkthrough. Use it to see the altar reset, upgrade tradeoffs, Light+/Ice+/Wind+ readbacks, mirror interaction, several domain bosses, and extraction messages; do not use its ending as proof of a completed campaign.
Sources and verification boundary
Identity, launch date, developers, platforms, elements, platform count, weapons, features, and official screenshots were checked against the Steam store page and appdetails response. World extraction names, fusion names, and quest labels were checked against the Steam achievement list. The August 27 launch and planned post-launch bug-fixing window were checked against the game’s Steam announcements. Campaign mechanics and failure signals were limited to the verified launch stream and readable Steam community reports; demo-era pearl-count advice was excluded because it was not shown to remain current in the retail build.