Before code #
Choose which layer owns the change and write its accepted-state/data boundary. A client can propose an action; the API decides whether the authenticated player can perform it. Preserve account-wide appearance and per-community earned progression.
Keep errors and unsupported states honest. Do not make a planned purchase, upgrade, battle or item appear usable just because a button or image exists.
Safe extension seams #
| Feature | Start here | Proof needed |
|---|---|---|
| Appearance option | Catalog/models, registered renderer adapter and authoring kit | Old/new save round trip, account-wide consistency, all supported visual variants |
| Inventory behavior | ViewerInventory + existing inventory controller/view | Ownership, stale revisions, community isolation and accepted render state |
| Room behavior | Raiderville service/protocol + scene adapter | Access, reconnect, lease/ordering and multi-client state |
| Chat integration | Separate verified transport and encounter adapter | Identity/channel binding, event deduplication, rate limits; actual grants separately approved |
| New gameplay/rewards | Server-owned model and transaction boundary | Idempotence, isolation, tuning and real validation before a live claim |
A useful handoff #
- Exact branch/commit and a scoped diff; preserve main and other work.
- Source assets, provenance, unique IDs, schemas and compatibility limits.
- Tests with meaningful failures as well as success; no private credentials or production data fixtures.
- Actual desktop, phone and318×496 panel captures when relevant, including loading/error/reduced-motion states.
- Documentation updated from the final source, explicitly separating implemented, local-only and planned work.
Current limits worth knowing #
The public docs are not a legal compliance certification or a source-access grant. Privacy/deletion/disconnection work and operational retention decisions remain separate owner responsibilities.
Room polling is not a multiplayer combat engine. Preview motion is not full directional locomotion. Local armor/walking proofs are not a promise of every outfit/body combination. Physical appearance does not import gear or stats from another community.
Report a mismatch instead of silently substituting a fixed green raider, fake online state, a different body, invented items or a successful-looking failed write.