CODELOCKBack

Guide

14Common problems

›Notifications do not arrive

Open Notifications → Delivery log: it shows where each notification went and why one was skipped (quiet hours, alarm muted, no access, channel disconnected). Check the event is on for the channel, and send a test.

›"No connection to the server"

The Rust server is restarting or unreachable — Codelock reconnects by itself. If it lasts long while the server is up, do "Pair with Server" in the game again.

›"Rust+ access has expired"

Open "Connect Rust+" and connect again — it takes a minute. Servers and devices stay.

›Discord does not accept direct messages

Allow direct messages from server members in Discord’s privacy settings, or add the Codelock bot to a server you are in.

›The server does not appear after "Pair with Server"

Check that Rust+ is connected (overview → Connection) and wait up to a minute. If it still does not appear, connect Rust+ again and pair once more in the game.

›A player is not found in the Tracker

The search covers your server’s players on BattleMetrics, by whole words — try the full name. Someone not yet seen on your server shows under "On other servers" and can be tracked ahead of time. BattleMetrics hides SteamIDs, so for a SteamID Codelock looks the player up by their current Steam name.

Still stuck? Write to us — the Support page has email and Telegram.