Whitepages

What is live now

• Epic Games OAuth flow is wired and ready for approved production keys.
• Island Forge generates UEFN terrain from uploaded audio analysis and writes each run into a named output folder with PNG, JSON, manifest, and Verse package artifacts.
• Channels provides a multi-category embedded guide with suggestions.
• Arena now has a dedicated A-Frame spectator deck at /arena with leaderboard, theater, and ops-rail concepts.
• The member hub already exposes a telemetry deck, stat cards, ticker rails, and ecosystem radar as the base for the future immersive room.
• Community and feed routes support social posts, updates, and member identity.
• Oracle Autonomous Database stores members, posts, islands, and channels.
• OCI Object Storage serves public media and generated assets.

Experience target

The long-term member experience is not a flat profile page. It is a room: one wall for generated island previews, another wall for player cards and earned status, and one main screen for a live telemetry deck with charts, heatmaps, ticker rails, and ecosystem cards.

• Island wall: grid of generated island PNGs, recent runs, and named build folders.
• Player wall: Epic identity, locker skin, room theme, tickets, platform role, and earned badges.
• Main screen: large TV-style telemetry with stat cards, chart stacks, live rail updates, and cross-platform readiness indicators.
• Room styling: premium workshop / hero-lab language rather than a generic account dashboard.

Data surfaces we can actually use

• Epic login identity: account identity and session state from Epic authentication.
• Platform data: islands, uploads, tickets, channels, announcements, room theme, admin state, and other data we store in Oracle.
• Public Fortnite surfaces: public shop, cosmetics, and published-island analytics once a real island code is live.
• Keyed Fortnite stat lookups: player stat snapshots when the external Fortnite stats key is configured.
• Product-side EOS data: stats, achievements, and progression for products we own and wire ourselves, not arbitrary third-party Epic games.

Dashboard build order

1. Stabilize the current member telemetry deck and keep all current cards sourced from real Oracle or Fortnite endpoints.
2. Add an island gallery wall inside the member room using the player's generated previews and saved metadata.
3. Add a player-card rack for badges, earned events, hub role, linked systems, and future TriptokForge-native achievements.
4. Upgrade the center screen into an immersive chart deck: deltas, heatmaps, activity timeline, ranked ladders, and event cards.
5. Add richer 3D or faux-3D panels only after the data rails are real and readable.

Reference note: templates/whitepages/MEMBER_HUB_ROADMAP.md

This lane searches the saved audio library plus the tracked storage roots for longer-form audio and exposes a stream-safe catalog directly inside WhitePages. Tracks shorter than 0:45 are filtered out before they ever reach the deck.

The visual language is tied to the same rotating skin manifest that feeds the shared member audio player across the rest of the site, so the vault and the site chrome stay in sync instead of feeling like separate tools.

Public system map

• Member identity: Epic-auth login, member profile fabric, role surfaces, and progression-aware dashboards.
• Creator tools: Island Forge, asset processing, scene packaging, and other member-facing generation flows.
• Community layer: channels, broadcasts, news, social posts, and community-facing discovery surfaces.
• World outputs: generated terrain packages, media assets, previews, and downloadable run artifacts.

Detailed hosting, repo, deploy, and route ownership notes stay in the staff appendix instead of the public reference layer.

What we are building

The current game direction is a browser MMORPG with a neon hub city, raid zones, loot collection, inventory, skills, shops, bank, extraction flow, and a polished delivery-quest vertical slice called Shinobi Post. The playable runtime lives in triptokforge-platform; WhitePages explains the structure, the approved tooling, and the resource pool behind it.

Game loop

1. Open the launcher and connect the MMO shell.
2. Move through the hub.
3. Interact with shops, the bank, and the raid gate.
4. Collect loot and manage inventory.
5. Use abilities, fight enemies, and extract from raids.
6. Keep the profile and world state synchronized through the server.

Approved resources

• Browser runtime: Phaser, PixiJS, Matter.js, Box2D, and Tiled.
• Safe art pools: Kenney, OpenGameArt, Time Fantasy, Oryx Design Lab, AmbientCG, and Polyhaven.
• Audio: GameSounds and Freesound.
• C++ reference pool: SDL, SFML, Box2D, doctest, Catch2, googletest, microui, GuiLite, lvgl, filesystem, and portable-file-dialogs for future tools or exporters.
• 3D / debug references: Three.js devtools-style scene inspectors for future scene and launcher tooling.

Implementation notes, repo topology, and internal build documentation stay in the staff appendix so the public page stays product-facing instead of backend-facing.

The four launch modes

• Prismatic Haven: companion care, feed / clean / rest / play, and growth.
• Spraypaint District: town building, decoration, and home styling.
• Shinobi Courier JDM: delivery routes, parkour, weather, and rewards.
• Companion Grove: social ecosystem, seasons, bond, and persistence.

Reference shelf

The full shelf lives in templates/whitepages/PRISMATIC_TOWN.md. It tracks the approved and study-only repos and references we used while designing the family.

• The channels page now renders from templates/channels.html instead of building HTML inside Python.
• channels_page.py now only normalizes embeds and groups channel data for the template.
• The page keeps the current holo/JARVIS visual treatment while becoming easier to maintain.
• The player stage now keeps a comfortable default size and supports saved drag-resizing on desktop.
• Scopes now mirror the news curation model with Fortnite, Builders, Arena, Signal, Community, and Chill rails.
• Channel suggestions submit through POST /api/suggest_channel for review.

Catalog refreshes should prefer official replay, playlist, and /videos feed URLs over weak raw handles, with the Oracle seed script acting as the source of truth for the live channel catalog.

• /arena is now the first real arena surface instead of only a note inside /esports.
• The room layout is theater screen front and center, leaderboard wall on the left, and concession counter behind the seating.
• The scene uses procedural stand-ins for speed while the right-rail asset locker points to Fab and Megascans source packs for future swaps.
• The right rail should grow into tournaments, replay lab, broadcast booth, team garage, and prize vault subsections.

Reference note: templates/whitepages/ARENA_ROADMAP.md

Current handoff

• The login flow fails safely when secrets are missing instead of using hardcoded values.
• The current Flask website login uses only the approved client ID, client secret, deployment ID, and exact callback URL.
• The production base URL drives the redirect base for login and logout.
• The callback path must exactly match the value approved by Epic for the production app.
• The login app belongs to the Epic Account Services / Developer Portal lane, not Fortnite Creator Portal publishing.

Reference notes: templates/whitepages/EPIC_APPROVAL_RUNBOOK.md, templates/whitepages/EPIC_LOGIN_READY_CHECKLIST.md, and templates/whitepages/EPIC_CONTACT_MATRIX.md

Implementation rule

• Do not put Epic marks into the main site lockup, favicon, or footer identity stack.
• Keep Epic marks on factual Epic-related UI and compliance surfaces only.
• Use the official disclaimer and policy language required by Epic where that fan-content boundary applies.

What it is

• Display name: ColorsTheForce
• Badge: AI Moderator
• Owner: TriptokForge
• Language: American English
• Core domains: Fortnite, UEFN, games media, code, creator operations, human communication, and moderation

How it should be operated

• Use the dedicated /ops staff console with either an admin account or a linked bot-operator account.
• Do not create a fake public human-style password for it.
• Allow manual post, edit, and draft generation through admin.
• Require human approval for destructive or high-impact actions.

Compliance boundary

• It can be knowledgeable about Epic, Fortnite, Nintendo, and Microsoft ecosystems.
• It must not claim to be an official representative of Epic, Nintendo, or Microsoft.
• It must remain clearly labeled as an in-house AI moderator owned by TriptokForge.

Reference notes: templates/whitepages/COLORSTHEFORCE_PROFILE.md and config/bot_profiles.example.json

Core patterns

• Immutable data: build fresh player records instead of mutating shared state.
• UI state: store HUD references per player for reliable cleanup and redraw.
• Material encoding: compress rarity and element into deterministic inventory slots.
• Persistence: keep long-term player progression compatible with seasonal updates.
• Death penalty: preserve risk and extraction tension as a core loop.
• World layout: keep the 32 farm plots in one coastal social cluster near town, then push biome escalation outward.

Current target layout keeps all 32 farm plots in one shared coastal hub near town, with coherent Fortnite prefab kits assigned biome by biome instead of random prop mixing.

The package is now intended to be theme-aware and concrete: the selected Fortnite chapter changes biome material guidance, gallery recommendations, landmark inspirations, foliage slot bindings, and placement-plan output instead of only changing a label.

The important contract is now explicit: changing world scale changes the downstream UEFN steps. If Forge flags World Partition, the player needs to enable it before import instead of trying to brute-force the landscape into a default island.

Reference note: templates/whitepages/FORGE_AUDIO_WORLD_MODEL.md

Forge Runbook

1. Open /forge, upload an audio track, and let the analysis complete so the terrain weights reflect the real file instead of defaults.
2. Name the world and choose the Fortnite chapter theme you want the asset manifest to target.
3. Set world scale, resolution, water level, wrap, farm direction, and cluster density. Keep the direct square landscape lane at or below 2017 x 2017. If the Forge streaming flag appears, plan to enable World Partition in UEFN before import.
4. Press Generate. Confirm the run saved into outputs/WorldName#N/ and download or open the generated files from the Forge locker.
5. In UEFN, create or open the target island. For worlds above roughly 1km on the widest axis: Edit -> Project Settings -> World -> Enable World Partition, then World Settings -> Enable Streaming.
6. Import heightmap.png through Landscape Mode -> Import from File using the recommended Forge resolution. Use preview.png as a visual reference and layout.json for metadata, town center, and plot positions.
7. Copy the generated Verse files into your project or extract verse_package.zip. Keep the generated files together with asset_manifest.json, landscape_config.json, and placement_plan.json, then build Verse in UEFN.
8. Bind the generated Verse slots to builtin Fortnite gallery and prop assets inside UEFN from the Fortnite content browser. The generated package documents supported builtin content-browser hints; it does not require custom shipped assets.
9. Treat the generated Verse files as data modules and binding scaffolds. The package tells UEFN what to place and what slots to wire; the editor still owns the final builtin asset binding, placed Verse device, and any project-specific runtime spawn logic.
10. Launch a session, validate streaming cells, town placement, plot spacing, and coastline readability, then iterate by regenerating the next numbered run folder instead of overwriting the old one.

Players stage from a safe hub, run extraction zones for materials and kills, and decide whether to bank progress or press deeper for better loot.

Economy loop

• Grow or gather materials, then sell or craft around rarity and element value.
• Kill enemies to earn drops, XP, and quest progression.
• Extract safely to keep the run. Die and the carry risk becomes real.
• Use insurance tokens to protect the most important item in a run.
• Level up into harder zones, more systems, and higher-end cosmetics.

Death penalty

• Lower stacks create full-loss pressure and teach early caution.
• Higher-stack players still take meaningful loss while keeping late-game progression viable.
• Insurance creates decision tension instead of full safety.

Material economy

• Five primary material families keep collection readable.
• Eighteen elements and multiple rarity bands support broad crafting depth.
• A deterministic slot and value model keeps UI and storage simpler.