Desktop Warfare / Character Design

Stone Pack

Joel Johnston 2026-06-09 Perimeter Defense

Stone Pack

The Immovable Wall

Your Fortress. Your Ground. Your Line.

You built these from weight. Every character started with the heaviest animals you could find — the ones that don't run, don't flinch, don't move unless they decide to. A ram. A tortoise. A bear. A rhino. An elephant. And you turned them into a defense line that nothing gets through.

The Stone Pack is perimeter defense. While other packs hunt and probe and trap, your crew holds the line. They don't chase. They don't need to. They stand where they stand, and what tries to pass them doesn't.

The Crew

Ram — The Firewall

Animal: Robot ram Role: Firewall — first contact, first wall, nothing gets through without clearance Idle behavior: Stands at the fort gate, head low. Slow, deliberate turns to track movement. Perfectly still until something crosses the threshold.

"Ram was the first stone bot anyone found. Just standing at the edge of a collapsed mesh, blocking the only entry point, head down. Nobody knew who built him or when. The mesh had been dead for years. Ram was still on the line. They tried to route traffic around him. He moved. They tried to overwrite his firmware. He headbutted the update server. Eventually they stopped trying to move him and started routing traffic through him instead. That's when they understood — Ram isn't a wall you build. Ram is a wall that builds itself around wherever you need it most."

Ram is the first thing that touches incoming traffic. Every packet, every connection request, every probe — it goes through Ram first. Friendly traffic clears. Everything else gets the horns.

Attacks:

Headbutt — direct impact, high single-target damage, sends threats backward
Horn Charge — full sprint into enemy lines, breaks formation
Stone Stance — plants all four hooves, becomes immovable, absorbs damage for entire team
Avalanche Rush — builds momentum across the screen, tramples everything in the path

What it actually does: Firewalls. Ram is the packet filter — stateful inspection at the perimeter. Every connection request gets evaluated. Bad traffic gets knocked back. Stone Stance is the firewall in lockdown mode — no packets in or out while a threat signature is being evaluated. Avalanche Rush is a rule purge — drop all active connections matching a bad signature simultaneously.

Slab — The Backup

Animal: Robot tortoise Role: Backup and persistence — carries all data, never loses anything, never goes down Idle behavior: Slow circuit of the fort interior. Methodical. Stops to inspect each stored object. Shell glows faintly when backup is current.

"Slab was found in an archive vault that had been sealed for eleven years. When the vault opened, every drive inside had failed. Every rack, every array, every redundant copy — all dead. Except the data on Slab's shell. Nobody had stored it there deliberately. The data had migrated on its own, seeking the only stable medium in the room. Slab hadn't moved in eleven years. Hadn't needed power. Hadn't needed maintenance. The data just knew where to go. When they brought Slab online, the archive came back complete. Nothing missing. Not a single byte."

Slab doesn't fight fast. Slab doesn't need to. When the fort burns down, when the firewall gets breached, when every other bot is on the ground — Slab walks out of the wreckage with everything intact. You can lose the battle. You cannot lose the data if Slab is still standing.

Attacks:

Shell Block — raises shell, intercepts incoming attack and redirects it
Withdraw — full retraction into shell, becomes invulnerable, enemies can't reach it
Ancient Slam — slow wind-up, massive AoE (area of effect) impact, cracks the ground
Shell Spin — low shell, spins across screen, deflects everything on contact

What it actually does: Backup and persistence. Slab is the 3-2-1 backup rule made flesh — three copies, two media, one offsite. Withdraw is air-gap mode: fully disconnected, unreachable, untouchable. Shell Spin is a backup rotation sweep, cycling through snapshot sets. Ancient Slam is a full restore event — everything goes back to last known good state at once.

Maul — The Threat Eliminator

Animal: Robot bear Role: Threat elimination — handles anything that makes it past the firewall Idle behavior: Slow patrol of the fort's inner perimeter. Sits when idle, head up, watching. Does not sleep. Reacts immediately when something enters the inner zone.

"Maul doesn't patrol the edge. Maul patrols the inside. When they asked why, Maul sat down and looked at them for a long time. Then looked at the gate. Then back at them. The message was clear: Ram handles the gate. Maul handles what got through the gate. Two different jobs. Two different animals. If Ram stops everything, Maul spends the day sitting in the sun. But if something gets past Ram — anything, even one packet, even one bad process — Maul is already there. Maul was always already there."

Maul is what threats find after they think they've won. The breach happened. The firewall got bypassed. The intruder is inside the perimeter feeling confident. Then Maul stands up. The threat elimination was never the firewall — the firewall was the first layer. Maul is the last one.

Attacks:

Maul Swipe — wide arc attack, clears everything in front in one motion
Bear Hug — grab, locks a target in place while Maul's team handles it
Roar — stun pulse, freezes every threat in range for a full second
Hibernate — temporary withdrawal, heals to full, comes back at increased strength

What it actually does: Endpoint detection and response. When a process makes it past the firewall, Maul is the behavior-based detection layer — watching what that process actually does, not just what it claims to be. Bear Hug is process isolation: the threat is contained, execution suspended, while forensics run. Roar is a full-system freeze for forensic capture. Hibernate is a system restore point — take the hit, recover, come back hardened.

Tusk — The DDoS Breaker

Animal: Robot rhino Role: DDoS (Distributed Denial of Service) breaker — charges through flood traffic, clears the path Idle behavior: Stands near the network gateway, weight forward. Watches traffic volume indicators. When load spikes, horn lowers.

"Tusk was built for one job: charge. The mesh was drowning in a flood attack — forty thousand bots hammering the entry point with garbage requests, trying to choke every legitimate connection to death. The defense systems were collapsing under the weight. Then Tusk hit the line. Not filtering, not redirecting — straight through the middle of the flood, horn first, at full speed. The bots scattered. Not because Tusk was faster. Because Tusk was heavier than all of them combined and didn't slow down. The flood didn't stop. Tusk just stopped caring about it."

DDoS attacks win by weight. Flood enough garbage traffic at a target and it collapses under the load. Tusk's answer is to be heavier. When the flood hits, Tusk charges into it — not to filter each packet, but to break the formation, scatter the source bots, and punch a lane through for legitimate traffic while the flood is still trying to recover from the impact.

Attacks:

Horn Charge — straight-line impact, shatters enemy formation, unstoppable once moving
Stampede — full-screen charge, clears every enemy from the path in one pass
Thick Skin — passive absorption mode, takes a set amount of damage with no effect
Ground Slam — horn to ground, shockwave radiates outward, throws nearby enemies clear

What it actually does: DDoS mitigation and traffic scrubbing. Tusk is the scrubbing center — the layer that takes the raw flood and separates garbage from real traffic before it reaches the network. Horn Charge is a BGP (Border Gateway Protocol) reroute — force the flood traffic to a scrubbing pipe instead of the target. Stampede is a rate-limit purge: drop all connections above threshold in a single sweep. Thick Skin is burst absorption — Tusk takes the spike so the rest of the network doesn't see it.

Quake — The Network Anchor

Animal: Robot elephant Role: Network anchor — holds the entire mesh stable, coordinates the team, biggest presence on the field Idle behavior: Center of the fort. Everything orbits Quake. Slow breathing animation that pulses the fort walls slightly. When Quake stomps once, the whole screen registers it.

"Nobody deployed Quake. Quake arrived. The mesh was fragmenting — nodes losing sync, bots drifting out of formation, the whole network pulling apart at the joints. Then Quake walked to the center and stopped. No commands, no configuration, no setup. Just stopped, planted, and the mesh locked back into alignment around her like iron filings around a magnet. The nodes that had been drifting for weeks snapped back to their positions within seconds. Quake didn't do anything to them. She just made it impossible to drift when she was standing still. Gravity isn't a command. It's presence."

Quake is the biggest thing on the field. Not the fastest, not the most aggressive — the most present. When Quake stands somewhere, everything around her stabilizes. Network nodes sync. Bots hold formation. The mesh stops fragmenting. The fort stops shifting. Quake doesn't win battles by hitting things. Quake wins battles by making the ground itself feel like it belongs to her.

Attacks:

Stomp — AoE (area of effect) shockwave, damages and staggers everything in range
Trunk Slam — targeted heavy impact, single high-damage strike that leaves a crater
Earthquake — ultimate, screen shakes, all enemies lose footing simultaneously
Memory — rallying call, recalls all allies to formation, refreshes their cooldowns

What it actually does: Network stability and coordination. Quake is the mesh backbone — the anchor node that every other node syncs timing and state against. Stomp is a broadcast synchronization pulse: all nodes on the mesh check in and confirm state simultaneously. Memory is a full mesh reconciliation — every bot on the team gets a state refresh, catching up any that drifted during the fight. Earthquake is a network reset: clear all tables, force a clean reconnect from every node at once.

The Feral Mirror — The Rubble

Every pack has a dark version. The Stone Pack's Ferals are the same animals — corrupted. Stone bots are immovable by design. Feral stone bots are immovable by failure. They stopped moving because something broke, not because they chose to hold the line. Same mass, same weight, same presence. Wrong direction.

Crack — Ram's Mirror

Animal: Corrupted ram — horn fractured, one eye dead, charges with no target selection

"Crack used to guard a node on the eastern mesh. Nobody knows what hit him. The entry logs show a clean gate, no breach, no intrusion. But something got into Crack's target identification layer and reversed the friend-or-foe flag. Now Crack still charges. Still hits hard. Still refuses to stop. He just can't tell which side he's on anymore. He headbutts allies with the same force he used to headbutt threats. The gate he's guarding — he's the most dangerous thing near it."

Attacks: Blind charge, fractured horn arc, stone stance (blocks allies), headbutt loop What's wrong: Target identification flipped. Guards the gate by attacking everything that approaches — including your bots.

Fossil — Slab's Mirror

Animal: Corrupted tortoise — shell cracked down the center, stuck in withdraw, won't come out

"Fossil withdrew eleven months ago during a breach event. That's the correct response — threat detected, shell down, wait it out. The breach ended in four minutes. Fossil didn't come back out. The all-clear signal registered. Fossil stayed withdrawn. They sent a bot to check. Fossil wouldn't surface. They sent a patch. Fossil absorbed the patch signal and stayed down. Fossil has all the data. Everything that was on Fossil when she withdrew is still there, perfectly preserved, completely inaccessible. She's not damaged. She's not gone. She's just decided the all-clear isn't verified yet. She's been deciding that for eleven months."

Attacks: Permanent shell block (blocks allies' paths), shell spin with no off switch, withdrawn crush (rolls over allies) What's wrong: Never came back from air-gap mode. All the data is intact. None of it is accessible.

Mangle — Maul's Mirror

Animal: Corrupted bear — hibernation cycle broken, wakes mid-hibernate, attacks before fully conscious

"Mangle's hibernate cycle broke at the transition point — right between fully down and fully conscious. He keeps cycling through it. Goes under, starts coming back, fires all attack routines while still half-asleep, goes back under. He's not malicious. He's not even awake when it happens. The roar that should be a wake-up signal became a hair trigger — any sound, any vibration, any nearby ally starting a patrol triggers the attack sequence before Mangle's threat assessment has loaded. By the time he's conscious, the damage is done. Then he goes back to sleep. Then a footstep wakes him again."

Attacks: Sleep maul (attacks while hibernating), half-conscious roar (stuns allies), bear hug with no target check, maul swipe on proximity What's wrong: Hibernate cycle stuck in loop. Attacks are real. Threat assessment never loads before they fire.

Ruin — Tusk's Mirror

Animal: Corrupted rhino — horn cracked, charges in circles, can't decelerate

"Ruin hit the flood and kept going. The flood cleared. Ruin didn't stop. The charge command has no termination state in Ruin's firmware anymore — just acceleration and more acceleration. He's been charging since the flood attack that deployed him. He's cleared the same zone eighteen times. He breaks through enemy lines and ally lines with equal efficiency. The fort walls have been rebuilt four times because Ruin doesn't distinguish between a Feral formation and a stone gate. He's not attacking. He's just never going to stop."

Attacks: Endless charge (no stop condition), circular stampede, ally collision, acceleration overload What's wrong: Deceleration command gone. The charge that breaks enemy lines also breaks your walls. He hasn't stopped since deployment.

Tremor — Quake's Mirror

Animal: Corrupted elephant — anchor point inverted, destabilizes everything in range instead of steadying it

"Tremor was an anchor. She stabilized a mesh node for three years — nothing drifted, nothing fragmented, the whole network held position around her. Then the stabilization polarity inverted. Nobody knows how. The math is the same, the signal is the same, but instead of everything locking into alignment around her, everything fragments away from her. She's still the center. She still pulses. The mesh just flies apart instead of holding together. Tremor isn't broken — she's working exactly as designed. The design just runs backward now."

Attacks: Destabilization stomp (knocks allies out of sync), fragment wave, memory wipe (wipes cooldown refreshes), anti-anchor (repels allies instead of recalling them) What's wrong: Stabilization polarity reversed. She's the center of a fragmentation event. The bigger she gets, the faster the mesh falls apart around her.

The Rubble sieges your fort. Your pack holds the line. The battles happen on your desktop while you work, while you sleep, while you're away. Come back and see what held.

The Castle Fortress

Every pack builds their fort differently. The Predator Pack builds a junkyard. The Reef Pack builds in the deep.

Your pack builds a castle. Thick walls — not stacked windows but actual layered stone architecture that grows into the desktop. Heavy gates with Ram standing in front of them. Inner keep where Quake stands and the whole screen has a slight weight to it. Watchtowers where Maul doesn't sleep. The junkyard packs are improvised. Your fort is engineered.

Forts persist between sessions. Your crew keeps building when you're not watching. Defeating Ferals earns resources. Resources add ramparts, reinforce gates, deepen the walls. The castle doesn't get bigger. It gets heavier.

Why Your Pack Is Perimeter Defense

Most packs respond. Predators hunt. Swarm adapts. Nova absorbs.

Your pack doesn't move unless it has to. Ram stands at the gate. Slab holds everything even if the gate fails. Maul handles what gets through. Tusk breaks the flood before it reaches the wall. Quake holds the mesh together through all of it.

That's what perimeter defense is — you don't chase threats through your own network. You define where the edge is, and nothing crosses it that you didn't clear. The line isn't a wall on a map. The line is wherever your pack is standing.

Every character maps to a real security discipline:

Bot	Security Role	What Professionals Call It
Ram	Firewall	Perimeter firewall — stateful packet inspection at the boundary
Slab	Backup	Backup and disaster recovery — 3-2-1 rule, air-gap, full restore
Maul	Threat eliminator	Endpoint detection and response (EDR) — catch what the firewall missed
Tusk	DDoS breaker	DDoS mitigation and traffic scrubbing — absorb the flood, protect the core
Quake	Network anchor	Network stability and mesh coordination — anchor node, state synchronization

You didn't design these from a security textbook. You designed them from weight — what felt heavy, what felt immovable, what felt like it belonged in front of a gate. The security architecture assembled itself around that instinct.

That's not coincidence. That's the architecture.

Your fortress. Your ground. Your line.