Patch day playbook

Patch days are predictable in one way only: something will break for someone. The goal isn’t to panic-load into a server—it’s to follow a short playbook so you know whether you’re cleared to play or should wait for a verified build.

Step 1: Read the status notice

Check the official status channel before launching. If the current game build is marked under review, treat that as a hard stop. Playing on an unverified combination wastes time and risks instability.

Step 2: Update the game first

Always patch Rust through Steam before updating your toolkit. Version order matters: game client first, then toolkit build matched to that client.

Step 3: Don’t stack changes

Patch day is the wrong time to also rework every overlay, swap sensitivity, and test a new raid profile. Change one layer at a time so you can isolate what caused a problem.

Step 4: Use a clean session test

Load into a low-pop area or a build server if available. Verify:

• Menu opens and closes cleanly
• Profile switching works
• One weapon profile behaves as expected
• Panic-disable bind still responds

Step 5: Know your rollback path

Keep the previous toolkit build installer or backup config accessible. If a new release has edge-case issues, rolling back to last known-good is faster than forum-diving mid-wipe.

When to wait

Wait if:

• Status shows pending verification
• You see widespread crash reports in the first hour
• Your custom overlay stack is unusually heavy

Waiting an hour on patch day often saves an entire evening of troubleshooting.