Skip to article
KAGRENAC Get started

Gameplay Design

An AI mod is worth playing when something in the game changes because of it, not just because a chat box answers. Before writing game code, your agent turns your idea into a short gameplay plan in PROJECT.md. It fills that plan from your conversation; you never fill in a research form.

Start With The Player

  • The fantasy. One sentence about what the player gets to feel, such as "my companion has my back".
  • The loop. What the player does, sees and hears in two or three minutes. If nothing visible or audible changes, it is not a loop yet.
  • The outcome. A subtitle, a voice line, a movement or a changed state the player can notice.

A simple mod where the player talks to one NPC needs only a few words for each.

Interaction Modes

ModeHow it starts
ManualThe player types to a character in game.
Ambient, one speakerSomething happens in the game, such as entering a place, and one nearby NPC remarks on it.
CompanionThe player talks to a companion, who also reacts to events and can carry out actions the game supports.
OperatorThe player asks an advisor for a report or gives an order. Obvious orders go straight to the game, with no AI call.

A mix is fine. Every mode keeps a real in-game chat box: the player sees who they are talking to, types freely and presses Enter. A hotkey that sends a canned line is not chat.

Triggers And Who Is There

  • Real triggers. Automatic lines start from something the game actually reports, not a timer that talks every few seconds.
  • Real observations. Characters are told only what the game can read now. Anything it cannot read is marked unavailable, never guessed. See Game awareness.
  • Participants and listeners. Note who is present and who could hear. Today one NPC answers at a time; conversations between NPCs are planned.

Who Decides

NeedUse
Fixed rules, emergencies, combatThe game's own AI or a simple rule
An obvious command, such as a button or fixed phraseThe game's handler directly
Words the player will read or hearThe dialogue model
Which nearby NPC answers the playerOptional NPC selection with JEV

Skip the AI when the outcome is already fixed, one option is always right, or nobody will see or hear the result.

The Player Comes First

  • Player input wins. When the player speaks, any automatic line in progress gives way. No new automatic line starts while the chat box is open.
  • Clean stops. An automatic exchange has a fixed number of lines, then ends. Generated lines never trigger more automatic lines.
  • No limits on the player. Lines the player asks for have no artificial quotas or cooldowns. Pacing applies only to automatic remarks.
  • Nothing lost. If a line fails, it goes back into the chat box to send again. Nothing is retried automatically.

Planned, Not Yet Available

Conversations between NPCs, with listeners and overheard knowledge, and broader JEV decisions, such as choosing an action, are planned. Today JEV only picks which offered NPC answers the player. If your idea needs one of these, your agent records it as a missing piece and builds what works now.

Full reference: docs/GAMEPLAY_DESIGN.md.

Next step: Plan the game integration.