PURPOSE
Holds a small set of static, build-time constants used as engine-wide debug toggles and visual-classification lookup tables. Acts as a tiny shared bag of “things that don’t fit elsewhere yet” — a debug-collision flag, a per-hull light-shape registry stub, and the canonical rarity color palette.
OWNS
DEBUG_COLLISION_BOXES: boolean flag, hard-codedfalse. Intended as a compile-time switch for rendering collision-box overlays.HULL_LIGHT_SHAPE: aRecord<string, { shape: string; fwd: number; perp: number }>keyed by hull identifier. Currently exported empty; reserved for per-hull cone-light parameters (shape, forward offsetfwd, perpendicular offsetperp).RARITY_COLORS: canonical rarity color table. Four entries —green(Common),blue(Rare),epic(Epic),legend(Legendary). Each entry carriesr,g,bchannel values, ahexstring, and a displayname.
READS FROM
Nothing. No imports. Pure constant data.
PUSHES TO
Nothing. Module has no side effects — it only exports values for other modules to import.
DOES NOT
- Does not declare types or interfaces beyond inline shapes on the constants themselves.
- Does not provide helpers (no color-lookup function, no hex parser, no shape resolver).
- Does not read environment variables, URL params, or runtime config; flags are baked into the bundle.
- Does not mutate any state at module load.
- Does not register anything with the engine loop, renderer, or store.
Signals
None. Module exports plain data — no events, no observers, no signal emission.
Entry points
Three named exports, all consumed by import:
DEBUG_COLLISION_BOXES— read by any system that wants to gate collision-visualization rendering.HULL_LIGHT_SHAPE— looked up by hull key when a renderer needs per-ship light-cone geometry.RARITY_COLORS— read by UI/tooltip/affix/loot code that needs to color items by tier.
Pattern notes
- File name is underscore-prefixed (
_debug.ts) to mark it as an internal/scratch surface within the config tree — distinct from the mainconfig.tsand from sibling structured-data configs. - Mixed-concern module: a debug flag, a future-use registry, and a production color palette live together. Each is a candidate for promotion into its own file once it grows (e.g., a real per-hull lights data file; a
rarity.tswith helpers and types). RARITY_COLORSkeys are tier names (green,blue,epic,legend) rather than rarity slugs — callers must use the color key, not a separate rarity identifier.DEBUG_COLLISION_BOXESis a literalfalseconstant rather than an environment-driven toggle; flipping it requires a code change and rebuild.HULL_LIGHT_SHAPEis shipped empty, so any lookup currently returnsundefined; consumers must handle the missing-entry case.