Skip to content

Glitter Boy O.C.C.: power armor and Boom Gun vertical #58

Description

@StreamDemon

Second sequential delivery slice under #12.

Depends on #57. Do not move this issue to next-up until the Coalition Grunt foundation is complete and its reusable multi-O.C.C. boundaries are merged.

Authoritative rendered sources:

  • RUE pp. 67-73 for the Glitter Boy O.C.C., O.C.C. stats, Glitter Boy power armor, Boom Gun, ammunition, and related systems.
  • Referenced skills and general power-armor/combat rules must be rendered and page-stamped during design; do not fill gaps from memory.

Scope to design before implementation:

  • complete page-stamped Glitter Boy O.C.C. content and builder legality;
  • the minimum reusable power-armor/robot-vehicle model required for the printed suit, locations, M.D.C., mobility, sensors, ammunition, and Boom Gun operation;
  • authoritative persistence and combat integration without client-authored armor or weapon state;
  • rules, backend, and SolidJS presentation through a legal level-1 vertical slice;
  • exact printed-value tests, package/root gates, and live browser acceptance.

Explicitly out of scope until designed separately: other power-armor O.C.C.s or a speculative generic vehicle/VTT system.

Missing subsystems: needs:power-armor, needs:loadouts.
Parent umbrella: #12.
Predecessor: #57.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:rulesRules engine (@riftforge/rules)needs:loadoutsRequires structured O.C.C. starting loadouts and authoritative inventory provisioningneeds:power-armorRequires a power armor and robot-vehicle subsystem

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions