Weird Wednesday: Cheat Shepherd
Weird Wednesday — Cheat Shepherd
The trigger
Two signals line up cleanly today. First, cheating is now big enough to be reported as an $8.5B-a-year industry, which means "cheat literacy" is mainstream: players already understand terms like wallhack, speedhack, lag switch, and aimbot. Second, there’s explicit player demand for low-input auto-battle games, plus a separate complaint that too many combat games drown good fundamentals in excess systems. That points to a tiny prototype where combat is automatic and the only player expression is illegal-looking intervention.
The idea
Make a single-screen autobattler where your fighter attacks on their own and you never press a normal combat button. Your entire moveset is a handful of "cheats" you inject into the match: speedhack to overclock your unit, wallhack to reveal incoming threats through fog or cover, lag switch to briefly freeze enemies, aim assist to bend missed shots into hits, maybe teleport desync to snap your unit out of danger. The twist is that an anti-cheat suspicion meter is always climbing. You are not building a fair build; you are shepherding a dumb auto-fighter through a match by using blatantly unfair tools just enough to win before the system catches you.
The core loop
Start a round. Watch your unit auto-path and auto-attack badly. Read the arena for the next failure point: getting surrounded, missing key shots, walking into traps, wasting time on a tanky target. Spend one cheat charge to correct that failure at the last second. Suspicion rises with every intervention, and repeated use of the same cheat raises it faster. Between rounds, choose one new cheat, one cooldown reduction, or one anti-detection perk. Then go again with slightly harder enemy patterns and slightly less room for sloppy timing.
Why now
This is a good moment for a game that treats cheating as readable game grammar instead of a backend security topic. Players already know the fantasy because of the cheating news cycle, and they’re actively asking for AFK combat that still gives them something to manage. It also answers the "too much of everything" fatigue: one character, one arena, one idea, no inventory treadmill. The weirdness is not in obscure rules; it’s in reframing familiar cheat tools as the only verbs the player has.
Scope
First playable milestone: one arena, one auto-fighter, three cheats, five enemy waves, and a visible suspicion meter. Cheats should be distinct and prototype-friendly: speedhack doubles move/attack rate for 3 seconds, lag switch freezes all enemies for 1 second, aim assist guarantees the next 5 shots hit. Add one between-wave choice after each clear. No meta-progression, no content breadth, no online anything, no real anti-cheat satire layer needed yet. If the 10-minute loop of "watch, intervene, risk detection" works, you have the game.
What kills it
If the cheats feel like ordinary spells with edgy names, the project is dead. The whole point is that each verb must carry the texture of cheating: ugly, tactical, slightly abusable, and best used to correct automation failure rather than to do direct damage. If players describe it as "just an autobattler with cooldown abilities," you missed the only reason to make it.
Ship the ugly prototype first: one bot, three cheats, one suspicion bar. If that tension is funny and legible within two minutes, keep going.