NPC Builder’s Events & Items system is a cornerstone of in-game interactions. These entities allow you to script dynamic NPC behaviors and customize gameplay responses. Events serve as triggers to drive actions, while items represent objects or tokens used in these actions. Whether reused across your game or set uniquely for specific characters, both events and items are essential to building an immersive narrative and interactive environment.
Create & Configure: Quick workflow
1
Decide scope: Global vs Character
Choose whether the event/item should be reused across many characters (Global) or tailored to a single NPC (Character-level).
Global → reuse, version centrally, link from repo.
Character → bespoke behavior, local overrides.
Character → bespoke behavior, local overrides.
2
Global creation (recommended for reuse)
Open Settings → Collections → Events or Items → New.
Fill Name/UID, Description, Type, and Save to collection.
Use descriptive UIDs to make linking easier (e.g. 
quest-token-gold).3
Character-level creation
Open a Character → Properties → Events & Items panel → Click “New Event” or “New Item”.
Fill required fields for the character-specific behavior. Use this when the event/item is unique to that NPC.
4
Link global elements to a character
In the character’s Events & Items panel choose “Link from Repo”, then select the global event or item.
Linked items remain managed in Settings; edits there propagate to characters that reference them.
What is an Event? (entity & purpose)
An Event is an entity that represents a triggerable interaction or behavior in the game world. Use events to encode what should happen and when—either as standalone behaviors or as item-driven actions.
1
When to use Events
Use events to:
- Trigger NPC behaviors (dialogue, follow, flee, give item).
- React to player actions (pick up, talk, trade).
- Drive quest steps and gameflow.
2
Benefits of modelling Events explicitly
- Reusability: define once and link across characters.
- Clarity: central place to document intent and outcomes.
- Composition: combine events with items and quests to build complex interactions.
Event Types
1
Action Event
Action Events are item‑agnostic behaviors (e.g., “NPC follows player”, “NPC starts conversation”, “NPC flees”). They describe a direct behavioral change and usually contain the action name, triggering conditions, and optional parameters (duration, range).
2
Item Event
Item Events are associated with a specific item (e.g., “Give token to player”, “Consume key to open door”). They define the relationship between an action and an item, including how the item is granted, removed, or checked.
Event Definition (fields to fill)
1
Name / UID
Unique identifier used for linking and API calls. Use short, descriptive slugs (e.g.
give-quest-token).2
Description
Human-friendly explanation: purpose, when it runs, and expected outcome.
3
Type & Parameters
Select Action or Item. Provide any parameters (conditions, item UID, quantity, timing).
For events that alter game state (give/remove items, complete quests), prefer global definitions to ensure consistent behavior across NPCs.
What is an Item? (entity & purpose)
An Item is a definable object used in gameplay and events: currency, quest tokens, keys, tools, or any tangible entity the game tracks. Items can be used for trade, progression, or story beats.
1
When to create Items
- Use Trade items for shops, barter, or economy systems.\
- Use Action items for quest tools, keys, or story-specific objects.
2
Why model Items explicitly
- Trackable state: inventory, ownership, counts.
- Interoperability: referenced by events, quests, and UI.
- Clear semantics: description and type ensure consistent usage.
Item Types
1
Trade
Items intended for buying/selling or barter (e.g., “gold coin”, “merchant voucher”). Include value, unit, and any trade rules.
2
Action
Items with a gameplay role (e.g., “skeleton key”, “ancient map”, “quest token”). Typically consumed or checked by Item Events.
Item Definition (fields to fill)
1
Name / UID
Unique identifier used by events and inventory systems.
2
Description
Explain role, appearance, and any rules (can be stacked, consumable, tradable).
3
Type & Metadata
Choose Trade or Action; add metadata such as unit, value, or tags used by game systems.
Keep item UIDs stable and descriptive. If you expect many variants, use tags or metadata instead of creating many near-duplicate items.
For request schemas, example payloads, and enum lists, open the OpenAPI explorer.