Support Operations
Triage for account access, builder readiness, export handoff, community publishing, and Discord support tickets. Identify the problem type, capture the right evidence, then move to the next useful route.
Triage board
Start with the lane that matches the user-visible symptom. Each lane names what it covers, what to check first, what evidence to capture, and the next route that usually resolves the issue fastest.
Access state, profile display, account menu behavior, notifications, and public actions that require authentication.
Check first
Evidence to capture
Pack contract blockers such as missing anchors, unresolved references, missing type settings, empty layouts, or loot metadata gaps.
Check first
Evidence to capture
Local ZIP output, folder names, manifest ids, JSON file shape, and the boundary between web export and Rust server install.
Check first
manifest.json id exactly.Evidence to capture
manifest.json id and folder namePublished prefab snapshots, stored thumbnails, creator tags, reports, imports, and update-to-latest behavior.
Check first
Evidence to capture
Readiness evidence desk
Good evidence keeps support focused on the app state instead of guessing. This is guidance only: no upload form, ticket table, or backend submission exists on this static page.
Raid, Cave, Lobby, Environment, Loot, or community prefab group.
Copy the first blocking message before changing the scene.
Capture both values when export or install shape is involved.
Include the exact connector, portal, vendor, spawn, or referenced anchor id.
Show the ZIP folder tree and the generated JSON file names.
Note whether this is a source group, public listing, private import, or update prompt.
Capture the page, modal, thumbnail, or preview state that made the issue visible.
Issue router
These cards do not duplicate the field manual. They route common symptoms to documentation, tutorials, Community, or a support anchor where the problem can be described more precisely.
A Lobby, Environment, or Raid pack is missing the formal Pack.Connector.* route anchor.
Documentation: anchors
cave.json.portalAnchorId needs to resolve to a Cave portal_anchor, not the route connector chain.
Documentation: troubleshooting
The pack still has a contract blocker, unresolved reference, or type-specific missing setting.
Documentation: readiness
Raid loot markers come from tagged supported storage containers, not old standalone marker assumptions.
Documentation: pack types
Community browsing uses stored thumbnails; save or publish flows are the supported refresh path.
Support: community lane
Imported prefabs are private snapshots. Use the update-import path when a newer public snapshot exists.
Documentation: community
Check the topbar state and the route that asked for authentication before assuming the action failed.
Support: account lane
Public browsing can be open while save, import, publish, report, or account-owned actions require auth.
Open Community
Practical FAQ
This FAQ avoids support policies, emails, staff response times, and direct deployment claims. It stays on the browser app behavior visible today and routes ticket intake to Discord.
Use documentation for exact pack contracts, tutorials for mission-style workflow guidance, Community for public prefab discovery, and this support page when you need to classify a problem and capture evidence before the next route.
The readiness message is the fastest signal because it names the contract that failed. Capture the first blocker, pack type, and any referenced anchor or file name before asking for help.
No direct server deployment is part of this static support route. The supported web flow is to export the pack ZIP and handle server installation through your normal server process.
Imports are snapshots in your private User catalog. When a creator publishes a newer public snapshot, use the update-import flow instead of expecting the imported copy to live-update.
No files are submitted through this page. Use the Discord support link to open a live support ticket, then include the evidence checklist items that match your issue.
Discord is the support intake route. Join the RaidCreator Discord, open a support ticket there, and include the pack type, readiness message, export shape, or community state that applies.
Discord support desk
Discord is the live support route for RaidCreator. Use this page to classify the issue and gather evidence, then join Discord to open a ticket with the right context.
Use Discord when the issue needs live support intake instead of another documentation pass.
Pack type, readiness message, folder shape, anchor name, screenshot, or community import state.
Documentation and tutorials still handle field-manual answers; Discord handles ticket conversation.
Next route
Documentation explains the contract, tutorials explain the workflow, Community handles public prefab discovery, and Discord carries live support ticket intake when the issue needs a conversation.