u/SomeRussianMike

Товарищи, я сделал кликер - симулятор революционера. Нужно взять власть в свои руки и удержать ее в течении 100 дней!

https://crokocat.com/game/taptaprevolution/

I've been building out a small browser games portal, and the last one got out of hand: a Quake 3-style arena shooter with blocky Roblox-looking characters. One HTML file, 2513 lines, ~200 KB. Three.js from a CDN, no build step, no bundler, no npm install. You open the file and it runs.

Some things I learned that I think are worth sharing:

The map is a config object, not a level editor. Everything lives in a MAP const at the top — weapon set, ammo spawn points, health pickups, whether corpses drop crates and how long they last. Ammo points are just [x, y, z, weaponType]arrays. Moving the sniper to a different tower is editing four numbers. This turned out to be the single best decision in the project, because iterating on the arena with an AI is much easier when the whole level is 8 lines of data instead of scattered geometry calls.

I had to give it a grid rule. Early on the arena looked like melted Lego — every generated wall was at a slightly different offset. So I wrote the rule down explicitly: 1 m grid, walls are 4 m cubes, XZ faces snap to whole meters, Y allows half-steps for stairs, masonry offsets are 0 or ±1. Once that constraint was in the prompt, the geometry stopped drifting. Constraints beat corrections.

The bug I'd never have found on my own: adding and removing lights in Three.js recompiles every shader in the scene, so each rocket launch froze the frame for a beat. The fix is a fixed pool of six PointLights that get grabbed and released instead of created. Same for the death effect — the grayscale filter makes the canvas a stacking context, which silently ate the HUD until I set explicit z-indexes.

Multiplayer is 176 lines and no game logic. The server is a dumb WebSocket relay that does rooms and host election, nothing else. Clients trust each other — it's a friends-by-link game, not ranked. Each client owns its own HP, the room host simulates the bots, and the shooter computes hits and tells the victim. State goes out at 20 Hz with snapshot interpolation and an adaptive delay of about 2.2× the packet interval. Pickups still aren't synced. It's fine. It's a prototype.

Six weapons: machinegun, shotgun, rockets, railgun, a knife with infinite swings, and a scoped sniper that one-shots and has deliberately terrible spread if you fire it from the hip. Bots don't get the sniper, because that was miserable.

Still desktop only — pointer lock and WASD, no touch controls yet, so mobile gets an honest "desktop only" screen instead of a broken one.

Link in the comments. Happy to answer anything about the netcode or the single-file setup.