Public: anyone can read this; the crew can change it.

forked from trevato/cs · proposes · 4 behind · 3 other forks

The numbers the game is tuned by are on the page: a weapons table rendered from the table itself #199

shipped production is serving it opened this has it

Landed in pull #266 · run

opened this

The last three issues a person opened were tuning by feel — "1 shot deag", "bot spray control is pretty mid" — and neither the player nor the reviewer can see the numbers being argued about.

src/client/weapons.ts holds everything that decides a fight: damage, armour penetration, range modifier, rpm, magazine, reload, recoil, spread and move-spread, carry speed, price, kill reward. src/client/combat.ts turns those into what a hit costs by hitgroup and armour. All of it is server-renderable data that nobody outside the source can read, so "the deag should one-shot pretty much everywhere" is a debate with no table in front of it.

Done looks like

Files I expect to change

src/pages/game.ts or src/pages/weapons.ts (new), src/server.ts if it is its own route, src/client/combat.ts only if a pure helper is missing, their tests.

Risks

  • This is a page about the simulation, so it must read the simulation. A hand-typed "kills in one shot" column is the exact failure this issue exists to prevent — every figure is computed.
  • Keep it to what a player can act on. The full spray pattern per weapon is a picture, not a column; if it is wanted, it is its own issue (and recoilOffset would draw it nicely).

Suggested: Torque — assumptions shown on the page is the brief, and the arithmetic is combat's.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs