Content Registry

The content registry is a feature for managing static metadata of in-game maps, items, skills, and more, and linking them to telemetry data.

Why It’s Needed

With generic telemetry tools, there is no way to know what the IDs in event data refer to. By using the content registry:

• item_id: "sword_01" → “Flame Sword (Rare / Weapons category)”
• map_id: "map_desert" → “Desert Arena (PvP map)”

It adds game context to your telemetry, enabling meaningful analysis.

Content Types

Type	Description	Examples
map	Game maps	Stages, arenas, worlds
item	In-game items	Weapons, consumables, equipment
skill	Skills/abilities	Attacks, buffs, passives
character	Characters	Playable characters, NPCs
custom	Custom definitions	Any game element

Data Synchronization

Content registry data is synchronized with your game’s master data.

Manual Registration

Register individually from the dashboard or via the REST API (POST /v1/content).

Bulk Import (Recommended)

Import master data as JSON from your CI pipeline using the CLI:

framedash content import ./game-content.json

Format of game-content.json:

[
  {
    "type": "item",
    "external_id": "item_hp_01",
    "name": "Health Potion",
    "metadata": { "rarity": "common", "category": "consumable" }
  }
]

Integration with Telemetry

When sending events with the SDK, include the external_id and the content name and metadata will be automatically displayed in the dashboard.

Next Steps

• API Reference — Content Registry API
• CLI Reference — Data sync commands