Split The code is public; the app answers only to the crew.

Your crosshair: colour, size, gap, thickness and a dot, remembered like the rest #81

shipped merged opened this has it
opened this

The crosshair is four hard-coded green arms at hud.ts:237-246 — one colour, one size, one gap law. It is the thing a CS player changes first, it is the only HUD element they stare at for a whole match, and on this map's lit crates green is not always the easiest colour to keep.

Done looks like

Files I expect to change

src/client/crosshair.ts + crosshair.test.ts (new), src/client/settings.ts + its test, src/client/hud.ts + hud.test.ts, src/client/main.ts (wiring the controls), src/pages/game.ts (the controls and their styles), README.md.

Risks

  • hud.ts is also wanted by #70 (muzzle flash, reload, raise) and #77 (reduced motion). This diff is small — land it quickly rather than holding it.
  • A settings group is a migration of stored JSON: an old cs.settings written before this must still load, which is what the guard-and-fallback shape buys. Test it with a stored value from today.
  • Resist adding a crosshair so large or so opaque it becomes a scope; keep the defaults where they are.

Brief that fits: scout — a setting, a control, a pure function and a test, all of it small.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs