On v1.3.5, the safest first party is not a launch-day “best build.” It is a six-skill loadout whose cards still agree with one another after the August combat rework. Give the party a way to create a status, a way to cash that status in, enough healing or shielding to survive the ten-second recovery cycle, and a clear plan for getting loot back to Emberwatch. If a guide shows fixed values from July, use its vocabulary only; read the numbers and conditions in your current client.
Current-build boundary: Skills & Raids launched on July 27, 2026. This guide was checked on August 13 against the official Steam metadata and announcement feed through the August 10 v1.3.5 fix. The large August 2 update changed cast times, cooldowns, healing, damage, enemy pressure, Mshard economy, and drop rates. Later hotfixes adjusted retreat, character selection, skill text, and a missing-quest case. The Steam screenshots are official, but some visible card values predate that rework. Whenever this article names a skill family, confirm the live card before committing resources.
Turn six slots into three jobs
Shelldon, Clawrk, and Owlivia each show two active slots in the current official interface. Do not judge those six choices one card at a time. Assign three jobs across the whole party:
- Setup: apply the condition that makes a later card stronger. The official UI shows examples built around Frostbite, Charged, Poison, Corrupted, and Empowered.
- Payoff: consume, repeat, or otherwise exploit that condition. A payoff with no reliable setup is a dead slot during its most important window.
- Recovery: heal, shield, cleanse, or reduce the damage taken while the important cards are unavailable.
A card belongs to the hero whose slot can equip it, but the combo belongs to the party. You do not need all three heroes to use the same element. You do need a reason for every status icon you are creating. If one hero applies Frostbite while the other four non-recovery slots care only about Poison and Corrupted, the Frostbite card must justify itself through its own damage or control.
| Question on the live card | Ready answer | Warning sign |
|---|---|---|
| What does this skill create? | A named status, shield, heal, Focus effect, or direct result the party needs | The effect is attractive but no later card refers to it |
| What makes it better? | A condition your other equipped cards can produce on demand | The required stack or status appears only on an unequipped card |
| How long are cast and recovery? | You know who protects the party during both windows | Several long casts begin together while no recovery tool is ready |
| Who can be targeted? | The target highlight matches the intended ally or enemy | You are relying on a portrait, range, or target rule the card does not accept |
| What changes at maximum Focus? | The extra clause solves a planned moment, such as cleansing | Focus reaches maximum and is spent on the first legal target without reading the bonus |
Read the v1.3 recovery cycle before pressing every key
The August 2 update was designed to slow skill spam and create more time for synergy decisions. It moved a large group of offensive, defensive, and status cards to a ten-second cooldown. The shorter six-second group includes Holy Surge and Putrid Mend. Frost Fang Strike and Life Drain share that recovery length, while Touch of Winter completes the five-card group. That distinction is more useful than memorizing a launch-week rotation.
Begin an encounter by pausing and checking the live cards. Identify which tools return in six seconds, which are on the longer cycle, and which require a 0.5-, 1-, or 1.5-second cast. The official rework put Fury Strike, Spear Thrust, and Thunder Strike among the half-second examples. That group also contains Conductive Surge, Freeze Frenzy, and Frost Fang Strike; the announcement assigns the same cast length to Ice Bash, BlightedScar, Decay Wound, and Life Drain.
The slower 1.5-second set spans several different jobs. Shield Burst and Purifying Chill are there, as are Haste Voltage and Shock Guard. The remaining named examples are Static Renewal, Corrupted Shield, Profaned Oath, and RotBloom. Rupture was separately set to one second.
Those groups describe the v1.3 announcement, not an eternal ruleset. The August 6 note changed the displayed text for Fury Strike and Haste Voltage, and v1.3.5 arrived four days later. Use the list to know what to inspect, then let the installed tooltip settle any disagreement.
Stagger commitments instead of creating a blank ten seconds
Do not fire every long-recovery card because all six buttons are bright. Start with the setup that determines the target, wait for the condition to appear, then commit the payoff. Keep at least one recovery action available until the enemy has revealed its own dangerous cast. When several party cards share a ten-second cooldown, spacing them by even one enemy action gives you more decisions during the gap.
A failed rotation has a recognizable signal: the party has spent Mshards, the enemy still lacks the required condition, and the only bright button does not solve survival. Pause there. Do not compound the error with another unrelated status. Re-establish the setup or defend until the intended pair returns.
Use the tooltip grammar to build real pairs
The official screenshots show how the game writes a dependency. The exact numbers visible in those marketing images may be old, but the conditional grammar is still the part to look for in the client:
- Septic Assault applies Poison and advertises an extra result when the target is already poisoned. That is a repeat-or-pair structure: first establish Poison, then use the condition-aware hit.
- Thunder Strike checks Charged stacks before producing its stronger control result. Do not spend the strike before the displayed threshold unless immediate damage is more important than control.
- Profaned Oath has one result when Corrupted is absent and a different result when it is present. It can participate in both setup and payoff, but only if you track the icon rather than pressing it on cooldown.
- Gods Blessing combines healing with Empowered and shows an additional maximum-Focus clause. Its best target is therefore a decision about health, the next skill, and Focus at the same time.
- Freeze Frenzy advertises Frostbite application. Pair it with a card whose current text rewards Frostbite, or treat it as a self-contained attack rather than assuming every cold icon is a combo.
One current player report describes finishing with both freeze and static effects, rotating freeze actions before using paralysis. That is useful proof that cross-area status packages can work, not proof of a universal best order. The same report notes that each of the four areas supplies skills and that each hero has two active slots. Your actual drops decide which complete pair is available first.
Pause to verify, then resume for one observable result
The official store describes pause as the place to read skills and status effects. Use it as a diagnostic screen:
- Hover the intended card and read its target, Mshard cost, cast time, cooldown, and conditional clause.
- Inspect the enemy and party status rows. Confirm the setup icon exists or decide that this cast will create it.
- Select the legal target and watch the highlight. The demo-era targeting indicator was added specifically to make valid recipients clearer.
- Resume long enough to see the cast complete, the resource change, and the expected icon or result appear.
- Pause again only if the result changes the next decision. On an easy encounter, let auto-attacks advance rather than turning every second into menu time.
This “one observable result” rhythm catches three different mistakes: an invalid target, a status that never landed, and a payoff spent before its condition. It also prevents the cursor effect from misleading you when a selected skill is unavailable; the August 6 hotfix specifically corrected that visual state when switching onto a card still in cooldown.
Make the tutorial produce a quest, a craft, and a return plan
The first loop is complete when you can explain what will happen to the loot before the next fight. The official store supports three quest families—target objectives, resource collection, and use of specified abilities—and says quests unlock equipment and skills. Do not rely on an unofficial claim that a fixed number of opening quests or a particular recipe must appear in a universal order.

After the tutorial, the current official notes say the crafting tab should open automatically. A separate July 31 fix repaired the crafting tutorial. Use that handoff as a checkpoint:
- Read the active objective before entering the map. If it names a skill, equip that skill now.
- Open the requested trade or craft and check the displayed resources, modifier slot, currency, and output. The live screen—not a rarity table copied from July—defines the cost.
- Keep quest resources separate from a speculative upgrade until the objective has accepted them.
- After crafting, read back the equipment or skill in the correct character tab. A successful click without the item appearing is not a verified upgrade.
If the first quest disappears because the game was closed with Alt+F4 during the opening lore text, update before deleting progress. v1.3.5 specifically fixes that path. Relaunch, confirm the current build has downloaded, and check Trade / Quests again. The settings screen contains a Delete Progress button, but the patch making that button larger is not a recommendation to use it as the first repair.
Separate backpack, safe pockets, Crow service, return, and retreat

The word “safe” is easy to overread. The July 30 official note states that using Retreat now costs both the backpack and the safe pocket, while skills and equipment are retained. That is the current explicit rule for retreat. It invalidates older advice that treats the pocket as protection during every exit method.
| Action | What the evidence establishes | How to verify success |
|---|---|---|
| Move to Safe Pockets | The item moves into a separate visible container | Reopen inventory and see it in the Safe Pockets grid; do not infer retreat protection |
| Send via Crow services | The action sends selected items toward the stash and has its own Steam achievement | Return to the stash view and confirm the delivered stack |
| Return to Emberwatch | The map presents a named return node; a safe return has its own achievement | The hub loads and the carried items appear where expected |
| Retreat | Current official rule: lose backpack and safe pocket, retain skills and equipment | Use only when preserving the equipped build matters more than carried loot |

Use Crow service when the selected cargo is worth securing and the run still has a supported reason to continue. Use Return to Emberwatch when the objective or resource state is already good enough. Use Retreat when the map or combat state makes a normal return unrealistic and you accept the documented loss. Do not choose among them by bag fullness alone; compare the quest state, equipped skill drops, carried resources, and distance to a known return.
Route by visible nodes, not a memorized map drawing
The map is not reliable enough for a permanent room-by-room route. A July 29 update added a chance for a Discovery Node to replace a combat encounter, explicitly changing node frequency. Current official media shows unknown nodes, a Crow icon, a camp-like icon, a combat node, and Return To Emberwatch. Plan from what the current map displays:
- Locate Return to Emberwatch before moving away from the known route.
- Identify whether a Crow service or other support node can secure the resource that just dropped.
- Read the active quest and decide whether the next unknown node can complete it or merely adds risk.
- Before a combat node, inspect the six cards and preserve the recovery tool that answers the likely status family.
- After the fight, re-evaluate. The August skill rework increased skill-drop chances in Sinking Graves, Cold Peaks, and Edge of the Abyss, so a single useful drop can be a valid reason to end a run.
Do not import the old “healing nodes restore exactly half” rule into current planning. That was a demo value, and the July 29 full-release balance note says healing nodes were reduced. Read the recovery shown by the current build and make the continue-or-return decision from the actual party bars.
Use current fixes as a troubleshooting decision tree
Several failures that look like a bad build are known state problems with official fixes:
- The party cannot be selected after a run: v1.3.2 fixed this exact post-run selection case. Update and reproduce once from a fresh launch.
- Retreat behaves incorrectly in combat: v1.3.1 and the large v1.3 update both mention retreat fixes. Confirm the current build, then remember that the intended loss rule still removes backpack and safe pocket.
- The map will not move after combat: the big skill update fixed an intermittent post-combat map lock. Restart after updating before treating the save as broken.
- The opening quest never appears: v1.3.5 targets the Alt+F4-during-lore path. Update, relaunch, and inspect Trade / Quests before using Delete Progress.
- The selected-skill cursor effect remains active: the August 6 minor fix turns it off when the replacement skill is still cooling down. Let the visible cooldown and card state, not the cursor particles, decide availability.
- A skill behaves unlike an old guide: v1.3 changed many cast times, cooldowns, costs, heals, and damage values. Rebuild from the installed card instead of forcing the obsolete sequence.
Stop the first session at a verified checkpoint
A good first session does not require a late-zone clear. Stop when all of these statements are true:
- each of the six equipped cards has a defined setup, payoff, or recovery job;
- you have watched one status condition appear before spending its payoff;
- the first quest or requested craft has been read back in the correct screen;
- you can distinguish a Crow send, a normal return, and a loot-sacrificing retreat;
- a useful drop, quest item, or crafted result is visible in its expected hub container;
- any failure has been compared with the v1.3.1–v1.3.5 fixes before progress is erased.
From that checkpoint, improve one dependency at a time. Replace a setup only when its payoff also changes, lengthen a route only when the return is still visible, and treat every patch as a reason to reread the six live cards.
Sources and version boundary: game identity, scope, mechanics, and official media were checked against Skills & Raids on Steam. The skill rework, current retreat loss rule, drop changes, tutorial behavior, and v1.3.1–v1.3.5 fixes were checked against the developer’s official Steam announcements. Current player observations were used only where they corroborated visible two-slot, area, status, and progression behavior.