Support

How to get help, report issues, and engage the MusterBox team.

Before you file

Take two minutes and capture the data that makes your report actionable:

musterbox sdk version                # SDK/protocol/ABI
musterbox diagnostics generate       # support bundle (redacted)
musterbox pipeline status            # outbound queue health
musterbox transport diagnose         # connectivity

Also note:

• environment (sandbox/staging/production) and hosted URL,
• your engine and version (e.g. Unity 2022.3, Godot 4.3, Bevy 0.19),
• the SDK error code (MBX-SDK-###) or platform code from the response,
• timestamps and any affected player IDs (hashed).

Channels

Need	Where
SDK usage questions	Start with the docs; then the developer channel
Bugs / crashes	Report with steps + diagnostic bundle
Security incidents	Follow Report a security incident
Documentation issues	Suggest a correction on the affected page

What makes a good report

1. Reproduce: exact steps, config (redacted), and code path.
2. Observe: expected vs. actual behavior, and the error codes you saw.
3. Diagnose: health check + bundle output.
4. Classify: is it SDK, adapter, or backend? The error codes separate transport (MBX-SDK-004), auth (MBX-SDK-005), protocol (MBX-SDK-009), etc.

Boundaries

Some things are deliberately not part of the SDK:

• the game’s own rules, authoritative server, or realtime layer — those live in the game project,
• OTP-style login with requiresOTP — surfaced as an error until supported,
• non-session credential scopes — grant session for match integrations.

Status of distribution

npm (@musterbox/sdk-js, @musterbox/sdk-wasm) and crates.io publication are not live yet; installs use vendored dist/ artifacts. If you are blocked on publication cadence, say so in your support request so it can be prioritized.