Files
sor/OVERALL.md
T

6.3 KiB

TODO

  • SOR: Design and implement version tagging/release flow (move away from :latest; use SemVer + Gitea Action for tagged image builds/promotions).

  • Custom Games backlog:

    • Admin: Custom lobby oversight — admin page listing active/recent custom lobbies, with ability to cancel a lobby or kick a player.
    • 3+ player support — MinPlayers/MaxPlayers are currently UI-only stubs; engine is strictly 2-player. Multi-player requires engine rewrite.
    • Lobby chat — in-lobby text chat between host and guest before game start.
    • Friend/direct invite — invite specific player by name/ID to a lobby, bypassing browser.
    • Public preset sharing — presets are currently owner-scoped; public browsable presets deferred.
    • Replay system — recording and replay of completed games (related to spectating infrastructure).
    • Vote "concede" option — add third option to preset-load vote to concede/exit lobby if vote stalls.
    • Lobby update while waiting — host rule changes after guest joins (without preset vote); requires push + guest acknowledgement flow in Full state.
  • Platform/engine backlog (not only Custom Games):

    • Board templates — BoardTemplateIdOverride exists in schema as nullable Guid, but no BoardTemplate entity, no admin template management UI, and no engine logic to apply templates. Wire-up deferred until template format is designed.
    • Admin: BoardTemplate editor — full CRUD page for named board templates (tile layout, size, special tiles); blocked on defining template storage format.
    • Hex tile shape — TileShape enum stub (Square/Hex) can be stored, but engine, client renderer, and pathfinding are square-only. Hex remains UI-disabled.
  • Product/UI/Platform backlog:

    • UI/UX OAuth config update (Google first).
    • Boot logo change.
    • App icon change.
    • Refactor each scene: split UI building out of .gd into node-based scene structure for easier UI changes.
    • Game website.
    • Tutorial in game + how-to guide on website.
    • Legal docs: TOS, Privacy Policy, EULA, Cookie Policy, plus any additional required docs (track in Shared/legal.md).
  • Account management:

    • Fix mailbox.
    • Link OAuth to existing account.
    • Reset password flow.
    • Full account metrics for leaderboard (including ranking).
  • Spending panel:

    • Uncensor toggle (censored by default).
    • Full tracker on USD / Origin Points spent and what it was spent on.
    • Download spending report.
  • Spending controls panel:

    • Set monthly spending cap (money and/or Origin Points).
    • Cap is lock-enforced once set.
    • Cap can only be changed once per month.
    • Warning prompts required before setting/changing cap.
    • Show next eligible cap-change date/time.
  • Legal links panel:

    • TOS, EULA, and other required legal docs links.
  • Bazaar / economy:

    • Player marketplace:
      • Search/browse listed cards.
      • Listing details: card identity (definition + variant), seller, price (Origin Points), listed-at timestamp, listing status.
      • Actions: buy listing, cancel own listing, create listing from owned inventory.
      • Filters/sort: card name/type/rarity/affinity, min/max price, newest, price asc, price desc.
    • Buy Origin Points (USD purchase flow).
    • Payment method display + confirmation modal.
    • Show SKU pricing/details in USD and Origin Points (where applicable).
    • Sacrifice / disenchant:
      • Select cards from owned inventory.
      • Preview Origin Points return before confirm.
      • Explicit irreversible warning.
      • Confirm flow: remove/flag cards from inventory and credit Origin Points.
    • Ledger/history (player view):
      • Transaction timeline for marketplace buys/sells, store purchases, sacrifices, refunds/reversals.
      • Receipt details with transaction id.
  • Audit / chain-of-custody requirements (critical):

    • Immutable ledger entry for every economy event including: transactionId, eventType, accountId(s), asset refs (cardInstanceId, skuId, etc.), balance before/after, timestamp, and request correlation (requestId).
    • Full custody trail per card instance: minted/acquired → listed → sold/transferred → sacrificed/destroyed.
    • USD purchases store payment provider reference id(s) and receipt linkage.
    • Admin/internal investigation queries for suspicious activity patterns.
  • Fraud / abuse signals (planned):

    • Repeated rapid buy/sell loops between same accounts.
    • Outlier pricing patterns.
    • High-frequency sacrifices after suspicious acquisitions.
    • Chargeback/refund correlation with asset transfers.
    • Multi-account linkage risk indicators.
  • Collection:

    • Add cosmetics.
    • Enable toggle to apply cosmetics to cards/decks.
    • Cosmetics panel UI:
      • Category selector (back/trim/art/model).
      • Preview pane.
      • Owned/locked state indicators.
      • Equip/apply controls.
  • Custom Games additions:

    • Filter controls (open slots, format/rules tags, region, friends-only).
    • Rules detail tooltip/panel on hover/focus with full ruleset display.
  • Leaderboard:

    • Track additional properties for a richer leaderboard.
  • Login / register:

    • OAuth buttons for login/register.
    • Forgot password flow.
    • Register: add TOS/Privacy acceptance.
  • Ranked:

    • Ranked game viewer: enable spectate for ranked games.
    • Anti-rematch / pairing controls:
      • Avoid same-opponent rematch within last 2 completed ranked games when alternatives exist.
      • Soft rule only; allow bypass at high queue times.
  • Settings:

    • Add message support / bug report entry.
  • Gameplay:

    • Full timing windows and reaction timing.
    • Mulligan rules.
  • Networking/privacy hardening:

    • Delta identity decoupling: replace client-visible accountId usage in game wire payloads with session-scoped playerRef identifiers.
    • Server identity map: maintain authoritative sessionId + playerRef -> accountId mapping with strict invariants on join/reconnect/resume.
    • Logging/telemetry split: keep internal accountId linkage in server logs only; expose playerRef (and display name) in client-visible/debug payloads.