Useful Information
Essential player guides, troubleshooting tips, and in-game commands for the NOX cluster.
Quick Reference Guides · Updated September 2026
In-Game Commands & Tokens
Use these commands directly in your game chat or console bar to manage stats, tokens, and quality-of-life toggles.
/dn on
/dn off
/forges on|off
/limits
/farm
/dctokens
/tokens
/unlockengrams
/rarelist on Noxus
/rename name
/DinoWake
/dinomindwipe
Discord Tribe Log Webhook Setup (/tlr)
Streamline your tribe operations by feeding your in-game tribe logs straight into a dedicated Discord channel using the /tlr command.
Create Discord Webhook
Go to your Discord Server → Click top-left arrow down → Server Settings → Integrations → Webhooks → New Webhook → Click the new webhook and Copy Webhook URL.
Link In-Game
Hop into ARK and type the command followed by your copied Discord webhook URL:
/tlr https://discord.com/api/webhooks/...
Rebuild Kits & PVE / PVP Switching
Manage your protection phase and claim your rebuild stash efficiently after a wipe.
Claiming Your Rebuild Kit
Suicide or reconnect once to the server. Once done, your rebuild kit will appear directly inside your shop stash.
Type in chat to check how much PVE protection time you have left:
/pvemode
To drop PVE protection and enter PVP mode early:
/pvpmode confirm
Note: Once out of PVE, there is no reverting until your next wipe!
How to Get Your Coordinates (CCC)
When filing support tickets regarding map glitches, stuck characters, or admin assistance, staff will require your exact in-game coordinates.
Open Console
Press Tab on your keyboard while in-game to bring up the admin console bar.
Type Command
Type ccc into the input bar and press Enter.
Paste in Ticket
Your coordinates are automatically copied to your clipboard. Simply paste them into Discord.
How to Find Your SteamID64
Admins require your unique 17-digit SteamID64 when processing shop purchases, tribe ownership transfers, or ban appeals.
steamcommunity.com/profiles/76561198...).Fixing "Mod Mismatch" Errors
Encountering a connection refusal or version mismatch? Your local workshop files are out of sync with the cluster.
