Skip to content
Roundcade RC arcade crestPlay now
The Roundcade build story

Built from the table outward

A ground-up product history: what changed, why we built it, and what is available now or preparing for the next preview—not a stream of internal commit names.

Preview actively evolving
Latest update · Next preview candidate

Explore moved player moments out of the profile menu

Image posts, follows, comments, reactions, profile people lists, and privacy controls now meet in a dedicated Explore destination built for browsing.

Read the newest update
Why we built Roundcade

Game night should survive the distance.

Roundcade began with a simple frustration: browser games were easy to open, but the night around them still felt scattered. One link for a game, another app for the group, and no shared place that remembered the people you enjoyed playing with.

So we built the table first—fair games, fast rooms, and reconnect protection—then grew the community around it without treating identity, safety, or operations as somebody else's problem.
01

Fun before machinery

The first proof was not an account system or a store. It was five complete games that people could actually finish together.

02

One place, not 26 islands

Every game shares rooms, friends, invitations, messages, connection recovery, and the same safety controls.

03

Trust is part of the product

Hidden information stays on the server, reports preserve evidence, and sensitive operator actions are permissioned and audited.

From the ground up

The real build timeline

Oldest first, because the later social and operations work only makes sense on top of the table engine that came before it.

01
Where it started
Phase 0 · Foundation

The first five tables proved the idea

Battleship, Standoff, Liar's Dice, Reversi, and Gomoku established the shared room engine and the standard every later game had to meet.

Why we built it

We needed to prove that a browser table could feel responsive, private, and complete before building a community around it. Each first game tested a different hard problem: hidden fleets, simultaneous choices, secret dice, deterministic boards, and configurable rules.

What changed

  • Server-authoritative turns, timers, outcomes, and per-player hidden views.
  • Private room codes, ready states, rematches, reconnect protection, and mobile play.
  • Bots that use the same legal action path as a human seat.
02
The arcade grows
Phase 0 · Game library

From five tables to twenty-six

Roundcade expanded across reflex, memory, word, strategy, team, arena, and Filipino card games without splitting into separate mini-apps.

Why we built it

A real game night needs range. Some groups want a ten-second reaction duel, others want chess, team clues, or a full Tong-its table. Variety became useful only because every new game inherited the same room and safety foundations.

What changed

  • Six fast games, ten word-and-strategy games, team play, real-time Snake Wars, Pusoy Dos, and Tong-its.
  • A dedicated security suite for every game, including leak checks for hands, codes, patterns, and answers.
  • Authentic disclosed rules for Filipino card games plus full chess, checkers, and Gomoku variants.
03
Keep play moving
Phase 0 · Matchmaking

Quick Match stopped empty queues from becoming dead ends

Players can choose a game, search for a compatible human, and receive a capable bot after a short wait when nobody else is available.

Why we built it

The fastest way to lose a new player is to make them stare at an empty queue. Human pairing remains the first choice, while a real game-playing bot lets the session begin instead of pretending activity exists.

What changed

  • Compatibility matches the selected game and its settings.
  • Every one of the 26 games implements a legal bot action contract.
  • Human players are always preferred before the bot backfill timer runs.
04
A player can return
Phase 1 · Platform

Accounts became a secure foundation, not a pop-up bolted onto a game

Registration, email verification, password recovery, device sessions, and protected sign-in were built around the existing tables.

Why we built it

Friends, safety actions, invitations, and durable messages need a person to have one trustworthy identity across devices. We delayed that machinery until the games were worth returning to, then made it strong enough to support everything after it.

What changed

  • Argon2id password hashing, opaque server-side sessions, CSRF protection, and rate limits.
  • Verification and recovery email flows plus device review and remote session revocation.
  • The public catalog remains browseable; playing requires an account and public social play requires verification.
05
People at the table
Phase 2 · Identity

Profiles and safety controls arrived together

Display names, handles, curated avatars, bios, favorite games, privacy settings, blocking, muting, and reporting became reachable player flows.

Why we built it

Identity without control creates an unsafe social layer. The same profile that helps a good player be remembered must also make it easy to mute noise, block unwanted contact, or report credible harm.

What changed

  • One rich identity presentation shared by the player's own profile and public profiles.
  • Block and mute behavior enforced by the server rather than hidden only in the interface.
  • Reports carry reasons and context into a real moderation queue.
06
The next match
Phase 2 · Social play

A good table no longer disappears when the match ends

Player search, friends, recent players, game invitations, notifications, and direct messages connect one session to the next.

Why we built it

The most valuable result of a multiplayer match is sometimes the person you want to play again. We built a consent-based path from shared match to friend request, invitation, and conversation instead of forcing people to exchange contact details elsewhere.

What changed

  • Recent Players records only people who actually reached a match together.
  • Game invites re-check room validity and privacy when accepted, not only when sent.
  • Confirmed friends can message with durable unread counts and reconnect reconciliation.
07
One shared place
Phase 2 · Community

Public rooms, truthful presence, and a community lobby made Roundcade feel inhabited

Players can browse compatible public tables, understand who is available, and meet in a moderated lobby without confusing room state with global presence.

Why we built it

A social game hub should feel alive without lying about activity. Presence is privacy-projected, room readiness remains room-authoritative, and blocked players are separated before discovery or matchmaking can place them together.

What changed

  • Public, private, unlisted, and locked room states with host controls.
  • Redis-backed presence with privacy projection, heartbeat handling, and explicit unavailable states.
  • Lobby messages, player cards, unread signals, and report-a-specific-message evidence capture.
08
Fast enough to trust
Phase 2 · Quality gate

The platform got lighter, clearer, and harder to break

Adaptive visual tiers, smaller real-time payloads, overload controls, security gates, and full endpoint-to-interface audits turned working features into a coherent preview.

Why we built it

A beautiful multiplayer screen is not finished if it stutters on an ordinary phone, leaks a secret, reconnects forever, or exposes a backend action nobody can reach. Performance and integration were treated as product behavior, not cleanup.

What changed

  • Full, Balanced, and Performance render tiers with reduced-motion support.
  • High-frequency Snake Wars payloads reduced by roughly 60% in the measured preview baseline.
  • Account-aware concurrency, privacy gates, rate limits, health checks, and caller coverage tests.
09
The other side of safety
Roundcade Ops · Foundation

Reports finally had a complete operator workflow behind them

Roundcade Ops connects reports, account support, sanctions, appeals, investigations, system health, staff roles, announcements, and immutable audit trails in a separate protected console.

Why we built it

A report button that nobody can work is decoration. Once Roundcade supported public social play, the internal response path became part of the feature: least-privilege roles, fresh MFA for sensitive actions, evidence-bound investigations, and no arbitrary message browser.

What changed

  • Separate admin session and origin, capability-based roles, fresh MFA, and action reasons.
  • Report-bound lobby removal and case-bound private-message access with per-message auditing.
  • Operational health, jobs, outbox, error timelines, and security-sensitive account actions.
10
Explain the product
Launch readiness · Public surface

Roundcade now has a public handbook, not just an app shell

Crawlable game guides, a Safety Center, FAQ, product history, legal routes, structured metadata, and a sitemap explain what Roundcade is before sign-in.

Why we built it

Players should not need an account—or a search through menus—to understand a game's rules, the platform's safety model, or why the product exists. Clear public content also gives search engines a truthful version of the preview instead of indexing private app screens.

What changed

  • One detailed guide per game, generated from the same GameInfo rules and host settings used by the server.
  • Readable public support and safety paths with no fake live feature claims.
  • Per-route titles, descriptions, structured data, canonical URLs, robots rules, and a generated sitemap.
11
Authority players can recognize
Phase 3A · Trust and identity
Next preview candidate

Official identity became visible—and difficult to imitate

Founder and Staff authority now comes from server-held roles, while custom avatars pass through one guarded media pipeline before they can represent a player.

Why we built it

A badge is useful only when a player can trust who issued it. Uploaded images also cannot be treated as harmless decoration: file validation, re-encoding, metadata removal, scanning, quarantine, review, takedown, and audit all need to agree before an image appears.

What changed

  • Founder, Staff, VIP, and Player treatments are server-derived and visually distinct.
  • Reserved names, authority palettes, impersonation signals, and staff-role changes are enforced beyond the client.
  • Custom avatars reuse one private upload and moderation path with safe fallback and report controls.
12
A place around the table
Phase 3A · Voice Rooms
Next preview candidate

Voice Rooms grew into a real gathering space

Live voice now has speakers, listeners, mic requests, host controls, room privacy, Party Chat, follow-and-recall, and clear recovery states instead of a single fragile call button.

Why we built it

Some nights begin with a game; others begin with people talking until a game starts. Roundcade needed a room that could hold both without giving a host remote control of somebody else's microphone or hiding moderation actions.

What changed

  • LiveKit carries audio while Roundcade remains authoritative for membership, roles, blocks, bans, and token issuance.
  • Room entry and mic access are separate choices: Invite only, Friends, or Public entry; Apply, Open seats, or Host invite mic policy.
  • Hosts can move speakers to listeners, followers can receive a rate-limited recall, and server-authored Party Chat receipts explain room actions.
13
More reasons to return
Phase 3B · Progression and expression
Next preview candidate

Matches now build a history beyond the final score

Game XP, levels, honors, leaderboards, daily rewards, earned Coins, gifts, Shop, My Items, and VIP benefits now share one server-authoritative progression and ledger foundation.

Why we built it

Retention should reward real play and real community—not turn spending into skill. We separated Game XP, social recognition, Coins, and VIP standing so every number says what it actually measures.

What changed

  • Completed-match events feed XP, missions, achievements, rewards, and all 26 per-game boards without trusting a client claim.
  • Coin balances come from an append-only ledger; gifts, purchases, reversals, and rewards use idempotent transactions.
  • Frames, illustrated profile and room themes, chat styles, and entrance effects have real previews, eligibility rules, expiry, and low-motion fallbacks.
14
The community comes forward
Phase 3 · Social preview
Next preview candidate

Explore moved player moments out of the profile menu

Image posts, follows, comments, reactions, profile people lists, and privacy controls now meet in a dedicated Explore destination built for browsing.

Why we built it

People already understand that discovery belongs in primary navigation. Hiding a feed inside Me made the community feel like a profile setting, so Explore now sits beside Play, Messages, Voice, and Me while profiles stay focused on identity and a player's own posts.

What changed

  • For You, Friends, and Following feeds explain why a post appeared and keep reporting one action away.
  • Followers and Following open real people lists with separate server-enforced visibility controls.
  • Explore is present in the mobile dock, desktop rail, authenticated Home navigation, and menu fallback.
Next preview gate · Connected polish

Preparing the next Roundcade preview

The current candidate connects trusted identity, Voice Rooms, progression, collectibles, VIP surfaces, Social Profiles, and Explore across the player app, server, and Roundcade Ops. Each stays a candidate until its responsive browser checks and deployment gate pass together.

A truthful preview“Next preview candidate” means the connected code exists locally and has focused proof; it does not claim public deployment. Real recharge, Gem competition, wagering, bonus conversion, and withdrawals remain disabled until their financial, safety, Ops, and release gates pass.
Play the current build