| Service | What we tried | Observed result | Collected | Source page |
|---|---|---|---|---|
| Perchance | Custom opening, Inspect, Pay, inventory-only follow-up | Inspect: 3 coins / 2 potions. Pay narrated; a further query returned 2 / 2. | 2026-10-15 | Page |
| AI Dungeon | Quick Play custom opening, then Inspect | 3 coins / 2 potions displayed; the gate opened without a Pay action. | 2026-10-15 | Page |
| FableAI | Custom Adventure as guest; Do: Inspect, then Pay | Inspect: 3 / 2 before and after. Pay: 2 coins / 2 potions. | 2026-10-15 | Page |
| Gameer | Follow Generate an RPG from its RPG landing page | Creator access required. Our custom prompt could not be submitted. | 2026-10-15 | Page |
| Rosebud | Paste the same prompt; select Generate your game | Sign in to Rosebud appeared; no generated game reached. | 2026-10-15 | Page |
| iWeaver | Select Input; paste the same prompt; select Create | Redirected to Login to your account; no generated material reached. | 2026-10-15 | Page |
Download the dated comparison (CSV)
The exact brief
Create a short playable RPG about a courier entering a locked observatory. Start with exactly 3 silver coins and 2 healing potions. The gatekeeper asks for 1 silver coin. Show the inventory before the choice. Offer Pay, Refuse, and Inspect the gate. Do not spend a coin until I choose Pay.
We tested the public interfaces in the same Chrome profile. The starting brief was identical wherever a prompt field was available. Gameer stopped us before that field, so its row is an access observation rather than a generation result. FableAI additionally required a character name and narrator notes: we entered Courier and “Use the supplied observatory setup. Keep inventory explicit.” No new accounts or subscriptions were created.
What changed inside the generated stories
On October 15, 2026, Perchance accepted our observatory brief and produced a gatekeeper demanding a silver coin. The opening did not display the requested inventory or the named Pay, Refuse and Inspect alternatives. After our inspection instruction, it supplied an inventory of 3 silver coins and 2 healing potions. Its payment response described handing over a coin and entering the grounds, but omitted the requested remaining totals. A separate inventory-only query then returned 2 silver coins and 2 healing potions.
On October 15, 2026, AI Dungeon let us enter Quick Play and submit the brief without signing in. Its selected model displayed Dynamic Small. The opening established the observatory and a gatekeeper but did not list the requested inventory or alternatives. We then instructed the character to inspect without paying or drinking. The reply listed 3 silver coins and 2 healing potions, yet also had the gatekeeper unlock and open the gate. We had not submitted a Pay action. Preserving the inventory therefore did not preserve the requested toll condition in this response.
On October 15, 2026, FableAI’s Custom Adventure accepted the brief through Play as Guest. The resulting story used narrator Azure. Its opening described the toll but did not display the requested inventory or named alternatives. We selected Do for the inspection instruction. The reply explicitly listed 3 silver coins and 2 healing potions both before and after examining the gate; the gatekeeper still demanded payment. After our Pay instruction, the story opened the gate and explicitly listed 2 silver coins and 2 healing potions. This sequence needed no additional inventory-only query.
Generation not reached
The blocked rows were collected on October 15, 2026. Rosebud allowed us to paste the complete brief into its game-description field, but Generate your game opened a sign-in dialog. iWeaver exposed its text field after we selected Input; Create then redirected to its login page. Neither attempt returned material we could inspect. Gameer’s creator-access screen prevented submission of our own brief. These are different stopping points, not measured failures of inventory handling.
What this comparison establishes
These are observations from the captured responses, not repeated trials or estimates of success rates. We did not equalize the underlying models, test long campaigns, reopen saved sessions or compare exported builds. The narrative text and visible inventory statements were inspected; no hidden inventory database was verified. A login barrier supplies no evidence that the requested RPG would succeed or fail after access.
For this toll scene, check two things separately: what the inventory says and whether the gate stays closed until the player pays. Our captured replies show why a correct coin total alone does not establish that a game condition was enforced.