These two AI Dungeon Story Cards give you a person and a place to enter manually, then a checklist for investigating why their information might not reach a reply. Start with useful card text before adding more triggers.
Documentation checked November 21, 2026 UTC. The examples are original non-explicit fiction with adult characters. We have not saved cards, inspected an account or context, or generated replies for this guide. EchoMelon publishes it and operates a competing story and character-chat product.
Give each field a clear job
In the official Story Cards guide, Entry supplies ordinary lore. Name labels; Type classifies; Notes annotate. Name/Type can inform the generator; Type/Notes serve Character Creator. Triggers select candidates. These are not privacy controls.
Use the following as manual field text, not an import file. Confirm the fields and saved values in your own instance. The separate AI generator may spend Credits; it is not needed to write these examples.
Card 1: Ora Selwyn
Name: Ora Selwyn
Type: Character
Triggers: Ora Selwyn
Entry:
Ora Selwyn, 42, is an umbrella repairer at Copper Arcade.
Finished umbrellas hang on the green rail by Ora's counter.
Ora matches each collection to a numbered ticket.
If the ticket is missing, Ora asks for a description and checks
her repair ledger before offering an umbrella.
The visitor chooses whether to continue the collection process.
Notes:
Author check: retain the collection procedure when revising Ora;
change it only after a deliberate premise change.
The Entry identifies its subject without relying on the card's label. It gives Ora something concrete to do when someone lacks a ticket. It neither promises that the ledger will identify an umbrella nor decides that the visitor accepts a particular one.
Card 2: Copper Arcade
Name: Copper Arcade
Type: Location
Triggers: Copper Arcade
Entry:
Copper Arcade is a covered pedestrian passage connecting Bell Street
to Ash Square. Ora Selwyn's umbrella-repair counter stands near the
Bell Street end. A tea kiosk stands near the Ash Square end.
The green rail beside Ora's counter holds finished repairs;
it is not a public umbrella loan rack.
Notes:
Author check: preserve the two street ends when revising directions.
Keep temporary crowds and the player's current position elsewhere.
The place card supplies a layout and the purpose of one object. It does not place the player at either end, set the weather or claim a repair has been collected. Mentioning Ora here, or Copper Arcade in Ora's Entry, is not proof that another card was automatically inserted; check each Entry separately.
Repair a fact left in metadata
Suppose Ora's earlier draft had the same Type and Triggers, but these fields:
Name: Ora Selwyn, 42 — umbrella repairer at Copper Arcade
Entry: Finished umbrellas hang on the green rail by her counter.
Notes: Ora matches each collection to a numbered ticket. If the ticket
is missing, Ora asks for a description and checks her repair ledger
before offering an umbrella. The visitor chooses whether to continue
the collection process.
The collection rule is present in your draft, but outside the ordinary lore field. The Entry also says “her” without identifying whose counter it describes.
Card 1 repairs that draft by moving the identity and collection rule into Entry. The age, occupation, location, rail and ticket condition stay the same. Notes becomes a maintenance reminder. This is an editorial repair, not evidence that a model obeyed the revised card. Keep an old copy so you can see exactly what you moved.
Put the immediate goal elsewhere
Plot Essentials is intended for important current information. For a proposed opening with player character Jules Daven, 35, use a short separate premise:
Jules Daven is visiting Copper Arcade to identify their repaired umbrella.
Jules has no collection ticket. Jules has not chosen whether to ask Ora
for a ledger check or leave and look for the ticket.
That is starting text, not an event already played. It avoids rewriting the stable cards every time Jules considers another action. For broader event maintenance, our recap guide covers a different task.
Plan literal trigger checks
Triggers ignore capitalization but preserve spaces and can match inside other words. The following are unrun diagnostic cases, not observed engine results. “Candidate” means only a text-match expectation from the documentation; Entry inclusion and output use remain unknown in every row. Each row is a separate proposed Trigger-field variant of Ora's card, not successive results from running both cards.
| Trigger field | Exact sample text | Candidate expectation |
|---|---|---|
Ora Selwyn |
Ora Selwyn checks the ledger. |
Name candidate. |
Ora Selwyn |
ora selwyn checks the ledger. |
Case variant remains a candidate. |
Ora |
The storage cupboard is shut. |
Substring candidate despite no character mention. |
Ora Selwyn, Copper Arcade |
Copper Arcade is quiet. |
Leading space in second trigger prevents this match. |
Ora Selwyn ,Copper Arcade |
Ora Selwyn. |
Trailing space in first trigger prevents this match. |
The fourth sample starts directly with Copper, without a preceding space. The fifth has a period immediately after Selwyn. Those details make the space checks meaningful. Prefer the full name over Ora to avoid the illustrated storage collision; it does not eliminate every possible false match.
For a first mention introduced by AI output, plan this timeline:
- Before output 1, inspect the recent text for earlier triggers. If
Ora Selwynfirst appears midway through output 1, its newly triggered Entry cannot inform that already-started output. - For output 2, inspect whether the Entry is actually included. Treat inclusion as possible, not established by the mention alone.
Neither output was generated here. A later input without the name is not a clean negative check if earlier history still contains it.
Record four separate observations
The context assembly guide explains that recency, frequency, card length and available space affect selection. Trigger checks consider recent actions beyond the last message. Even components classified as Required, including Plot Essentials, can be trimmed or omitted when over budget.
Use the documented Context Viewer where available; we have not operated it. Record these separately:
Date; account/model/context settings: NOT CHECKED
Card fields saved and reopened: NOT VERIFIED
Relevant recent text and candidate trigger: NOT RUN
Complete Entry found in sent context: NOT INSPECTED
Raw first reply and later retries: NOT COLLECTED
Reply preserves collection rule and player choice: NOT TESTED
If the Entry is absent, investigate fields, recent history and budget before rewriting Ora. If it is present but contradicted, retain the actual reply and look for conflicting context. A plausible umbrella answer alone proves neither insertion nor reliable memory.
For the broader workflow, read our AI Dungeon review. To find a character for another story, browse EchoMelon's English character directory.
Comments
Join the discussionNo comments yet. Be the first to comment.

