Skip to main content
Eposyne Launch Architect

The runtime layer · Beta

An AI Game Master. Inside your game.

Director reads game state, makes narrative decisions, and returns validated parameter updates. Within your rules. Every time. Built to run on-device through its native SDK, which is not yet available; today, developers use the hosted Director beta.

Eposyne Director dialogue view: an NPC tavern keeper with state, response options, and known profile

What is Director?

Eposyne Director is a runtime AI Game Master that reads your game state and makes constraint-validated narrative decisions in real time. It drives NPC behavior and dialogue within the limits your game declares; plot progression through story arcs is in development. Director is built to run on-device through its native SDK, which is not yet available. Today, developers use the hosted Director beta for building and testing, and its model calls are paid from usage credits. Eposyne plugins exist for Unity and Unreal, and any other engine can call the HTTP API. It is in beta: the core runtime is what you can build against today, with no licence fee until launch. After launch, it takes 1% of gross revenue above the first 100,000 EUR.

Hosted beta

On-device SDK not yet available

Validated

Checked against your rules

No licence fee

Until launch; beta calls from usage credits

Any engine

Unity, Unreal plugins; HTTP API

01The problem

Most game worlds don't actually react.

Players expect worlds that feel alive. Most games still rely on systems that look complex but feel predictable.

Static Dialogue Trees

01

Pre-authored branches players exhaust quickly. Same lines, every playthrough.

Scripted Outcomes

02

Quests that play out the same way regardless of what the player actually does.

NPCs That Forget

03

Characters with no memory. Save their life, they still greet you like a stranger.

02How it works

State in. Validated story out.

Six things Director is built to do at runtime

Learn more →

01Constraints

You Define the Rules. Director Follows Them.

Define your game state as parameters with allowed values, ranges, and mutability. Director operates within those boundaries. If the model proposes a change that breaks a rule, Director drops it.

Constraint validation flow params proposes valid invalid → dropped PARAMETERSGame State RUNTIMEDirector CONSTRAINTSValidate OUTPUTTo Player
  1. 01Mutable and immutable parameters
  2. 02Allowed values and range enforcement
  3. 03Every output validated before it reaches the player

02Decisions

Send Game State. Get Decisions Back.

Your engine sends a snapshot of the current scene. Director returns validated updates. JSON or XML in, same format back. One API call.

Decision round-trip state decide updates each decision SNAPSHOTEngine RUNTIMEDirector VALIDATEDUpdates APPLYEngine
  1. 01Simple REST API integration
  2. 02JSON and XML round-trip support
  3. 03Choose from the hosted beta's models; local models come with the native SDK

03Memory

NPCs That Carry What You Did

In the beta, your game passes what the player did as part of the state it sends, so Director can read it in later scenes. Help someone, betray someone, ignore someone, and the next conversation starts from there. A dedicated NPC memory module is in development.

NPC memory loop writes reads shifts carries over PLAYER ACTIONInteraction STATEGame State AGENTNPC ADAPTSBehavior
  1. 01Past interactions and choices, passed in as state
  2. 02Build relationships over time
  3. 03Change behavior based on history

04Emergence · In development

Stories That Arise From Play

The direction Director is built toward: narrative arcs from gameplay, not scripts. Player actions shape what happens next and consequences propagate through the world. The beta covers the reactive part today; a story-arc module for proactive arcs is in development.

Emergent narrative loop acts triggers leads to propagates INPUTPlayer Action STATEWorld State EMERGESEvent RESULTConsequence
  1. 01Events arise naturally from player choices
  2. 02Actions carry forward through the state your game sends
  3. 03Systems create story, not just content

05Dialogue

Conversations That Respond to Context

Director can write a line of dialogue for any value your game marks as text, from the context your game sends: what has happened, who is speaking, and what is at stake. Within the limits you declare. No hardcoded branches.

Context-aware dialogue context generates PASTHistory WHOSpeaker TENSIONStakes RUNTIMEDirector OUTPUTDialogue
  1. 01Context-aware responses every time
  2. 02Text values stay within the limits you declare
  3. 03No dialogue trees to maintain

06Generation · In development

New Entities Born From Play

In development: Director creating new characters, factions, quests, and rivals at runtime, each one shaped by the current state of your world. Not random. Contextual. This is not available in the beta.

Runtime entity generation world spawns STATEWorld State RUNTIMEDirector ENTITYNPC GROUPFaction GOALQuest
  1. 01Generate NPCs, factions, and quests at runtime
  2. 02New entities grounded in existing world state
  3. 03Power structures and intrigue that write themselves

03Control

Control, not chaos.

Director is designed for real production environments. You stay in control. Director handles execution.

Constraint Validation

01

Mutable and immutable parameters. Allowed values. Range enforcement. If the model proposes a change that breaks your rules, Director drops it.

Scoped Authority

02

You define what Director can change and what it cannot. Personality stays locked. Mood can shift. You set every boundary.

Engine Has the Final Say

03

Director proposes; your engine decides. The engine applies only values you declared, marked as changeable, and within range.

Works with your engine

It runs alongside your systems.

Unreal EngineEposyne for Unreal plugin
UnityEposyne for Unity plugin
Other engines through the HTTP API

04In the field

Built for these genres.

Director is being built and tested against wildly different game types. Same engine. Different worlds.

The Rusty Tankard fantasy RPG tavern powered by Director

Fantasy RPG

01

Tavern NPCs with moods, trust levels, and dialogue that shifts based on player actions. Insult the bartender and she remembers.

Heartbeat High social sim powered by Director

Social Sim

02

Character relationships, affection systems, and social dynamics that evolve every interaction. Friendships form and break naturally.

Faereld survival game powered by Director

Survival

03

Dynamic quests, district-level world state, and NPCs who react to your reputation. Every choice shapes what opportunities appear next.

05The pipeline

From creation to execution.

Architect and Director are built to work together. One authors the narrative, one runs it.

Architect

01

Builds your narrative systems: quests, dialogue, structure. The authoring layer.

Learn about Architect →

Director

02

Runs them in real time: behavior, adaptation, emergence. The runtime layer.

You are here

Director is not AI NPCs. It is a narrative runtime. It interprets player behavior and drives the story forward. Every session. Every choice. Every consequence.

Pricing

No licence fee until you launch.

Director

No licence fee while you build

  • Runtime narrative engine (beta)
  • NPC behavior within your rules
  • Context-aware generation
  • All core features included

During the beta

The hosted beta's model calls are paid from usage credits. Every new account starts with a welcome credit to try it.

After launch

After launch, 1% of gross revenue above the first €100,000 per title

Enterprise

Enterprise licensing, a one-time buyout of the revenue share, SLA, and integration work by contact

Build a World That Actually Responds

See how Director transforms static game worlds into living narrative systems.

06Questions

Director FAQ

What is Eposyne Director?

Director is a runtime AI Game Master, currently in beta, that reads your game state and makes constraint-validated narrative decisions in real time. It drives NPC behavior and dialogue within the limits your game declares. Plot progression through story arcs is in development.

How does Director differ from a regular scripting system?

Traditional scripting is hand-authored. Every branch must be written and tested in advance. Director takes your world's rules, state, and goals, and generates narrative decisions at runtime that still respect every constraint you define. It handles the branches you didn't write.

Does Director require a cloud connection?

Today, yes. Developers use the hosted Director beta, which is reached over the network for every decision; it is for building and testing, and a shipped game cannot use it yet. Director is built to run on-device through its native SDK, which is not yet available. The native SDK is what brings no cloud dependency, no network calls, and no player data leaving the game. Today each hosted call is paid from usage credits; on-device inference through the native SDK runs on the player's hardware.

How does Director's pricing work?

Director has no licence fee while you build. The hosted beta's model calls are paid from usage credits, and every new account starts with a welcome credit to try it. After your game launches commercially, Director takes 1% of gross revenue above the first 100,000 EUR per title, so small releases pay no licence fee. Enterprise licensing, a one-time buyout of the revenue share, SLA, and integration work are available on request. See pricing for the details.

Which game engines does Director support?

Director has plugins for Unity and Unreal Engine: Eposyne for Unity and Eposyne for Unreal. Any other engine can call Director's HTTP API directly. It works as middleware that reads game state and returns validated narrative parameter updates.

Can Director hallucinate or break my game's lore?

Not outside the limits you set. In your engine, you declare which values Director may change and within which allowed values or ranges. Any proposed change outside those limits is dropped before it reaches your game, and your engine applies only declared, changeable, in-range values. You define the boundaries; Director operates inside them.

Do I need Architect to use Director?

No. Director does not read Architect worlds today; it works with the state your game sends and the limits your game declares. Architect content reaches your game through the Eposyne plugin's import.