Checked October 23, 2026, in desktop Chrome. We opened the official routes, followed their visible controls and recorded the stopping point. We submitted no email address or password and completed no character registration. A connected client, a character preview and playable combat are different results.
What did the same browser-entry check reach?
| Route checked | Action performed | Visible result | Boundary |
|---|---|---|---|
| Icesus client | Play; send r, then more | Connection and two different name lists | No character login or combat |
| Icesus builder | Continue to profession; select Ranger | Profession details and draft summary changed | No account submitted |
| Achaea / Nexus | Create character; Human; Monk | City selection opened | No character completed |
| Written Realms | Play; introduction start | Opening text, then loading screen | No controllable scene verified |
Can I test the connection without a character?
At the Icesus client, we chose Play from the welcome panel rather than starting the builder. The page reported a connection and presented a character-name prompt. We entered r and received six suggested names. Sending more produced another six-name set, replacing the suggestions with different names while leaving the client at character naming. This verifies an actual request and response before character login; it does not verify entry into a room. We stopped without choosing a name or creating a character.
Use that distinction when trying a text based RPG in a browser: a responsive name prompt establishes that the connection works. It says nothing yet about the quality of quests, the pace of combat or whether you will enjoy the community.
Can I inspect the character before registering?
In the Icesus builder, our visible draft began with Human selected and an Account step disabled. Continuing to Profession showed Soldier selected. We clicked Ranger. During the request, the detail panel described Ranger while the summary still showed Soldier and the continuation control was disabled. After the update settled, the checkmark, portrait description and draft summary all changed to Ranger, and the continuation control advanced toward upbringing. The page also told us that background choices had been updated to fit the profession. We did not treat the first changed label as a completed selection.
That makes the builder useful for inspecting a possible character before the account stage. Wait for the summary and next-step control to agree before continuing. The page displayed a browser-saved draft notice; we did not reload it or test recovery on another device, so this is not a persistence result.
What does a guest reach in Achaea?
The Nexus opening identified our session as a guest and offered separate controls for a new character and an existing one. We chose the new-character route, selected Human, then confirmed that race. A class catalogue replaced the race choices. Selecting Monk opened a class description; confirming it advanced to a city catalogue containing Ashtan, Cyrene, Eleusis, Hashan, Mhaldor and Targossas. The progress line retained Human and the Monk selection. We stopped at this city screen without choosing a city, entering credentials or completing a character. The sequence demonstrates a guest preview of successive creation choices, not guest access to an established character.
Choose this route if examining a race and class before deciding on a character matters to you. Do not read the guest label as a promise that an entire campaign needs no account.
Did Written Realms actually become playable?
Written Realms initially showed Log In and Sign Up beside its Play control. After Play, the visible navigation changed to Lobby and Log Out, although we had supplied no email address or password. An introductory overlay described a character trapped in a web with a fallen knife. Its loading label changed to a start invitation. Activating that invitation returned us to a loading state, and the later observation still showed loading rather than a controllable game scene. We recorded this stopping point instead of counting the introductory prose as a successful gameplay action.
This is a result from our session, not a diagnosis of the service or proof that other players cannot enter. If your attempt stops there too, try a different working entry rather than assuming the introductory paragraph is an interactive scene.
How is this different from an AI text adventure?
This check asks what a browser entry actually lets you do before registration. Our text RPG decision guide addresses a different choice: selecting a defined action, proposing an invented move or editing story direction. If generated narration is the priority, the AI RPG selection hub links to our inventory, knowledge and memory tests. None of those results establishes how these character-creation flows behave.
Open the route you prefer, perform its next visible action, and confirm that the resulting screen matches the choice you just made.