nikolaj-lat Factions
Edit tabs/factions.json.
The factions authored here are the world's complete roster: the engine uses them as fixed context during play and reveals them as the story names them.
Required Fields
| Field | Requirement |
|---|---|
name |
Must match object key exactly |
basicInfo |
Three-sentence structure (see format below) |
factionType |
"major" if the faction should span into newly generated regions, "minor" if not |
hiddenInfo |
Full paragraph of secrets (see guidelines below) |
Conditional Fields
| Field | When to Include |
|---|---|
known |
Set to false to hide at game start. Omit otherwise |
Never Include
Omit these fields (auto-set at runtime):
detailType,embeddingId,embedding
basicInfo Format
Three sentences covering scope, purpose, and public perception:
- One sentence about what the faction is and its scope
- One sentence about their goals or activities
- One sentence about how outsiders perceive them
Format: "[Name] is [scope description]. They [primary activity or goal]. [Public reputation or perception]."
hiddenInfo Guidelines
Write a full paragraph revealing what is not publicly known. Mix different types of secrets:
- True origins or founding history
- Internal conflicts or power struggles
- Secret alliances or enmities with other factions
- Hidden resources, locations, or capabilities
- Long-term plans or hidden agendas
- Dark secrets or moral compromises
Both narrative depth AND gameplay-useful information should be included.
Discovery Mechanics
Factions default to known: true at runtime unless the config explicitly sets known: false. Use known: false for secret organizations, hidden cults, or factions the player must discover through gameplay.
A hidden faction becomes known when the latest story text contains its full name as a whole word (case and spacing insensitive), or when a known-entity trigger effect sets known. Give hidden factions distinctive names that can plausibly appear verbatim in narration.
Schema
interface Faction {
name: string
basicInfo: string
factionType: 'minor' | 'major'
hiddenInfo: string
known?: boolean
}
Faction + World Lore Sync
When creating a faction, you must also create a corresponding World Lore entry. The faction key and world lore key must match exactly. The faction basicInfo and world lore text must be identical (same text, two retrieval pathways: semantic search for lore, exact key match for faction).
Reference
For detailed documentation, see factions-reference.md.