Castle Story asks you and your friends to build a fortress from individual blocks while a hostile force tries to reach the crystal at its center. You command Bricktrons, small stone-bodied workers who can dig, gather resources, raise walls, and take up arms. In Co-Op Invasion, players control the same crew and defend one shared Home Crystal against waves of Corruptrons. Sandbox multiplayer lets the group build without those attacks, while Conquest turns the same construction tools toward a fight between rival factions.
The central co-op mechanic is shared control. In standard Invasion, everyone uses the same Bricktron crew and settlement; there are no separate armies or castles. Orders and blueprints enter one common work queue, so a mining task and a wall design affect the same base. Each player sees the same unfinished jobs and the same changing battlefield. The teamwork comes from directing one small workforce together, not from choosing complementary hero classes.
One island, one workforce, many jobs
The game begins on a floating island with a Home Crystal, a small number of Bricktrons, and resources embedded in the landscape. Workers can harvest timber and mine stone, and your group uses those materials to build structures and defensive tools. Digging also changes the island itself, opening routes through hills or exposing more resources. The map is not just a flat board beneath your castle: excavated ground and raised construction help shape how the settlement grows. The built environment is not decorative: support, height, doors, bridges, and narrow passages change access and structural stability. Timber and stone feed construction, while wisps collected across the island enable additional Bricktrons to spawn from the Home Crystal. The shared map therefore supplies both building materials and the workforce used in defense, tying resource gathering directly to the size of the available crew.
Construction is block by block. You lay out a blueprint for a wall, tower, staircase, doorway, or other structure, then the Bricktrons carry materials and complete it. The physics system gives that placement a practical consequence. A tall tower can fall if its base is destroyed, so a fortification’s shape and supports matter as much as its height. Catapults launch explosive barrels, doors and bridges affect access, and traps or narrow passages can turn enemy movement into part of the defense.
Bricktrons start as workers, but the settlement can turn some into soldiers. Available roles include shielded Knights, cheaper but less-armored Halberdiers, ranged Archers and Arbalists, healing Artificers, and bomb-throwing Alchemists. Changing those roles means equipping units with different weapons and armor, so the group’s defenses grow out of its production and equipment rather than a character selection screen. Workers still have value when danger is close: they can repair walls and carry on with their tasks, though they are weaker fighters than dedicated units.
The Home Crystal connects growth to survival. New Bricktrons spawn from it after enough wisps are gathered. In Invasion, Corruptron waves attack the crystal or other targets and continue without a fixed final round; the run ends when the defense is overwhelmed.
Preparing that defense means choosing how the same crew is equipped. A Knight can absorb more damage while holding a position; an Archer or Arbalist can fire from a wall or tower; a Halberdier is a lighter melee defender. Other roles add support through an Artificer who can heal nearby units while stationary, or an Alchemist who throws explosive bombs. Those jobs are not fixed characters with personal skill trees: you change Bricktrons by equipping armor and weapons. A high wall may shelter ranged units, while a narrow doorway gives melee fighters a place to hold. Construction and unit preparation therefore feed into the same question: what kind of defense can this island support before the next attack?
Invasion keeps construction, resource gathering, and unit equipment inside one settlement rather than separate bases. Every blueprint belongs to the same build queue, and terrain changes can reshape access across the island. Digging may open or expose a route; moving a resource point, adding a bridge, or changing a wall can alter how units and enemies move through the space. The physics system also means that completed structures need support to remain standing. The shared island and its connected jobs are the focus, not parallel private build areas.
Co-op shares one crew and settlement
Co-Op Invasion is the clearest PvE mode for friends. Corruptrons arrive in waves and attack the Home Crystal or other targets while one shared Bricktron crew gathers, builds, equips units, and fights back. The same base and worker pool serve every player. A mining route can expose a flank, an unfinished wall can leave a gap, and units focused on one threat can leave another approach open; those consequences come from the settlement and its task system, not separate player objectives.
The common crew makes cooperation direct and can also make the controls feel crowded. Every player issues commands to the same worker pool, and construction jobs compete for its time and materials rather than running in private queues. Multiple blueprints, resource tasks, and unit orders all affect the same base. Because digging and building change both terrain and access, a completed wall or bridge can alter paths across the island. Shared control is therefore the defining constraint and feature of Invasion: the whole multiplayer session operates through one settlement.
Blueprints are work orders rather than instant structures: Bricktrons carry wood and stone to a marked site and complete the build there. The shared workforce also handles mining and repairs, while weapons and armor change unit roles. Production and defense therefore draw on the same workers and materials. Invasion’s pressure comes from managing those connected systems as Corruptron waves continue without a fixed final round. Sandbox uses the same construction tools with the enemy waves removed. The Home Crystal is both the objective under attack and the point from which new Bricktrons spawn after enough wisps have been gathered.
Some community mods change Invasion so that players have separate crystals and Bricktron crews. These setups require matching files for everyone and can be buggy; the base game uses one shared crew.
Sandbox removes the Corruptrons and enemy waves, leaving multiplayer construction as the focus. Catapults and explosive barrels can still be used against other players. The mode has no escalating survival pressure or separate campaign progression.
Competitive modes use the same building tools
Castle Story also includes multiplayer that is not cooperative. Conquest asks factions to spread across an island, capture shards, and defend their Home Crystals. Capturing territory can support a larger Bricktron force, while losing the Home Crystal knocks a faction out. In the versus version, your friends are opponents trying to outbuild, outmaneuver, and attack your settlement. Catapults, explosive barrels, and the shape of the island give those battles a physical side: a wall can protect a route, a bridge can expose one, and a damaged support can bring part of a castle down.
Invasion and Sandbox are the co-op-oriented options: Invasion puts the shared crew against Corruptron waves, while Sandbox removes those attacks and leaves the island open to construction. Conquest is the competitive mode for opposing factions.
You can play co-op online or over a LAN; there is no same-screen couch option. Cross-platform play covers the Windows, macOS, and Linux versions, but which operating-system combinations work together is unclear, so check your group’s setup before planning a session. The co-op party limit is also unclear: Conquest Versus supports two to four players, but that range does not establish how many can join Invasion or Sandbox.
Hosting and network setup
One player hosts a multiplayer session and can invite friends through the Steam overlay or let them join from the session list. Firewall rules or network routing may interfere with connections, and port forwarding may help in some cases. If a connection fails, troubleshooting can take additional work.
Castle Story is best treated as a settled package rather than an actively expanding game. New updates were no longer in development, although community support was expected to continue. The World Editor and Workshop let players create, share, and try additional maps. Those community-made worlds add places to explore, but they are not new developer-made campaigns.
The building concept remains distinctive, but the execution asks for patience. Some players praise the satisfaction of seeing a defense come together; others find the controls awkward, the pathfinding unpredictable, or performance uneven. A Bricktron may take a longer route around terrain or become blocked by the layout, and commands may not happen immediately. Unit orders and task management are part of the game’s challenge.
Castle Story suits a group interested in designing defenses as well as surviving them. Invasion gives every player the same crew and a Home Crystal to protect, while Sandbox leaves the island open to shared construction. Towers, gates, bridges, and traps become part of a physical defense, though physics and unit pathfinding can make a blueprint harder to realize than it first appears. Its co-op is built around one settlement and shared construction jobs; it has no separate armies or same-screen couch mode, and the Invasion/Sandbox party limit is not established by the 2–4-player Conquest Versus count.