Rune Tooth
“Rune” establishes the opening, and “Tooth” supplies the second anchor. The physical matching direction makes this a candidate for quest keys, rather than a statement about the word’s historical origin. Distinguish the key’s visible identifier from the lock condition revealed later.
- Short form
- Rune Tooth
- Formal form
- Rune Tooth of the Old Road
Read the five-part design analysis
Construction & intended reading
“Rune” establishes the opening, and “Tooth” supplies the second anchor. The physical matching direction makes this a candidate for quest keys, rather than a statement about the word’s historical origin. Distinguish the key’s visible identifier from the lock condition revealed later. Name a progression item so players can identify it in an inventory without learning the solution prematurely. Its material or visible mark can connect it to the world before its exact use is known.
Sound & visible shape
This draft has 10 characters including spaces and punctuation, 2 visible word groups, and a longest letter group of 5 characters. The balanced sounds preference changes the ordering of candidates using visible English-letter patterns. It is a spelling heuristic, not a pronunciation recording or a linguistic quality score. Read the exact form aloud beside the nearest two names in your cast or map.
Background & scene
A key fits three doors, but its worn tag names the room the player must leave unlocked. The selected background is “An inherited tradition.” An older generation uses the name as a record of an obligation. Write one moment when the present bearer accepts, changes, or refuses that inherited explanation. In the fantasy role-playing frame, keep one visible object, relationship, or routine that lets the audience connect the name to this particular setting.
Short form, formal form & speaker
“You found Rune Tooth.” Keep the ordinary object type beside this title in an inventory. Reserve “Rune Tooth of the Old Road” for an inscription or a description if it is too long for the small label. The selected audience is “Everyday public use.” Use the form a resident or repeated reader could recognize without an explanatory footnote.
Revision & project checks
Avoid calling an unidentified item Final Vault Key before the final vault has been introduced. Test the result on a quest inventory, a locked-door prompt, and an item discovery log. A length limit can remove unsuitable drafts mechanically, but it cannot establish that a subtitle, map, or translated string will fit. Compare neighboring names, check unintended readings, and research third-party conflicts separately. Treat the crafted distinction as a creative emphasis, not a measured power level or a verified rarity.
These are creative interpretations and mechanical checks, not real-language etymology, user research, or rights clearance.
Take it into a scene
A key fits three doors, but its worn tag names the room the player must leave unlocked.
“You found Rune Tooth.” Keep the ordinary object type beside this title in an inventory. Reserve “Rune Tooth of the Old Road” for an inscription or a description if it is too long for the small label.
Open the game design laboratory 0 blockers · 0 review notes
A fictional, rule-based prototype. Counters are planning tokens, not measured or balanced game statistics.
1. Review this candidate against your project
- Display budget
- 10/28 characters
- With 30% expansion
- 13 characters — a planning estimate
- Project labels compared
- 0 supplied names
No conflict was detected by the enabled text checks. This is not a uniqueness, pronunciation, or rights clearance decision.
2. Identify and unlock · Story choice
Make the choice and its social consequence legible.
- Player action
- Inspect the matching mark
- Observable evidence
- the token’s circular opening matching the shutter’s projected mark
- Design constraint
- Avoid calling an unidentified item Final Vault Key before the final vault has been introduced. A refusal opens a different conversation; do not silently erase the original request.
| Branch | Consequence |
|---|---|
| Success | The token’s opening matches the projected circle and the permission is identified. |
| Setback | The player reaches a plausible lock without the required permission context. |
| Recovery | Find the former clerk before retrying the archive entrance. |
3. Rehearse the state changes
Inspect → commit → success or setback → recovery. Mode controls prerequisites and refunds; pressure controls planning capacity and cost.
Planning tokens: 6/6 · Attempt 0 · Evidence not inspected
4. Keep the public label within its information boundary
The selected name is revealed immediately in this prototype.
| Surface | Before discovery | After discovery |
|---|---|---|
| Inventory row | Rune Tooth | Rune Tooth |
| Interaction prompt | Inspect the matching mark: Rune Tooth | Inspect the matching mark: Rune Tooth |
| Collection record | Rune Tooth | Rune Tooth |
Designer-only fictional explanation
The token grants permission to leave an archive record unfinished.
This note is part of the published fictional exercise; it is separate from the proposed in-game interface copy.
5. Implementation handoff
- Prototype the entry condition on a quest inventory, a locked-door prompt, and an item discovery log.
- Show the token’s circular opening matching the shutter’s projected mark before asking the player to infer the result.
- Write the description available at pickup and remove knowledge the player has not earned.
The text export includes the brief, checks, branches, recovery plan, and interface labels. Rehearsal progress is temporary and is not a saved game.
