SHIP THE SDK. READ THE GRAVES.

Sign up to create your studio, add a game to mint a per-game SDK token (tmb_…), then initialize the SDK once. Managed exceptions and session heartbeats are captured automatically.

# 1. Sign up — creates your studio (you become owner)
# 2. On Games -> New game (name + engine), then open it
# 3. SDK tokens -> Mint token  (shown once - store as a build secret)

using AnkleBreaker.Tombstack;
 
Tombstack.Init("tmb_live_9f4c…a21e", "https://your-tombstack-host");
Tombstack.SetUser("user-123", steamId: "7656119…"); // when auth resolves
Tombstack.SetConsent(true);                          // GDPR / store-policy gate

Four primitives power everything in Tombstack:

Add the UPM package com.anklebreaker.tombstack in Unity 6 (6000.0)+ — download the .tgz from the download page and use Window ▸ Package Manager ▸ + ▸ Add package from tarball…:

https://d37yvxlv29ed7d.cloudfront.net/downloads/com.anklebreaker.tombstack-0.9.0.tgz

Prefer git? Add package from git URL… works for everyone — the package lives in a public repository: https://github.com/AnkleBreaker-Studio/tombstack-unity.git#v0.9.0. Zero-code init: create a Tombstack ▸ Config asset under a Resources/ folder named TombstackConfig — it auto-initializes on load.

After Tombstack.Init (or zero-code auto-init), the SDK is fully autonomous — no try/catch wiring, no log-shipping code:

Logs surface in the dashboard as Player log download links on the signature detail and bug detail pages, and GDPR erasure deletes them with the player's other artifacts. All three systems are config toggles (default ON) and consent-gated: with Require Consent, nothing is captured until Tombstack.SetConsent(true).

Managed C# exceptions and session heartbeats upload automatically; failed uploads persist and retry on next launch. Capture handled exceptions explicitly to keep context.

try {
    inventory.Equip(item);
} catch (Exception e) {
    Tombstack.Capture(e); // symbolicated + grouped by signature
}

Let players file bug reports from inside the game — optionally with a screenshot. They land in the dashboard alongside crashes.

Tombstack.ReportBug("Quest log empty after load", "ui");

All endpoints authenticate with a token sent as Authorization: Bearer … (or x-api-key). Two kinds exist:

The public read and triage APIs require a studio key (tmb_st_…) or a per-game token that was granted the read/write scope. A default ingest-only SDK token is rejected with 403; a missing or unknown token gets 401.

Every response uses the envelope { "success": true, "data": … } / { "success": false, "error": "…" }. Common error codes: 400 validation, 401 bad/revoked token, 404 not found, 429 rate limited (with Retry-After).

Rate limits (fixed 1-minute window): 120 requests/min per IP — the abuse guard for a crash-looping client — and a deliberately high 20,000 requests/min per game key backstop, so a real crash spike across your whole player base is never throttled.

A separate editor API (/api/editor/*) powers the Unity plugin's in-editor hub — it is plugin-internal, documented in the repo's docs/API.md.

Game clients are treated as hostile input: every field is validated, clamped and rate-limited. os ∈ {windows,macos,linux,other}, arch ∈ {x64,arm64,x86,other}, timestamps within the 90-day window.

High-frequency telemetry batches via { sentAtIso, items: [...] } (1–200 items, ≤512 KB). Each item is validated independently — a bad item is dropped and the rest stored — and carries its own occurredAtIso; the envelope's sentAtIso only computes clock skew. A batch is charged its item count against the rate window, so batching can't amplify ingest past the per-IP/per-key limit.

curl -X POST https://your-tombstack-host/api/v1/ingest/metrics:batch \
  -H "Authorization: Bearer tmb_live_9f4c…a21e" \
  -H "Content-Type: application/json" \
  -d '{
    "sentAtIso": "2026-06-11T12:00:05Z",
    "items": [
      { "name": "fps", "value": 59.8, "unit": "fps",
        "occurredAtIso": "2026-06-11T12:00:00Z",
        "buildVersion": "2.4.1", "os": "windows", "arch": "x64",
        "role": "client", "matchId": "m-1", "sessionId": "sess-9" },
      { "name": "rtt_ms", "value": 42, "unit": "ms",
        "occurredAtIso": "2026-06-11T12:00:01Z",
        "buildVersion": "2.4.1", "os": "windows", "arch": "x64",
        "role": "client", "matchId": "m-1" }
    ]
  }'

Binary artifacts upload out-of-band via presigned S3 PUTs (15-min TTL) requested with boolean flags: crashes accept "minidump": true (response carries data.minidumpUpload) and bug reports accept "screenshot": true (data.screenshotUpload). Both accept "log": true to request a player-log slot (data.logUpload, text/plain). Read APIs return a short-lived logUrl wherever a log exists.

curl -X POST https://your-tombstack-host/api/v1/ingest/crashes \
  -H "Authorization: Bearer tmb_live_9f4c…a21e" \
  -H "Content-Type: application/json" \
  -d '{
    "occurredAtIso": "2026-06-08T11:40:00Z",
    "buildVersion": "2.4.1",
    "os": "windows",
    "arch": "x64",
    "signature": "SIGSEGV@InventoryService.Equip",
    "stackHint": "NullReference in InventoryService.Equip"
  }'

{
  "success": true,
  "data": { "crashId": "01J…", "minidumpUpload": null, "logUpload": null }
}

Pull aggregated and recent data back out — for dashboards, automations or your own tooling.

Fleet & log-pull writes (write scope, except fulfill which is ingest): enrich a server's metadata, raise a player-log pull, and let a targeted client honour it (uploading only its own log). The server registry row is created lazily by role=server telemetry, so POST /servers only enriches an existing server (unknown serverId → 404).

Triage writes back over the same token auth — set { "status": "open" | "resolved" | "ignored" } on a signature or a single bug report:

{
  "success": true,
  "data": {
    "totalCrashes24h": 312,
    "crashSpike": false,
    "topSignatures": [
      { "signature": "SIGSEGV@InventoryService.Equip", "count": 188, "affectedUsers": 142 }
    ]
  }
}

Upload debug symbols (PDB / dSYM / .sym) per build from CI so native crashes can be symbolicated — the tombstack-symbols CLI wraps these calls. Registration is idempotent on (game, build, debugId, module) and returns a presigned S3 PUT for the file itself.

curl -X POST https://your-tombstack-host/api/v1/symbols \
  -H "Authorization: Bearer tmb_live_9f4c…a21e" \
  -H "Content-Type: application/json" \
  -d '{
    "buildVersion": "2.4.1",
    "moduleName": "Game.dll",
    "debugId": "3C8DA0F8-…-1",
    "os": "windows",
    "size": 18874368
  }'

Point Claude or Cursor at the Tombstack MCP server (@anklebreaker/tombstack-mcp) to triage crashes with an AI — it wraps the read API as MCP tools.

{
  "mcpServers": {
    "tombstack": {
      "command": "npx",
      "args": ["-y", "@anklebreaker/tombstack-mcp"],
      "env": {
        "TOMBSTACK_BASE_URL": "https://your-tombstack-host",
        "TOMBSTACK_TOKEN": "tmb_live_9f4c…a21e"
      }
    }
  }
}

Everything you install ships from public repositories or straight from this site:

Unity SDK — AnkleBreaker-Studio/tombstack-unity (public). Install via UPM git URL https://github.com/AnkleBreaker-Studio/tombstack-unity.git#v0.9.0 or grab the tarball from the download page.

Native C/C++ SDK — AnkleBreaker-Studio/tombstack-native (public, v0.1.0, in development). C99 DLL ABI for any engine, with offline crash sidecars the CLI uploader drains; minidump capture is coming (Phase 2).

CLI — tombstack-doctor, tombstack-upload and tombstack-symbols, zero-dependency Node 18+ — download the zip.