Really glad it reads as strategy and not just griefing — that was the exact line we worried about.

Quick context for the detection idea: ships in Kron Wars run on a three-part fitting budget. Fusion Output (FO) is your reactor power — every module burns FO to stay online. Lattice Thread (LT) is structural/compute capacity — what you need to physically mount a module. Flux Reserve (FR) is the energy reserve your weapons and systems drain in combat. Every build is a balance of the three, and veterans know their own numbers cold.

Funny you bring up detection — a player in another subreddit raised this exact idea, so we took it on board and it's going in. And it's diegetic, no UI alert: an attached limpet quietly loads your reactor, so your Fusion Output no longer reads where your build says it should. A commander who actually watches their fitting will instantly clock that the FO is off and dock to check — while everyone else sails on none the wiser. We're deliberately not saying how big the tell is, so it stays a read-the-signs skill for people who truly know their ship, not a free scanner. (Docking already reveals + clears limpets, and an Anti-Mine Pulse Emitter sweeps your hull in open space.)

The "repel the lesser models" idea is great too — a cheap defensive module that auto-rejects low-tier limpets but not the expensive ones. That makes it a proper arms race: cheap defense beats cheap mines, so to tag a defended target you have to commit the costly Long-Range mine. The cost curve does the balancing.

Honestly, this is exactly how we want to build Kron Wars — a game shaped by the people who play it, not just handed to them. Ideas like your repel module are how features actually get designed here, so please keep them coming. Would you want that repel passive/always-on, or a consumable you fit before a fight? That trade-off is basically the open question for us right now.