Trace Shard
“Trace” establishes the opening, and “Shard” supplies the second anchor. The recorded memory direction makes this a candidate for save crystals, rather than a statement about the word’s historical origin. Keep the fictional crystal identity separate from what the save action actually preserves.
- Short form
- Trace Shard
- Formal form
- Trace Shard of the Old Road
Read the five-part design analysis
Construction & intended reading
“Trace” establishes the opening, and “Shard” supplies the second anchor. The recorded memory direction makes this a candidate for save crystals, rather than a statement about the word’s historical origin. Keep the fictional crystal identity separate from what the save action actually preserves. Name an in-world saving object with a recognizable material and ritual. Its atmosphere should support the interaction while interface text explains exactly when and what the player can save.
Sound & visible shape
This draft has 11 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 crystal records a campfire’s shadow but refuses to preserve a scene while someone is still speaking. 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 Trace Shard.” Keep the ordinary object type beside this title in an inventory. Reserve “Trace Shard 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
Do not use Permanent Memory for an object that stores only a temporary checkpoint. Test the result on a save prompt, a slot list, and a checkpoint confirmation. 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 crystal records a campfire’s shadow but refuses to preserve a scene while someone is still speaking.
“You found Trace Shard.” Keep the ordinary object type beside this title in an inventory. Reserve “Trace Shard 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
- 11/28 characters
- With 30% expansion
- 15 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. Save and confirm · Story choice
Make the choice and its social consequence legible.
- Player action
- Record the camp
- Observable evidence
- a completed conversation followed by an explicit save confirmation
- Design constraint
- Do not use Permanent Memory for an object that stores only a temporary checkpoint. A refusal opens a different conversation; do not silently erase the original request.
| Branch | Consequence |
|---|---|
| Success | The scene ends and a text confirmation states that progress is saved. |
| Setback | A companion is still speaking; the request is not yet complete. |
| Recovery | Finish the conversation and request a new confirmed record. |
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 | Trace Shard | Trace Shard |
| Interaction prompt | Record the camp: Trace Shard | Record the camp: Trace Shard |
| Collection record | Trace Shard | Trace Shard |
Designer-only fictional explanation
The facets preserve the campfire shadows after the story is finished.
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 save prompt, a slot list, and a checkpoint confirmation.
- Show a completed conversation followed by an explicit save confirmation before asking the player to infer the result.
- Specify whether the object creates a manual save, checkpoint, or temporary return point.
The text export includes the brief, checks, branches, recovery plan, and interface labels. Rehearsal progress is temporary and is not a saved game.
