Vibe Console

Purpose: Make sure Chronos is connected and scoped correctly.

• • Base URL
• • API Key
• • World ID
• • NPC ID

This section is required for every developer. Chronos must always know which backend and which world namespace it operates on.

Purpose: Define how your world behaves using design intent — not hardcoded logic.

Rules are stored on the server and read by the NPC Brain whenever Brain Think runs.

IF player_helped_villager THEN mood=friendly
IF player_lied_to_guard THEN mood=hostile
IF player_apologized THEN mood=neutral

{
  "on_event": {
    "player_helped_villager": { "mood": "friendly" },
    "player_lied_to_guard":   { "mood": "hostile" }
  }
}

Guards remember crimes.
If a player lies, they become suspicious.
Helping villagers improves reputation.

You only need to set rules once per world. After that, your game can send events normally — no code changes required.

💡 Recommended: Manage rules here in Vibe Console instead of setting them in game code. This allows designers to adjust behavior without rebuilding the game.

Why you see example events like player_stole_item:

This does not mean games steal apples. This exists to provide one simple, repeatable demo event.

In real games, events may look like:

• • player_killed_npc
• • quest_completed
• • door_opened
• • faction_betrayal

All events share the same structure. The example button simply means: Append Any World Event.

Purpose: Force the NPC Brain to evaluate memory, rules, and events.

This is a developer-only debugging mechanism.

In production games, Brain Think is typically triggered automatically:

• • On event thresholds
• • On time ticks
• • On player proximity

Purpose: Display Chronos’ derived NPC state.

This proves memory persistence, state evolution, and cross-session behavior.

This is the core "magic moment" of Chronos Engine.

Purpose: Inspect append-only world history.

• • Debug ordering
• • Verify event persistence
• • Understand Brain inputs

This is optional but extremely useful during development.