Your Rust Stream. Now Controlled by Your Audience.

What you configure

• RustMaxx account + Profile — Link your streamer subscription, set your Steam64 so in-game actions and patrol anchors resolve to the right player.
• Admin → Streamer interactions — Copy your per-server webhook URLs, map TikFinity connections (event names → server actions), and grab spawn templates (for example Roaming NPC / npcmaxx).
• Server dashboard — Allow TikFinity for that server, tune Streamer interactions allowed actions, and optionally set a TikFinity patrol anchor (Steam id) so spawns leash to you when the webhook does not pass anchorSteam.
• TikFinity (tikfinity.zerody.one) — Create Actions with Trigger WebHook pointing at the full URL RustMaxx shows you (must be public HTTPS, not localhost). Use Connections so gift names or custom event names match the rules you defined in RustMaxx.

TikFinity URL placeholders (viewer identity)

In the webhook URL or JSON body, TikFinity can substitute the triggering viewer's TikTok fields — for example so MaxxInvaders shows the correct nickname on a bot:

• %nickname% — display name (common for NPC labels)
• %username% — @handle
• %userId% — numeric id (use for crew / unique viewer tracking when the payload must include userId or uniqueId)

If a name shows up literally as %nickname%, TikFinity did not expand the variable — prefer POST JSON with viewerName set from TikFinity's variable picker, or fix the action's query string substitution.

Production URL must match

The host in TikFinity must match your live site exactly (including www vs apex). RustMaxx uses your configured public base URL for webhook links; mismatched origins break OAuth-style flows and webhooks alike.