Six different code paths write to brain.stats.hp directly, bypassing CombatFacade.apply_damage(). OvercastResolver burns HP by hand. TileEffectService has its own damage pipeline. AbilityOrchestrator calls identity.update_vitals() without going through combat.
Godless has 432 abilities, 250 status effects, a 600ms real-time tick system, grid-based positioning with elevation, posture breaks, resource pools, combo prerequisites — But they're scattered across 15 files talking past each other.
The strangler fig pattern is how we fix this: build the new system alongside the old one, rewire callers one at a time, delete the old code when nothing references it. The game never breaks. You can ship mid-refactor. This is the way.
I asked @opencode to audit my game's combat system. It came back with 15 architectural issues. My combo system? Dead code. Never called at runtime. My status damage? Double-counting through two parallel math paths. My ability executor? A 162-line god function. Brutal. Necessary.
What they're building in 40 prompts: A visual demo — a pretty 3D scene with terrain, character, animations, maybe local movement. Frontend-only.
No backend,
no database,
no WebSocket protocol,
no login/auth,
no persistence,
no multiplayer sync,
no combat system
There is literally no reason to post on x unless you are verified, post dumb bait content, 30 times a day, beg for followers, or are already rich and famous
ive never coded and dont know how yet im building an mmorpg. i was thinking about hosting it online for others to play. its a browser type modernized MUD with full pvp and tactical warfare between kingdoms. What's your thought on that?
17. The client is a Three.js 3D isometric viewport running on React/Zustand. InstancedMesh rendering for 20,000 tiles. Custom shaders with elevation tint and LOD fog. It's a MUD that looks like a game.
15. Class resources aren't mana bars. Fury decays 2/tick. Chi regenerates 0.5/tick. Essence doesn't regen at all. Overcast burns your HP. Play your class or pay the price.
14. 11 interceptors gate every action. Status, stamina, pacing, darkness, capacity, scaling, potency, environment, resonance, grammar, thresholds — your action either clears the pipeline or it doesn't happen.
13. You don't type commands. You speak abilities. Fuzzy matching means "fireball" finds PYROCLAST. Your deck is your vocabulary. The parser learns your style.
12. 2-second combat rounds. Symmetrical engagement. You hit them, they hit you back. No turn queues. No initiative rolls. Just raw, simultaneous violence with posture as your only shield.
11. Godless runs on a sharded nervous system. Four event bridges pulse 1s, 5s, and 60s ticks. Combat, weather, sovereignty decay, spawns — every system breathes on its own heartbeat.
10. Weather isn't cosmetic. Fog cuts your vision radius. Rain makes you WET. Blizzards EXHAUST you. Markov chains keep the sky shifting. Plan around the storm or die in it.