All Activity

Rust client logs can help staff review crashes, connection errors, loading issues, and other client-side problems. The main file to look for is: output_log.txt Open Steam. Go to your Library. Right-click Rust. Select Manage, then Browse local files. Look for output_log.txt in the Rust folder. You can usually find it here: Steam\steamapps\common\Rust\output_log.txt If staff asks for your client log, attach the output_log.txt file to your help ticket. Please do not copy and paste the entire log into the ticket unless staff asks you to. If you do not see the file, start Rust, try to reproduce the issue, then close Rust and check the folder again.

If Rust crashes while joining a server, it is usually caused by a bad cached map file or another client-side loading issue. Start by closing Rust completely and clearing your Rust map cache. Close Rust completely. Open your Rust install folder through Steam. Go to the maps folder. Delete the files inside the maps folder. Restart Rust and try joining the server again. You can usually find the folder here: Steam\steamapps\common\Rust\maps After clearing the folder, Rust will download a fresh copy of the map the next time you connect. If you are receiving a specific error instead of a normal crash, these articles may help: How do I fix the Invalid Packet: Client Ready error? How do I fix the World File Mismatch error? If Rust continues crashing after clearing your map folder, verify your Rust game files through Steam and try again. If the issue still continues, please create a help ticket and include the server you are trying to join, what happens when Rust crashes, and your Rust client log file. You can find instructions here: How do I find my Rust client log file?

if you have a stack of shovels and one breaks instead of it separating into a broken one it gives you a brand new one in your inventory

It's come to my attention that the auto claiming has not worked in a while, tested today to confirm. Will need to manually claim them prior to the time running out for them to be stored in the stash. Believe it's the case on all modded servers running it.

The Server Update Required error means Rust has received an update that the server has not finished applying yet. This usually happens when Facepunch releases a mandatory server update. These updates are required before players can connect again. RustEZ servers are updated promptly, so this error is usually temporary. In most cases, you only need to wait for the server update to finish, then try connecting again. Close Rust completely. Restart Steam and make sure Rust is fully updated. Wait a few minutes for the server update to complete. Try connecting again. If the error continues for an extended period, check RustEZ announcements or create a help ticket so staff can confirm the server status.

If you are unable to connect to a RustEZ server, the issue may be caused by Rust, Steam, your network, or cached connection data. Try the steps below before creating a help ticket. Close Rust completely and reopen it. Restart Steam. Restart your PC. Restart your modem and router. Make sure Rust is fully updated in Steam. Verify your Rust game files through Steam. Try connecting directly using the server IP. Server IPs can be found at rustez.com/connect. Temporarily disable any VPN, proxy, or custom DNS service and try again. Make sure Rust is allowed through your firewall and antivirus software. Flush your DNS cache. Restart your PC again after making network changes. If the issue continues, uninstall and reinstall Rust. To flush your DNS cache on Windows: Open the Start menu. Search for Command Prompt. Right-click it and choose Run as administrator. Run the following command: ipconfig /flushdns After flushing DNS, restart Steam and try connecting again. If you still cannot connect after trying these steps, please create a help ticket and include the server you are trying to join, any error message you are seeing, and what troubleshooting steps you already tried.

The World File Mismatch error usually means your Rust client has the wrong version of the map or a bad cached map file. To fix this, you will need to clear your Rust map cache. Close Rust completely. Open your Rust install folder through Steam. Go to the maps folder. Delete the files inside the maps folder. Restart Rust and try connecting to the server again. You can usually find the folder here: Steam\steamapps\common\Rust\maps After clearing the folder, Rust will download a fresh copy of the map the next time you connect. If the error continues after clearing your map folder, try verifying your Rust game files through Steam, then attempt to connect again.

The Invalid Packet: Client Ready error is usually caused by a Rust game bug where a sleeping bag or bed tied to your player becomes invalid. When this happens, the client can error while loading and prevent you from connecting to the server. This is not something you can usually fix on your own. Staff will need to resolve the issue for your player data so you can connect again. Create a new help ticket. Include the server you are trying to connect to. Mention that you are getting the Invalid Packet: Client Ready error. Once staff reviews the ticket, we can clear the issue causing the connection error and help get you back into the server.