Game Changelogs

The Changelog manager lets you document updates for players across three branches: Alpha (testing), Beta (staging), and Live (production). Publish changelogs without game updates.

Branch System

Branch	Audience	Purpose
Alpha	Internal testing	Early features for QA
Beta	Beta testers	Staged rollout, feedback
Live	All players	Official public updates

Creating a Changelog Entry

1. Go to Live Ops > Changelogs
2. Select a branch (Alpha, Beta, or Live)
3. Click New Entry and fill in:
   • Title: Release name (e.g., “v1.2.0”)
   • Content: Changelog text
   • Categories: Select from Added, Changed, Fixed, Removed, Known Issues
4. Leave as Draft (not published yet)
5. Review, then click Publish

Categories

Added:    New features, mechanics, items
Changed:  Adjustments, nerfs, buffs
Fixed:    Bug fixes, crash fixes
Removed:  Removed content, deprecated features
Known:    Known issues, planned fixes

Draft Workflow

1. Write your changelog in Draft status
2. Preview in the Dashboard
3. Publish when ready

Once published, the changelog is immediately visible to players via the SDK.

SDK Integration

Players can fetch the latest changelog:

var changelog = await QuestData.get_changelog("live", 1)
# Returns the latest 1 entry from the live branch
print(changelog[0]["title"])      # "v1.2.0"
print(changelog[0]["content"])    # Full changelog text
print(changelog[0]["published_at"]) # "2026-04-01T12:00:00Z"

API Reference

# Get latest changelog entry for a branch
curl "https://api.questdata.io/v1/changelog?branch=live&limit=1" \
  -H "x-game-api-key: YOUR_API_KEY"

# Get last 5 updates
curl "https://api.questdata.io/v1/changelog?branch=live&limit=5" \
  -H "x-game-api-key: YOUR_API_KEY"

Response:

{
  "branch": "live",
  "entries": [
    {
      "id": "v1.2.0",
      "title": "v1.2.0 - Monster Hunt Update",
      "content": "New dungeon, new boss, bug fixes",
      "categories": ["added", "fixed"],
      "published_at": "2026-04-01T12:00:00Z",
      "author": "dev@questdata.io"
    }
  ]
}

Tips

• Publish 1-2 hours before rollout to let CDN cache
• Use Beta branch for staged testing first
• Keep each entry under 300 characters for mobile