Ironsand does not bind a character, an active skill, and a weapon into one traditional class. The launch-build lobby presents those choices separately, then asks the player to assemble temporary perks inside each mission. If the first run feels weak, changing the named “class” is usually the wrong response. First identify which layer failed: the character’s baseline, the equipped skill, the current firearm, the run cards, or the mission objective.
This route follows that decision chain through the first two Titan encounters and into Cannon Preparation. It is not a room-by-room full-game walkthrough. The verified recording ends just after the cannon objective begins, and eight rapid post-launch hotfixes changed saving, quest feedback, performance, the Uzi, and navigation. The checkpoints below therefore explain what to read on the current screen, what to preserve for the next phase, and which old claims should be ignored.
The lobby loadout is three decisions, not one class pick
Open the lobby panel and read the labels literally. In the verified release footage, Huntress occupies the Character slot while Engineer occupies the separate Skill slot. The Engineer description on that screen is a timed automated turret, not a complete character identity. This matters because a durable character can carry an offensive skill, while a faster character can take an area-control skill. Do not let a guide that calls Engineer, Medic, Defender, and Berserker four fixed classes decide the build for you; that model conflicts with the release UI.
Use the character panel to identify the baseline you are actually buying. It exposes health, energy shield, block chance, speed, dash cooldown, axe damage, reload-speed modifier, and experience gain. A new portrait is worthwhile only if those live values solve a named problem. If the last attempt ended because a global warning caught you with no dash, compare mobility and defense. If it ended because ordinary rooms took too long, inspect weapon handling and experience gain. A locked portrait with a larger price is not automatically an upgrade for the current run.
Next, choose the skill by the job it must perform. The Engineer turret is useful when the player needs damage to continue while moving, interacting, or hiding from a Titan warning. Another skill may be better when the build already clears rooms but lacks recovery or a panic button. Finally, leave optional difficulty modifiers off for the first progression attempt. The lobby can separately toggle conditions such as Reinforced Titans, Cultists, Long-Eared Special Forces, Orbital Danger, and Shadow. Turning several on before learning the normal combat rhythm makes every later adjustment harder to evaluate.
Separate permanent progress from the mission build
Ironsand runs two upgrade economies at the same time. The ship holds persistent character purchases, a skill tree, unlock quests, and currencies carried out of completed missions. The operation supplies level-up cards, equipment offers, element changes, weapon finds, and combat resources that shape the current attempt. Spending in one layer does not repair a bad choice in the other.
- Before departure: confirm the character baseline, active skill, room privacy, and modifier state.
- During rooms: make one temporary build coherent enough to clear crowds and still move during Titan attacks.
- Back on the ship: buy persistent value only after checking the quest and skill-tree screens, then rebuild the lobby loadout deliberately.
The persistent skill tree in the checked build is divided into Rage, Weapon, Abilities, and Survival. A first point that prevents the next death is more valuable than spreading currency across four headings. If room clears are safe but the Titan takes too long, inspect Weapon or Abilities. If the health and shield bars collapse before the player can reach cover, inspect Survival. Rage is not a substitute for correcting a movement failure.
Temporary cards should form a plan before they form a collection
Level-ups present three cards with names, effects, rarity frames, and a visible level. The release recording shows offers such as Poisoning Grenade, Softpaw Alliance, and Bloodlust on the same screen. Those are three different jobs: broader explosive control, more Long-Eared support, and close-range damage. Choosing all three because they are new produces a busier HUD, not necessarily a safer build.

Name the next threat before clicking:
- If small enemies are crossing the room faster than the firearm can clear them, add area control or an automated source of damage.
- If a Titan warning forces long periods without firing, prefer effects that keep working while repositioning or improve the survival window.
- If the build already controls space, strengthen the same damage condition rather than opening an unrelated fourth condition.
- If an effect requires close range, verify that the character’s shield, block, speed, and dash can support that distance.
Official development notes describe three broad elemental families – Flame, Lightning, and Cold – and distinguish high point-damage, rapid-fire, and area-damage weapons. Treat those as build questions, not as a permanent tier list. Check the element changer and each current tooltip for the values that apply now. Hotfix 5 changed the element changer’s feedback, and Hotfix 8 converted the Uzi to a heat system, so launch-week ammo advice for that weapon is already stale.
A weapon find is a trade, not a trophy
The verified HUD and pickup interaction present one active firearm alongside the character’s axe. When NEW WEAPON FOUND appears, stop before interacting. Compare the offered weapon with the job the current cards are already performing. A revolver can improve deliberate single-target shots but may reduce the safety margin against a dense room. A launcher can solve clustered enemies but makes a close obstacle or ally a reason to hold fire. The right pickup is the one that preserves the build’s answer to the next room and the next Titan.
Use a four-part check at every weapon or equipment station:
- Range: can the weapon work from the cover position the coming fight provides?
- Output pattern: does it deliver point damage, rapid pressure, or an area hit?
- Handling: what happens while it reloads, cools, or runs dry?
- Existing effects: will the current element and cards trigger reliably with that firing pattern?
The release footage also shows armor offers and an elemental-damage reroll station before a late room. Do not spend there simply because the station appeared. Buy armor when its live comparison protects the failure window. Reroll an element when the result completes a build, not when it erases several rooms of useful synergy for an untested color.
The room is finished only after the exit and resources are read back
Combat rooms close the forward passage, then display THE PASSAGE TO THE NEXT ROOM IS OPEN when the blocking wave is resolved. A yellow objective marker points onward. That message is the signal to switch from combat to audit: reload, inspect health and shield, collect nearby currencies, check for a weapon or equipment interaction, and only then cross the threshold. Running toward a closed marker wastes dashes and exposes the player to the last turret or flanker.

Enemy families demand different movement even when the objective is unchanged. A laser or grenade-launcher flying turret makes open ground expensive. A shielded ground target makes frontal fire inefficient. Arakh and other fast enemies punish a long reload taken in the middle of the lane. Break the room into two jobs: remove the enemy that controls movement, then finish the enemy that merely survives longer. The kill feed is useful evidence; if Long-Eared allies or a turret are clearing small targets, the player can spend attention on the weapon system that is actually locking the route.
Hotfix 8 added a minimap after the verified video was recorded. Use it to confirm the next room and nearby route structure, but do not read it as a promise that an uncleared space is safe. The store also describes the environment as destructible. A wall or bridge can become a weapon, but it can also stop being cover. Before firing explosives near a defensive position, identify a second path out.
The first Titan is a mobility exam with a damage requirement
A Titan health bar changes the scale of the fight, not the rules that kept the run alive. The official store names turret fire, missile barrages, pulse attacks, and heavy artillery as Titan attack families. The verified first encounter also displays a full-screen red warning during its dangerous sequence. None of that proves that every Titan uses one fixed order or that every glowing component is a permanent weak point.
Run the encounter in three modes:
- Readable pressure: fire from a position that still shows the boss and one escape lane. Let turrets, damage-over-time effects, and Long-Eared support contribute.
- Global warning: stop treating damage as the goal. Leave the center line, break sight where solid cover remains, and preserve a dash for the final displacement rather than spending every charge at the first flash.
- Recovery: reload and re-establish the camera before returning to damage. A boss that leaves the reticle is more dangerous than a few seconds of lost output.
The failure screen tells you which layer to change. Dying while reloading in ordinary pressure is a weapon-handling problem. Dying with unused movement or defensive skills is an execution problem. Reaching the warning with no dash is a build or cadence problem. Losing all cover after firing an explosive into the arena is an environment problem. Only the first of those is likely to be solved by replacing the firearm.
The ship visit converts observations into unlocks
After a mission, walk the ship before launching again. The checked Quests screen ties specific combat accomplishments to skills and weapons. Visible examples include destroying a Turret Droid for the Engineer skill, axe kills for a machine gun, toxic-enemy kills for other weapons, finding every resource crate on the first level for a plasma machine gun, and destroying a Spider Mech for another unlock. These are long-term targets, not instructions to sabotage the current clear.
Pick one quest whose requirement fits the operation already being played. If the run naturally meets Turret Droids, let that progress unlock Engineer. If the character is not safe in melee, do not force hundreds of axe kills during a progression attempt. A resource-crate quest rewards a slower post-room audit, while a named-boss quest belongs to the route that reaches that boss.
Hotfix 6 fixed a case where a quest could fail to trigger even though the corresponding Steam achievement had unlocked. If the Quests screen still disagrees with an achievement, update the client first, return to the ship, and read the counter again. Repeating an old requirement before checking the hotfix state can waste an entire run.

The second Titan asks whether the build still has an identity
The verified second operation begins with Huntress and Engineer, no optional modifiers, and the same closed-room progression. Its level-up offers mix defense, movement, axe control, ammo recovery, and skill-triggered weapon damage. That variety is a trap if every offer becomes a new plan. By the time the second Titan appears, the build should be describable in one sentence, such as “turret pressure while the player stays mobile” or “safe ranged damage with a defensive reset.”
The second Titan again creates a red global-danger phase, but the arena geometry and attack source differ from the first fight. Reusing the exact dodge path is less reliable than reusing the decision order:
- Find the solid structure that survives ordinary fire.
- Keep a line that lets the boss remain visible without standing at the center of the arena.
- Place automated damage where it can work through the player’s movement phase.
- When the global warning appears, move first and confirm safety before resuming fire.
- After the warning, clear the target that prevents recovery, then return to the Titan.
If the first Titan fell but the second does not, do not assume the game demands a larger permanent grind. Check whether the firearm lost its fit with the temporary cards, whether too many card picks opened unrelated conditions, and whether the new arena removed the safe range used in the first encounter.
Cannon Preparation reverses the mission rhythm
After the second Titan in the verified route, an interaction panel announces LOAD THE CANNON and offers to start the mission. The next screen replaces forward-room progress with a CANNON PREPARATION percentage. An official development post describes the Arena as a defense objective where a massive cannon charges while endless waves try to stop it. This is the point where a forward-push build must be reviewed before activation.
Do not start the cannon simply because the button is available. Reload, compare the nearby weapon offer, inspect the temporary build, and decide how the objective will stay protected while the player answers threats. Area control and sustained effects become more valuable because enemies come to the defended space. Mobility still matters, but a long chase away from the cannon can be a loss even when it ends in a kill.
For co-op, assign jobs without pretending they are fixed character classes:
- Objective anchor: stays close enough to see the cannon percentage and calls when the pad is being overrun.
- Lane control: removes the wave that can reach the objective fastest.
- Heavy-target pressure: preserves high-value damage for armored enemies or the Titan rather than spending it on the first small target.
- Recovery and flex: covers a failed lane, a revive window, or the escape route during artillery.
Character, skill, weapon, and card choices can fill those jobs in different combinations. In solo play, combine anchor and lane control first; a slower but self-sustaining build is more useful than a burst setup that must leave the objective to recover. The supplied video stops near the beginning of Cannon Preparation, so this guide does not invent a fixed charge time, wave count, or complete Arena clear.
Know which progress the current build actually saves
Launch footage and early discussions predate the current safety systems. Hotfix 4 added automatic single-player saving after a crash and at the end of each mission. Hotfix 8 added the ability to continue a co-op run solo after a disconnect or crash. Those notes do not promise a manual save in the middle of any room or a free checkpoint during Cannon Preparation.
Plan around the confirmed boundary. If a single-player mission is stable and near completion, finishing it reaches the documented save point. If co-op breaks after Hotfix 8, look for the solo continuation before abandoning the run. If the client is older, update before using any recovery advice in this guide. The live client, mission-end transition, and current official hotfix notes override launch-week recordings.
Watch the verified first-run checkpoints
The embedded recording was independently matched to IRONSAND – Full Gameplay Walkthrough Part 1 [FULL GAME] No Commentary by Zish Gaming. YouTube reports a 3,468-second duration, and the supplied 854×480 local file is 3,467.768 seconds, matching the public video within normal container rounding. Visible checks include three-card level-ups, weapon and equipment interactions, the first two Titan encounters, the ship’s Character/Skill/Quests screens, and the beginning of Cannon Preparation.
The video was uploaded on August 21, 2026 and therefore does not show the minimap, current Uzi heat system, end-of-mission single-player save change, or co-op-to-solo recovery added later. Use it for the verified route and UI relationships, but check current values and menus against Hotfix 8.
Current-build boundary: Hotfix 8 on September 1, 2026
Ironsand is Steam App 2454600, developed and published by Renderise and released for Windows on August 20, 2026. Steam lists single-player, multiplayer, and online co-op support. The official page describes four-player role synergy, Titan attack families, run-based weapon and character upgrades, destructible environments, and Long-Eared allies.
Hotfix 8 is the cutoff for this guide. It added the minimap, reworked the Uzi around heat, enabled solo continuation after a co-op disconnect or crash, adjusted recoil and weapon audio, and included additional stability changes. Recheck current tooltips and later official notes before relying on a weapon’s firing economy, an upgrade value, a quest trigger, a save boundary, or a modifier interaction.
Sources and credits
Identity, release metadata, supported modes, official screenshots, and the high-level Titan, progression, environment, and Long-Eared systems were checked on the official Ironsand Steam page and its public app data. The current boundary comes from Renderise’s official Hotfix 8 announcement, with saving, quests, elements, and Arena behavior checked in the official news archive. Route details and UI relationships were independently sampled from the verified walkthrough recording above. The four selected pictures remain byte-original JPEG downloads from Steam.