World Editor Field Reference

Search the public World Editor fields that make up a Codex. Internal sources, retired simulation fields, and legacy plot controls are excluded.

Search fields

110 fields

basic.mainCharacter

Main Character

Entity fields

Marks this character as a likely viewpoint protagonist.

• Use for lead characters the player may embody or follow closely.
• Keep the list small so cover art, starting context, and player focus stay clear.
• Do not mark every important NPC as a main character.
• Only the author sets it, with the Main character switch on the entity; the World Edit helper and outside agents cannot.

Example

Use for the primary hero, reincarnated lead, party viewpoint, or central playable figure.

basic.tags

Tags

Entity fields

Short searchable labels used to group and retrieve this entity.

• Use up to a few compact tags, separated by commas.
• Prefer concrete query words: faction, location role, species, threat, theme.
• Avoid repeating the same words already used in the brief when possible.
• At most 50 characters per tag.

Example

ghost,rebirth,immortal,clan,rival

basic.brief

Brief Summary

Entity fields

One short reference line describing the entity hook.

• Make it specific enough to identify why this entity matters.
• Use it as a quick scan line, not a full backstory.
• Avoid generic phrases like mysterious figure or powerful artifact.
• At most 200 characters.

Example

A dry well that glows at night and drinks memories instead of water.

race

Race

Entity fields

Species or lineage reference for a character.

• Select an existing Race entity instead of typing a loose value.
• Use this for biological, metaphysical, or culturally recognized lineage.
• Create a Race entity first if the lineage needs lore, culture, lifespan, or abilities.

Example

Eldergrove Sylphs

gender

Gender

Entity fields

Character gender or culturally equivalent identity marker.

• Use the wording natural to the setting.
• Keep it concise; put social customs or restrictions in description or culture fields.

Example

female

alias

Alias

Entity fields

Known names, titles, nicknames, or cover identities.

• Use multiple entries when names come from different groups or eras.
• Each alias should help retrieval or roleplay, not just repeat the real name.

Example

The Ashwalker; The Shadow

originLocation

Origin Location

Entity fields

Specific place where this entity came from or first became relevant.

• Choose a Location or Region that already exists in the world.
• Use origin for background; use relations for current location or ownership.

Example

Volcanic Village

originRegion

Origin Region

Entity fields

Large region tied to the entity origin or cultural root.

• Use this when the exact place is less important than the territory or biome.
• Prefer a Region entity ID or name already present in the world.

Example

Northern Glass Wastes

originFaction

Origin Faction

Entity fields

Group, clan, nation, school, or institution tied to the entity origin.

• Use for inherited allegiance, training background, or institutional roots.
• Current allegiance should be represented through relations when possible.

Example

Whisperwind Clan

bloodline

Bloodline

Entity fields

Inherited family, house, or metaphysical lineage.

• Use when ancestry changes status, abilities, social treatment, or fate.
• Avoid decorative surnames with no consequence.

Example

House Darion

bornAt

Born At

Entity fields

Birth time aligned with the world starting time.

• Use the world time format from the premise when possible: hh:mm dd/mm/yyyy.
• Store the date, never an age: an age goes stale as story time moves, a birth date does not.
• Age should make sense relative to the Starting Time.

Example

08:40 12/05/2001

diedAt

Died At

Entity fields

Death time if the character is dead, undead, reincarnated, or historically recorded.

• Leave unset for living characters.
• If used, keep it consistent with age, backstory, and current state.

Example

16:40 01/12/2030

emergedAt

Emerged At

Entity fields

Time when a race, species, or lineage appeared in history.

• Use for origin myths, mutations, divine creation, or ecological emergence.
• Keep it consistent with the world chronology.

Example

00:00 01/01/0047

foundedAt

Founded At

Entity fields

Founding time of a faction or institution.

• Use a date that supports the faction age, authority, and historical memory.
• If the founding is disputed, explain the dispute in ideology or historical notes.

Example

12:00 03/04/0911

createdAt

Created At

Entity fields

Creation time for an item, object, construct, or relic.

• Use when age, maker, or historical timing affects the object meaning.
• Pair with creator or originLocation when those are known.

Example

23:10 09/09/1204

backStory

Back Story

Entity fields

Character history that explains current drive and friction.

• Explain how the character became who they are now.
• Use concrete causes, losses, obligations, training, debts, or shame.
• Avoid trauma that only decorates the character without changing behavior.

Example

Born as the second son of the Whisperwind chieftain, trained in swordsmanship from age six...

historicalNotes

Historical Notes

Entity fields

Useful history tied to a location or place.

• Capture events that still affect access, factions, taboos, danger, or rumors.
• Prefer modular entries over one vague paragraph if there are multiple facts.

Example

Siege: the north gate still bears glass scars from the nine-day siege.

foundingMyth

Founding Myth

Entity fields

Mythic story explaining why a region exists or matters.

• The myth may be false, but it should shape culture, law, fear, or identity.
• Do not use it as a plain history summary.

Example

The valley is said to have formed where a moon-serpent shed its first skin.

creator

Creator

Entity fields

Entity or faction that made, founded, authored, or engineered this entity.

• Applies to Character, Object, Creature, and Item.
• Select an existing Character or Faction when possible.
• Use relations when the creator link should be graph-queryable long term.

Example

Whisperwind Clan

persona

Persona

Entity fields

Stable character psychology and observable behavior in one prose block.

• Cover archetype, outward face, social mask, voice style, shadow leak, body language, triggers, and interesting facts in compact prose.
• Keep it roleplay-ready: specific, observable, and repeatable across scenes.
• Avoid restating backstory; focus on how this character acts and reacts under pressure.
• At most 700 characters (roughly 70-110 words).

Example

Ruler-Warrior archetype. Outward face: authoritative, measured, vigilant. Social mask: keeps one-step distance, softens with children. Voice: slow and deliberate, last syllable drags when sarcastic. Shadow leak: title-flex and cold stare when challenged. Body language: taps sword hilt while thinking, scans exits on entry. Triggers: public disrespect, tense unfamiliar rooms. Quirks: prefers cold tea, stacks small stones while waiting.

secretInfos

Secret Infos

Entity fields

Hidden facts the player may discover later.

• Use secrets that create future choices, leverage, risk, or emotional reversal.
• Do not put public biography here.

Example

Knows the shrine key was never lost, only renamed.

longTermGoals

Long Term Goals

Entity fields

Durable motivations that keep a character active beyond one scene.

• Goals should create future pressure, alliances, betrayals, or quests.
• Prefer concrete objectives over vague destiny language.

Example

Secure legal control of the river gate before winter taxes are counted.

knowledge

Knowledge

Entity fields

What this character knows of the world: the only picture of it they act from when they play their own part.

• In play, each character decides their own moves from who they are, what they remember and this field. They never read the premise, its hidden truths or anyone else's notes: what is not here, and not lived in play, they do not know.
• Write it from where they stand: what someone of their place, trade, age, schooling and travels knows of the world (its powers, laws, places, history, peoples, dangers) and how they came to know it: saw it, were taught it, heard it at market.
• Name the edges: what they know only as rumor, what they believe that is false, what they have never heard of. A farmhand knows the price of grain and the local lord's name, not the court's politics or the true cause of the war.
• The world's secrets stay out unless this character truly holds them. Their own secrets belong in Secret Infos.
• Write what they know when the story opens (before turn 1), never what the story will show them later: that reaches them in play, and a later state of their knowledge is a variant.
• Absolute values: years and named places, never "last year" or "up north from here".
• At most 1500 characters (roughly 150-250 words).

Example

Born and raised on the Saltmarket docks of Vey: knows every pier, which captains pay on time, which customs clerks take bribes, and the smugglers' signal lamps. Reads numbers and ship marks, not books. Knows the Harbor Guild runs the port and that the Duke raised the salt tax in 1203; believes the Duke is ill because the guild says so. Knows the sea witches of the Shroud Isles only from sailors' stories and does not believe them. Has never left Vey, knows the capital only by name, and has seen magic used only by the temple healers.

appearance

Appearance

Entity fields

Stable visual description used for scene writing and image generation.

• Define repeatable traits that remain recognizable across scenes and art styles.
• Use fixed colors, shapes, silhouettes, materials, symbols, scars, and accessories.
• For characters, cover build, eyes, face, hair, clothing, and notable features in one prose block.
• For locations or creatures, describe visible structure, scale, mood, and recurring markers.
• Absolute values only: the image model reads this field alone. Never name another character or compare with one ("a year older than Theo", "her mother's eyes"); state the apparent age in years, the color, the size.
• At most 700 characters (roughly 60-110 words).

Example

Build: tall, narrow-shouldered, dancer-like balance; old blade scar on right forearm. Face: heart-shaped, soft jawline, faint beauty mark beneath left eye. Eyes: storm-gray with electric-blue flecks, sharp outer corners. Hair: raven-black with icy teal gradient, waist-length, wavy, center-parted. Clothing: indigo battle robe with silver wind-glyph trim, loosened sash, sandals, silver anklet on left ankle. Notable features: jagged cheek scar, crescent earring on left ear, black glass prayer beads on right wrist.

appearanceMarkers

Appearance Markers

Entity fields

Shared visible markers of a race, lineage, or species.

• Use traits that identify members at a glance: ears, scale pattern, eye ring, scent, posture, clothing adaptation.
• Distinguish shared species traits from individual character appearance.

Example

Eyes: vertical amber pupils
Skin: pale bark-like veins along wrists

level

Level

Gameplay

Universal power and attribute unit for stats and gauges.

• 1 Level equals 1 attribute point in the world rules.
• Level-related values must follow Gameplay Properties.
• Keep level consistent with rank, danger, stats, and region difficulty.

Example

1200

stats

Stats

Gameplay

Entity attribute values using keys defined in Gameplay Properties.

• Only use stat names already defined in Gameplay Properties / Stats.
• Values should make sense with level: total stats should stay near the level budget rule defined for this world.
• Prefer concrete numbers or formulas that can drive gameplay checks.

Example

Magic 15
Combat 9
Stealth 4

gauges

Gauges

Gameplay

Dynamic bars like HP, Mana, Sanity, Corruption, or Favor.

• Only use gauge names already defined in Gameplay Properties.
• Gauge values should follow the formulas and trigger logic in the world rules.
• Use current/max or concise numeric state when useful.

Example

HP 55/100
Mana 18/30
Corruption 7/100

abilities

Abilities

Entity fields

Powers, skills, techniques, or innate traits available to the entity.

• Use names and effects that match the world rules.
• Prefer modular entries with unlocks, cost, limits, or requirements.
• Avoid vague power labels without observable effect.
• One entry per ability: its name (at most 50 characters) and its effect, cost, limit and tell in at most 200 characters.

Example

Flamewalk: crosses fire for 3 turns; costs Mana proportional to burn intensity.

requiredStats

Required Stats

Gameplay

Minimum stats needed to use an item, object, or ability.

• Use stat names from Gameplay Properties only.
• Write checks in a compact, verifiable form.

Example

Swordsmanship >= 20

effect

Effect

Entity fields

Functional outcome of an item or object.

• Describe what changes when it is used, equipped, consumed, or activated.
• Include limits, risks, or costs if those are essential to balance.

Example

Reveals invisible oath-marks for one scene; fails in direct sunlight.

usageLimit

Usage Limit

Entity fields

How often or under what conditions the item can be used.

• Use clear constraints: per turn, per day, after recharge, only in location, requires cost.
• Avoid soft limits like only by the worthy unless the check is defined elsewhere.

Example

Once per dusk; recharges after absorbing a truthful confession.

category

Category

Entity fields

Ability category, school, technique type, or item grouping.

• Use compact labels that help filtering and balance.
• For abilities, categories can be magic, skill, innate, forbidden, ritual, or world-specific schools.

Example

forbidden,ritual,blood-magic

description

Description

Entity fields

Narrative body text for Object, Myth, or Lore entities.

• Write concrete content the writer and simulator can reuse: story, meaning, physical detail, or cultural weight.
• For Myth and Lore, explain what is believed or known and how it shapes the world.
• For Object, describe construction, function, wear, and scene-relevant detail beyond condition.
• Keep it medium length — specific enough to guide scenes, not a full essay.

Example

The lantern only lights near true north. Priests claim its flame is a fragment of the first dawn, still bound by a forgotten oath.

costBase

Cost Base

Gameplay

Default resource cost for an ability.

• Reference gauges, stats, currency, or world resources defined in Gameplay Properties.
• Keep the cost formula short and reusable.

Example

Mana = 3 + intent intensity; HP +1 if cast inside cursed rain

cooldownBase

Cooldown Base

Gameplay

Default cooldown or recovery time for an ability.

• Use turns, seconds, scenes, rests, dawn/dusk, or world-specific cycle units.
• Cooldown should reflect power, risk, and genre pacing.

Example

3 turns; reset early if the caster breaks an oath

usageRestriction

Usage Restriction

Entity fields

Rules that block, weaken, or shape ability usage.

• Write restrictions that can be checked in play.
• Good restrictions create tactical choices, social risk, or narrative cost.

Example

Cannot be used while Sanity < 30 or inside consecrated courts.

climate

Climate

Entity fields

Weather and environmental pattern of a region.

• Mention conditions that affect travel, survival, economy, culture, or combat.
• Avoid generic labels if a concrete seasonal pattern is available.

Example

cold salt fog most mornings; glass storms every seventh dusk

commonResources

Common Resources

Entity fields

Materials, crops, energy sources, animals, or trade goods found in a region.

• Use resources that explain economy, conflict, crafts, or faction interest.
• Prefer concrete resource names over generic wealth.

Example

ironwood,blue-salt,stormglass,reed-rice

accessMethod

Access Method

Entity fields

How characters reach or enter a location.

• Include physical route, gate condition, social permission, ritual, danger, or cost.
• This should help scene planning and quest gating.

Example

Open only at low tide; travelers must carry a silver lantern or be redirected by mirror fog.

habitat

Habitat

Entity fields

Natural environment where a creature lives.

• Tie habitat to behavior, danger, reward, ecology, and local rumors.
• Use specific terrain, time, and conditions when possible.

Example

mangrove crypts where moonlight reaches standing water

behavior

Behavior

Entity fields

Observable creature or NPC behavior pattern.

• Describe actions, triggers, hunting style, social habits, or avoidance patterns.
• Use behavior that can influence encounters and consequences.

Example

stalks reflections instead of bodies; retreats if its name is spoken backward

rewardExperience

Reward Experience

Entity fields

EXP or progression reward for defeating, resolving, or studying a creature.

• Keep the reward consistent with level, threat, and world leveling rules.
• Use zero or low values when violence should not be the main solution.

Example

120

lifespan.matureAtYears

Mature At Years

Entity fields

Age when this race is treated as physically or socially mature.

• Use numbers that fit biology, culture, and power growth.
• If social maturity differs from biology, explain that in culture notes.

Example

18

lifespan.averageYears

Average Lifespan

Entity fields

Typical lifespan for this race or species.

• Keep it consistent with history, population, reproduction, and social memory.

Example

120

lifespan.maxYears

Max Lifespan

Entity fields

Upper known lifespan limit for this race or species.

• Use for rare elders, ancient rulers, or biological limits.
• If immortality exists, explain its cost elsewhere.

Example

300

ideology

Ideology

Entity fields

Faction beliefs, doctrine, or justification for action.

• Write what the group claims to value and what that belief enables or excuses.
• Good ideology creates contradiction, loyalty, oppression, or conflict.

Example

Order is mercy: every citizen must be indexed so no grief can go unaccounted.

scope

Scope

Entity fields

Scale of a faction influence or operation.

• State whether it is local, regional, continental, hidden, official, or cross-world.
• Use scope to calibrate resources and political reach.

Example

regional temple network with covert influence in river courts

headquarters

Headquarters

Entity fields

Main base or seat of power for a faction.

• Choose an existing Location or Region.
• If the headquarters is hidden or mobile, explain that in scope or relations.

Example

Iron Quarter Citadel

symbol

Symbol

Entity fields

Recognizable emblem, banner, mark, or visual identity of a faction.

• Use symbols that can appear in clothing, flags, documents, seals, or architecture.
• Tie it to belief, history, or intimidation when possible.

Example

a black heron holding a silver nail

initialLeader

Initial Leader

Entity fields

Founder or first leader of a faction.

• Select an existing Character when possible.
• Use this for origin identity; current leadership can be modeled separately.

Example

Mother Veyra

condition

Condition

Entity fields

Current state, damage, curse, activation state, or physical condition.

• Use for items and objects whose state changes usefulness or risk.
• Keep it concrete and scene-actionable.

Example

cracked but functional; hums when a liar touches the handle

material

Material

Entity fields

Main substance or construction material of an object.

• Use materials that imply weight, durability, cost, origin, or magical properties.

Example

black basalt threaded with stormglass

purpose

Purpose

Entity fields

Designed function or ritual role of an object.

• Explain why the object exists and what it enables.
• If the purpose changed over time, mention the current use elsewhere.

Example

anchors court oaths so spoken contracts can be audited by priests

isUnique

Is Unique

Entity fields

Whether this item or object is one-of-a-kind.

• Turn on for relics, named artifacts, or irreplaceable quest objects.
• Leave off for repeatable equipment, currency, or common resources.

Example

true

statement

Statement

Entity fields

Canonical truth represented by a Fact entity.

• Write the fact as a clear claim that affects lore or decisions.
• Avoid opinions unless the fact is about a belief held by a group.

Example

No mirror in the capital reflects the royal family after sunset.

source

Source

Entity fields

Where a fact or claim comes from.

• Use witness, archive, faction record, experiment, prophecy, or rumor source.
• Source quality can create doubt or investigation hooks.

Example

sealed court ledger copied by the River Monks

discoveredAt

Discovered At

Entity fields

Time when a fact became known or recorded.

• Use when discovery timing matters to politics, science, faith, or secrecy.

Example

09:00 21/07/1241

occurredAt

Occurred At

Entity fields

Time when an event happened or is scheduled to happen.

• Use exact world time when possible.
• If the event is uncertain, explain uncertainty in summary or consequence.

Example

13:00 17/10/1409

location

Location

Entity fields

Place where an event happened or primarily matters.

• Select an existing Location or Region.
• Use relations for broader territorial or ownership links.

Example

Ashfall Village

summary

Summary

Entity fields

Concise event summary and stakes.

• Describe what happened and why it matters later.
• Do not turn it into a full scene transcript.

Example

Mount Vael erupts and threatens nearby settlements.

consequence

Consequence

Entity fields

Lasting result caused by an event.

• Use concrete changes to factions, places, resources, beliefs, or relationships.
• Good consequences remain useful many turns later.

Example

Refugees flee south; ash taxes triple; the old shrine route becomes impassable.

originHint

Origin Hint

Entity fields

Partial clue for an Unknown entity origin.

• Use only enough information to guide later resolution.
• Unknown entities should be resolved promptly when the world reveals enough context.

Example

smells of river salt but leaves desert glass behind

observedEffect

Observed Effect

Entity fields

What people have directly seen this Unknown entity do.

• Use observable evidence, not explanation.
• This field helps investigation scenes stay grounded.

Example

candles bend toward it; written names fade within three breaths

needsResolution

Needs Resolution

Entity fields

Question or uncertainty that should eventually be answered.

• Frame the unresolved issue clearly so future turns can close it.

Example

Determine whether it is a creature, curse residue, or faction-made device.

imageUrl

Image URL

Entity fields

Generated or uploaded image used to represent this entity.

• Read-only here. Edit images through the image panel.
• A stable appearance description helps future regeneration stay consistent.

imagePrompt

Image Prompt

Entity fields

Prompt used to generate the entity image.

• Read-only here. It is kept for audit and regeneration context.
• Improve appearance fields if regenerated images are inconsistent.

relation.type

Relation Type

Relations

Meaningful UPPER_SNAKE_CASE label that connects two entities.

• Use a precise long-term relation, not generic RELATED_TO or CONNECTED_WITH.
• Directed relation order matters: A-[ADMIRES]->B means A admires B.
• Reuse the same type string consistently for the same meaning across the world.

Example

OWNS, SERVES, MENTORS, LOCATED_IN, BORDERS, BOUND_TO

relation.source

Source Entity

Relations

Entity on the left side of the relation.

• For directed relations, source is the actor, holder, believer, owner, or dependent side — whatever makes sense for that relation type.
• Changing source changes the graph meaning.

Example

A in A-[OWNS]->B

relation.target

Target Entity

Relations

Entity on the right side of the relation.

• For directed relations, target is what the relation points to.
• Use entity IDs, not display labels or names.

Example

B in A-[OWNS]->B

relation.direction

Direction

Relations

Whether this relation is directed, reversed, or truly two-way.

• Prefer directed because they preserve causality, authority, ownership, belief, and dependency.
• Use undirected only when symmetry is semantically true and useful for queries.

Example

forward: A-[TYPE]->B; undirected: A-[TYPE]-B

relation.since

Since

Relations

When the relation began or became relevant.

• Use world time if known.
• Leave blank if timing is unknown or not useful.

Example

09:00 21/07/1241

relation.status

Status

Relations

Current activity state of the relation.

• Active means it currently affects behavior or world state.
• Dormant, Broken, or Hidden can preserve long-term memory without overstating present action.

Example

Active

relation.brief

Relation Brief

Relations

Short natural-language meaning of the relation.

• Do not repeat entity names.
• Explain why the entities will still matter to each other later.
• Write it as it stands when the story opens (before turn 1), never as events the story will play; when one side does not know it, say who.
• Prioritize emotional, political, economic, historical, cultural, territorial, or causal links.
• At most 200 characters.

Example

Bound by an oath that transfers every broken promise into physical debt.

name

Name

Entity fields

Human-readable name shown to users.

• Use a name that feels natural in the world language and genre.
• A memorable imperfect name is better than a forced perfect name.

Example

City Of Copper Mirage

id

ID

Entity fields

Stable internal identifier used by relations and references.

• No spaces or special characters for entity IDs.
• Do not use generic numbering like entity_001 unless the setting itself justifies it.
• Changing IDs can break references, so edit carefully.

Example

CityOfCopperMirage

label

Label

Entity fields

Entity type used for filtering, generation, and editor forms.

• Choose the most useful simulation category: Character, Item, Location, Region, Race, Creature, Faction, Ability, Event, Myth, Fact, Object, or Unknown.
• Unknown should be resolved when enough information exists.

Example

Character

brief

Brief

Entity fields

Short hook or summary for quick scanning.

• Keep it compact and specific.
• Use details that make the item distinguishable at a glance.
• At most 200 characters.

Example

A major guild fractures after a bitter leadership dispute.

startingTime

Starting Time

Premise

Fictional world time when play begins.

• Use 24-hour format when possible: hh:mm dd/mm/yyyy.
• Age should make sense relative to the Starting Time.

Example

08:00 01/01/407

genreTags

Genre Tags

Premise

Up to a few genre labels describing the world tone and market shape.

• Use tags that help users understand the promise quickly.
• Keep tags broad enough to search but specific enough to set expectations.

Example

Isekai, Dark Fantasy, Reincarnation, Faction War

authorStyle

Author Style

Premise

Tone, pacing, and prose influence for the world.

• Use a concise style guide, and name a writer, work or school when the prose should take their voice (a parody names its target).
• This affects narration, comedy level, tragedy, and emotional distance. It outranks the writer's default voice (a light novel told close to the protagonist).

Example

Grim logic and moral extremity; characters collapse under ideology.

storyDescription

Story Description

Premise

High-level world premise and systemic conflict.

• Use 2 or 3 sentences that hook the fantasy concept and simulation conflict.
• Write this in natural language that hooks the reader.

detailInstruction

Detail Instruction

Premise

How the player experiences systems, choices, and consequences.

• Explain how actions unlock paths and close others.
• Balance small moment immersion with long-term systemic consequence.

backstory

Backstory

Premise

Foundational past of the world, not the player character.

• Describe lore, myths, catastrophes, or prior conflicts that shaped the current structure.
• Do not describe the protagonist here.

worldRules

World Rules

Premise

Metaphysical and mechanical laws of the setting.

• Define costs, limits, territory shifts, magic laws, death rules, faction karma, or reincarnation price.
• Rules should feel usable as game or world logic.

Example

SpellCasting: magic requires chanting and Mana unless mastered.

hiddenTruths

Hidden Truths

Premise

Invisible forces that push the world forward.

• These are not public backstory or plot summary.
• Use neutral, systemic truth: selection logic, exploitation, constraints, or trade-offs.
• They can contradict public myths and should exist even if the player never appears.

Example

Systemic reincarnation: reincarnation exists to recycle flawed souls rather than redeem them.

gameplayProperties.stats

Gameplay Stats

Gameplay

Core attributes used for checks, growth, and interaction logic.

• Each stat should combine a name with mechanical and narrative function.
• Name it with a word players already know from games and anime (Strength, Charm, Luck): the Player sheet shows only the name and a number, never this description.
• All entity stats must use these keys.
• Do not reference variables that are not defined in Gameplay Properties.

Example

Magic: converts emotion into elemental spells, costs mana proportional to intent intensity

gameplayProperties.gauges

Gameplay Gauges

Gameplay

World or character condition bars that update dynamically.

• Usually include HP if the world tracks health.
• Name the bar so it explains itself: a familiar word that also says whether higher is good (HP, Stamina, Sanity, Heat). Players never read the premise; a lore term such as Signal belongs in the description, not the name.
• Define mechanics, trigger conditions, and formulas clearly.
• All entity gauges must use these keys.

Example

HP: 0 = death; restored via rest or items
Mana: regenerates 1 + stats.Magic per turn

gameplayProperties.currency

Currency

Gameplay

Money or trade resources used by the world economy.

• One line per currency: the key is the currency name, the value is what it buys, hires, or indebts.
• Can vary by region if the narrative needs it.
• Use currencies that affect trading, hiring, debt, taxes, or faction pressure.

Example

Crowns: official capital coin
SaltScript: contract-backed river currency

gameplayProperties.levelingSystem

Leveling System

Gameplay

How EXP, levels, rewards, and scaling work.

• Keep it scalable, thematic, and math-consistent.
• Level is the universal attribute unit in the world rules.
• Lines: description (how EXP and levels work), then one line per aspect such as experience, rewards, or scaling.
• Ranks do not go here; they belong in Rank System.

Example

description: Levels come from resolving threats, not grinding
experience: max EXP starts at 10 and increases by 10 percent per level

gameplayProperties.rankSystem

Rank System

Gameplay

Ordered progression ranks with social, mechanical, and metaphysical meaning.

• One line per rank, lowest first: the key is the rank name, the value is its level range, what it handles and unlocks, and what still kills it.
• Use at least 5 ranks in one consistent conceptual system.
• Each rank should gate zones, change relationships, shift mechanics, or unlock systems.
• Rank escalation should feel like transformation, not just a bigger number.

Example

Unmarked: levels 1-4; safe only inside the wards
Ashmarked: levels 5-9; survives minor curse zones but is distrusted by temple guards

gameplayProperties.powerReference

Power Reference

Gameplay

Reference scale for comparing power, threats, zones, and ranks.

• One line per reference point: the key is who or what, the value is its level range.
• Use this to keep level, stats, danger, and rank consistent across entities.
• Good references prevent random overpowered values.

Example

Village guard: level 3-8
Regional champion: level 80-120

phase.phaseName

Phase Name

World Phases

Short label for this story stage on the phase graph.

• Use a name the author can scan quickly on the canvas.
• Prefer concrete stage titles over generic Step 1 / Step 2 labels.
• Keep it distinct within the same cast branch (Global or main character).

Example

Arrive in the ruined capital

phase.descriptionPlayer

Player Description

World Phases

Reader-facing summary of what this phase feels like.

• Write in plain language the player could read as context or UI copy.
• Describe the situation and stakes, not internal director notes.
• Keep it short enough to skim; put internal story context in Phase Content and transition rules in Progression Logic.

Example

You wake among ash and broken towers. The city still breathes, but nothing trusts a stranger.

phase.descriptionLLM

Phase Content

World Phases

Internal definition of the story state while this phase is active.

• Describe the dramatic purpose, current world state, active pressures, and desired tone.
• State the important conditions that should remain true throughout the phase.
• Give Director, Writer, and Simulation enough context to improvise several consistent turns.
• Describe a flexible narrative space, not a fixed chapter outline, exact dialogue, or mandatory scene sequence.
• Say the situation this phase opens on and its time scale (one night, a season, years): the next phase is chosen from this text alone. Exit and branch conditions go in Progression Logic.
• Optional labeled lines keep long phases scannable: PURPOSE, STATE, PRESSURES, OBJECTIVE, KR1-KR3, TONE, BG LINK.
• OBJECTIVE is one verifiable end-state for this stage; KR lines are observable results a reader could check, never chapter task lists.
• PRESSURES names the active forces, factions, or scarcity squeezing the cast here.

Example

Opening survival phase in a ruined capital. Food is scarce, locals distrust outsiders, and rumors point toward a sealed royal vault. Keep the protagonist under-informed and dependent on local knowledge. Tone is tense, lonely, and grounded.

phase.isEnding

Story Ending

World Phases

Marks this phase as a story ending. Landing here ends the play session choices.

• IMPORTANT: An ending node MUST NOT have any next phase. Remove outbound connections before enabling Ending.
• Use the flag button on the phase node (not the details panel) to toggle Ending.
• If the node already has next phases, the Ending control is disabled until those edges are removed.
• Enable on terminal beats only (victory, defeat, epilogue, closed door).
• When the writer advances into an ending phase, player options are cleared and the reader sees Play Again.

Example

true

phase.guidance

Progression Logic

World Phases

When the story leaves this phase, and which next phase fits which evidence.

• Two or three short lines: ADVANCE (the observable event that ends this phase), BRANCH (what makes each next phase the right one), AVOID (what this phase must not do yet).
• Write conditions an observer could check in play ("after the player publicly sides with…"), never "when the story feels ready".
• Pacing, time scale and the situation a phase opens on belong in Phase Content: the writer picks the next phase from that text alone.
• Optional HOOKS: block lists promises planted in this phase, one per line: [CORE] H01 | payoff: <phaseId> | timing: slow-burn | one-line promise. Story Studio reads it; play never shows it to the writer, so a promise to keep alive also goes in Phase Content.
• Hook timing is one of immediate, near-term, mid-arc, slow-burn, endgame; the payoff id must be a later phase in the same branch.
• Do not repeat the phase premise or tone; keep those in Phase Content.

Example

ADVANCE: After they formally commit to a faction or obtain a credible route into the vault.
BRANCH: phase_vault_s2_0 if they side with the guild; phase_vault_s2_1 if they go in alone.
AVOID: Do not reveal what is inside the vault yet.

entityLabel.Character

Character

Entity types

A living being with a name and agency who can talk and act in the story.

• Use for heroes, NPCs, demons, prophets, or any creature that can speak and choose.
• Prefer Character over Creature when the being has personality and dialogue.
• Mark only true viewpoint leads as Main Character so cover art and play focus stay clear.

Example

Odile Varenne — a harbor clerk who forges travel papers for the families the tide guard turns away.

entityLabel.Region

Region

Entity types

A large territorial unit or meta-zone that contains many places.

• Use for empires, domains, continents, biomes, or broad territories.
• Prefer Region when the scale is larger than a single city, shrine, or room.
• Link Locations under a Region through relations when the hierarchy matters.

Example

Northern Glass Wastes — frozen empire of mirrored dunes.

entityLabel.Location

Location

Entity types

A specific place where scenes can happen.

• Use for shrines, cities, ruins, inns, strongholds, or other concrete sites.
• Keep Locations smaller and more playable than Regions.
• Give each place a clear narrative role: danger, refuge, secret, or travel hub.

Example

Ashen Shrine — ruined temple that drinks spoken names.

entityLabel.Race

Race

Entity types

A distinct species or lineage shared by many beings.

• Use for humans, elves, orcs, dragons, or any recognized species group.
• Put culture, lifespan, appearance markers, and shared abilities on the Race entity.
• Characters should reference Race instead of repeating species lore on every person.

Example

Eldergrove Sylphs — wind-born people who age by promises kept.

entityLabel.Creature

Creature

Entity types

A beast or semi-sapient entity without full character agency.

• Use for chimeras, wyrms, familiars, monsters, and non-speaking animals.
• If the being talks, plans, or acts like an NPC, prefer Character instead.
• Creatures still matter for threats, ecology, and world texture.

Example

Glassfang Wyrm — serpent that nests in broken mirrors.

entityLabel.Item

Item

Entity types

A distinct object of power or narrative weight.

• Use for relics, weapons, keys, cursed heirlooms, or plot-critical objects.
• Prefer Item when ownership, power, or quest progress depends on it.
• Use Object instead for ordinary props with little story weight.

Example

Crown of Ash — relic that burns one memory for each command given.

entityLabel.Object

Object

Entity types

A minor item or environmental piece without major power or plot focus.

• Use for furniture, tools, signs, or scenery props that still need a name.
• If the object is magical, cursed, or quest-critical, use Item instead.
• Keep Object entries light so the world stays scannable.

Example

Waystone Lantern — iron lamp that only lights near true north.

entityLabel.Faction

Faction

Entity types

A collective force or organization that acts as a group.

• Use for guilds, clans, cults, houses, nations, empires, and schools.
• Capture goals, power, and membership through the faction plus relations.
• Prefer Faction when many characters share allegiance or institutional pressure.

Example

Whisperwind Clan — spy house that trades secrets for safe passage.

entityLabel.Ability

Ability

Entity types

A specific power, skill, or technique a being can use.

• Use for named spells, martial arts, blessings, curses, or unique techniques.
• Keep abilities reusable: many characters can reference the same Ability entity.
• Describe cost, effect, and limits so simulation and writing stay consistent.

Example

Flamewalk — step through fire and reappear within line of sight.

entityLabel.Event

Event

Entity types

A defined moment in time with lasting consequences.

• Use for wars, summonings, betrayals, festivals, disasters, or turning points.
• Events should change world state, not just decorate history.
• Link participants, places, and fallout through relations and plot conditions.

Example

Night of Broken Crowns — three dynasties fell before dawn.

entityLabel.Myth

Myth

Entity types

A legendary tale or belief about the past.

• Use for creation stories, saint legends, or half-true cultural beliefs.
• Myths shape ideology even when they are incomplete or false.
• Prefer Fact when the content is treated as hard canonical history.

Example

Creation of the Moonmother — belief that tides are her unfinished tears.

entityLabel.Fact

Fact

Entity types

A world-known truth or canonical historical record.

• Use for established history, laws of nature, or widely accepted data.
• Keep Facts short and authoritative so agents can treat them as reliable.
• Use Myth when the story is believed but not proven.

Example

The Glass Sea freezes solid every seventh winter.

entityLabel.Lore

Lore

Entity types

Supporting world knowledge that does not fit a stricter entity type.

• Use for doctrines, customs, systems, or background notes that need a home.
• Prefer Race, Faction, Myth, or Fact when those labels are a better fit.
• Keep Lore concrete so it still helps retrieval and writing.

Example

Ash Tithe — custom of offering one memory at every city gate.