KEEP YOUR PEOPLE AT THE TABLE
Back to the game.
Phones, laptops and Chromebooks can create and join rooms. The webserver keeps the table running; your phone does not need to accept incoming connections.
Joining with a code
My code is rejected
Enter all eight letters and numbers, then press Enter. Spaces and the middle dash are optional. A full game has four reserved seats. An expired or missing game needs a new invite from its creator. Codes last up to 24 hours and close after 30 minutes without a connected player polling the table.
I lost my connection or my phone went to sleep
Return to the same tab and browser. Your private seat is saved for reload in that tab. After 20 seconds away a bot takes over; your reconnect reservation lasts five minutes. Wake the tab and wait for the next update. After five minutes, rejoin with the game code if a seat is free. Leaving the table releases the reservation immediately.
Keep one active tab for your seat. Private browsing or blocked session storage may prevent recovery after reload. Clearing site data removes your saved seat.
The table is not updating
Check your internet connection and open this site's HTTPS address. Finish any Wi-Fi sign-in page. If a work or school network blocks the site, ask its administrator to allow HTTPS to the game's domain, or try another trusted connection. A VPN can change connectivity; follow your network policy. You do not need to disable your firewall or browser protections, open ports on your phone, enable UPnP, or change Safari experimental settings.
Bots wait while a human is choosing trump, bidding or playing. Look for the active player. Any connected player can deal the final two, open the call window, or continue after a result.
The creator left. Can we keep playing?
Yes. Their seat becomes a bot and another connected player can start the table. The creator's browser coordinates bot turns while active. The server selects and validates bot moves privately and takes over coordination if the creator sleeps or disconnects. At least one browser must remain connected for the table to progress.
Hosting your own server
Use a continuously available HTTPS webserver. A browser on a mobile phone cannot reliably act as an incoming public webserver: mobile sleep, network address translation and changing networks interrupt it. This version uses ordinary HTTPS requests and polling, so it does not need WebSocket ports or peer-to-peer router settings.
For a VPS, expose only HTTPS through a reverse proxy and keep the Node port private. Back up the database together with its encryption key. The repository's docs/ONLINE-HOSTING.md includes setup, API behavior, rate limits and recovery instructions. A local loopback preview is visible only on the computer running it; remote players need the deployed public address.