RE: https://infosec.exchange/@k3ym0/116297258355796740

So now clearly the next step is to start moving the game logic into DNS.

one record for each bit of state, so like for counting ammo you have 10.ammo.pistol.guns.example.com and actions are further subdomains where you have a CNAME record to redirect to the next state.

so
shoot.10.ammo.pistol.guns.example.com
CNAMEs to
9.ammo.pistol.guns.example.com

And similarly reload.10.ammo.{...} redirects to 12.ammo.{...}

The environment and enemies should be similarly in DNS, and updating a game tick resolves to the next URL, so you would need to jointly encode player and enemy state for something like

13.x.17.y.monster.35.x.37.y.player.combat.example.com

So that e.g. the enemy could trigger a "move" or "shoot" in the next tick, depending on player and monster state.

So then the entire client side game is just a set of state URLs that you prepend the current input to and resolve over and over.