browser -- play in a browser tab The same game as telnet, with gauges and the full-country atlas beside the log. Open https://play.riftforge.me/client/ (or http://localhost:4080 on local Docker). Telnet on port 4000 still works. The public door on the same host (https://play.riftforge.me/) has Origins, Help, and starter commands -- that is the HTTPS site. How you play 1. Open the play page in any modern browser -- no Mudlet install 2. Log in with the same name and password you use on telnet 3. Type commands in the bar at the bottom (up/down recalls history) 4. Watch lifeforce, stamina, focus, and fuel in Status (right column on a wide screen; the Status tab on a phone) 5. Use the compass buttons to walk exits, or type n / look as usual 6. Type atlas for a screen-sized camera in the main log. The HUD map stays the full country and only swaps when you change planes. 7. Right-click a landmark on the HUD atlas (tap or long-press on a phone) and pick walk, drive, atlas, or enter -- never a silent warp. Left-click on a computer does not move you. How you play (continued) 8. Public chat and tells also land in the communication log above the main window (Public and Tells tabs). Check Hide these in the main window to keep those lines out of the story log -- they still appear in the pane. Uncheck it (or hide the pane) to print them in both places. Room speech stays in the main log. 9. Inside a town or building, an interior map sits under the atlas: streets you can see plus rooms you have already walked. Click a square to name it; that does not move you. E marks a way out. Open country hides that pane. 10. Click help browser in the header (it types the command -- it does not leave the tab) 11. The chevron on Comm / Atlas / Interior / Status collapses that pane without losing its controls; the +/- buttons beside a map zoom it in or out (the pane scrolls, the rest of the HUD stays put) 12. display in the header opens font size and a high-contrast theme; both remember your choice 13. Paste more than a couple of lines into the command bar and it offers to send them as separate commands instead of mangling them into one 14. Click the story, Tab, or start typing to jump to the command bar (Escape does the same when no dialog is open). shortcuts in the header lists the rest; End jumps the story log to the newest line (skipped while you are typing). Screen reader keeps Tab for moving between controls 15. save log in the header downloads the story as a text file. This browser also keeps a local copy so a refresh can restore the log -- nothing is sent to the server 16. On a phone, use the Log / Maps / Status / More bar at the bottom. Maps is the atlas and interior; Status is compass and gauges; More opens help, shortcuts, and display. A computer window that is just a bit narrow still shows the atlas and gauges -- the bottom bar is for touch phones. The room name sits above the story log. The command bar stays at the bottom when the keyboard opens. The story stays in the main log, one whole row per telnet line -- the same stacking as the Public comm strip, so rooms and speech should not smear over each other. The log scrolls inside the play window so it cannot grow the page under the command bar. If you tab away and come back, the play page redraws so the log and maps do not smear. If the story still smears or you can scroll under the command bar, hard-refresh the play page (Ctrl+F5) and check the build stamp in the header. What you typed prints back in a dim, italic line above the reply so slow connections don't feel silent -- never during a password prompt. Color is decoration; combat tags like [HIT] stay visible. If you use a screen reader, type config screenreader on -- the atlas and interior map hide, exits stay as text, and Hide these in the main window starts on so public chat and tells are not spoken twice. When lifeforce drops hard, the page may vibrate once and speak Lifeforce critical.