4.5 KiB
4.5 KiB
SOR — Left To Do
Generated from report.md + current repo docs (OVERALL.md, AI architecture plan, legal/gameplay backlog docs) on 2026-04-28.
1) High-priority platform/devops
- Implement image/release versioning flow (move off
:latest, use SemVer + tagged build/promotion pipeline).
2) Account/Auth/Web
- Fix mailbox integration.
- Link OAuth to existing accounts.
- Complete reset/forgot password flow end-to-end.
- Add OAuth buttons to login/register UX.
- Add TOS/Privacy acceptance in register flow.
- Complete full account metrics feeding leaderboard.
- Website/tutorial content completion (game website + in-game tutorial + how-to page alignment).
3) Economy/Bazaar/Spending (major unfinished area)
- Player marketplace core (search/list/create/buy/cancel listings).
- Marketplace filters/sorting + listing metadata/details.
- USD purchase flow for Origin Points.
- Payment method display + purchase confirmation UX.
- SKU pricing/details in USD and Origin Points.
- Sacrifice/disenchant flow (selection, preview, irreversible warning, confirm + inventory/credit updates).
- Player ledger/history timeline + receipt details.
Economy integrity + security
- Immutable ledger entries for all economy events with full before/after balances and correlation IDs.
- Full card custody trail lifecycle (acquire/list/sell/sacrifice).
- Store payment provider references and receipt linkage.
- Admin investigation queries for suspicious behavior.
- Fraud signal detection (loop trading, outlier pricing, suspicious sacrifice bursts, chargeback correlation, account-linkage risk).
4) Custom Games (partially built, still large backlog)
- Admin custom-lobby oversight (list active/recent, cancel/kick tools).
- 3+ player support (current engine still 2-player constrained).
- In-lobby chat.
- Friend/direct invite flow.
- Public preset sharing.
- Replay system.
- Preset vote “concede” option.
- Host rule update flow while guest is waiting (with guest acknowledgement/push semantics).
- Lobby browser filters (open slots, tags, region, friends-only).
- Rules detail tooltip/panel with full ruleset display.
5) Engine/Gameplay systems
- Full timing/reaction windows.
- Mulligan rules.
- Complete deferred ability effect handlers (from gameplay effects gap docs).
- Continue gameplay TODO items (aura transition/movement validation path).
6) Ranked/Leaderboard
- Ranked spectate support.
- Anti-rematch controls with soft-bypass at high queue times.
- Richer leaderboard properties and metrics.
7) Collection/Cosmetics
- Add cosmetics inventory domain support.
- Toggle/apply cosmetics to cards/decks.
- Cosmetics panel UX (categories, preview, owned/locked state, equip/apply).
8) Settings/Support
- Add support/bug-report messaging entry in Settings.
9) Board templates + alternate board shapes
- Implement
BoardTemplatedomain (entity/model/storage format). - Build admin CRUD/editor for board templates.
- Wire template application into game engine.
- Hex tile support (engine/client/pathfinding still square-only).
10) Networking/privacy hardening
- Replace client-visible
accountIdin wire payloads with session-scopedplayerRef. - Maintain authoritative server
sessionId + playerRef -> accountIdmap (join/reconnect/resume invariants). - Split telemetry exposure (internal account IDs only server-side; client/debug surfaces show
playerRef+ display name).
11) AI subsystem (from Server/docs/SOR.Ai-Architecture-Plan.md remaining phases)
- Active ability support in AI actioning.
- Triggered-target selection improvements.
- Adaptive difficulty API/logic.
- AI personality + lobby display polish.
- Counter-deck selection behavior.
- Initial trained model integration baseline.
12) Legal/compliance
- Ship legal docs: TOS, EULA, Privacy Policy, Cookie Policy (+ any required jurisdictional docs from legal checklist).
Deferred / later-design items (not immediate implementation)
- Fog of War system.
- Asymmetric team sizes (e.g., 3v1).
- Ranked multiplayer ELO/MMR design.
Notes
- This list intentionally excludes items that appear already landed in recent commits unless the backlog/docs still mark them incomplete.
- If you want, next step can be a priority-sorted execution plan (
Now / Next / Later) with owners and rough effort sizing.