Most Important Answers!
Here you can find answers to a range of questions related to our game servers and other related services which are asked by players all the time. This list of questions is by no means exhaustive, so if you have any other questions which you think should be included here, please do let us know so that they can be added.
Firstly, make sure that you actually require an admin. Answers to many common questions can be found on the website. Make sure that you check the FAQ as well as the section related to the game you are playing for all relevant details.
If you have a question which is general or something specific to gameplay and not directly related to the server, you can either search online or try asking other players with in-game chat.
If you do need to ask the admin a question, you can create a ticket on the website, PM the admin on Discord, use in-game chat by starting your message with "admin: ", or you can make contact via email.
You will first need to figure out exactly what kind of lag you are experiencing.
If you are experiencing a low frame rate, random FPS drops, full game stutters or game freezes, the client-side game or your PC is most likely the cause. See 1.3 for more details on how to resolve these kinds of issues.
If you are experiencing high ping, delay when interacting with things or you are being teleported backwards, your internet connectivity to the server is likely the cause. See 1.4 for more details.
If you get stuck while "Receiving data" on the loading screen, you have a major internet connectivity issue, see 1.5 for more details.
The most common cause of client-side performance issues is insufficient hardware, but there are many factors which could make things a lot worse for you in certain situations. Your performance will vary depending on where your player is on the map in relation to other players and structures, as well as what is happening in the area.
If you have constant issues, you should make sure that all background applications are closed (especially things like web browsers which use your GPU), lower your graphics settings if possible, and avoid areas of the map where your performance is extra bad.
If you only start experiencing performance issues after playing for some time, your game has probably leaked too much memory, in which case you can try exiting and starting your game again.
Many players are CPU bottlenecked due to the current state of the games optimization. If you have a decent graphics card and are playing on the "fastest" graphics quality, try using the "fantastic" or "beautiful" quality instead. This will offload more work to your GPU and may result in better performance.
Running your game in fullscreen mode may give you a decent FPS boost but may also cause issues if you minimize your game depending on the current game build. You can enable exclusive fullscreen by adding the following to your Steam launch options for Rust: -window-mode exclusive
You are experiencing a major connectivity issues which is likely caused by something saturating your connection or an external issue related to your provider.
Most common causes of connectivity issues:
- A background application on your PC is saturating your connections available bandwidth
- Another device on your network which shares your internet is saturating your connection
- An issue with routing between you and the server is throttling your ISP connectivity
- A faulty or congested router somewhere between you and the server is causing packet loss
- Your provider is shaping or throttling your bandwidth due to their policies
- Congestion at your exchange is throttling your DSL line
You should first make sure that your PC and any other devices that share your internet connection are not using a considerable amount of bandwidth since a common cause of connectivity issues is a saturated connection.
The easiest way to rule out other devices is by unplugging the ethernet cable from each device and disabling wifi or turning off each wifi-enabled device on your property. You should close all non-essential applications on your own PC and monitor the bandwidth of all the remaining processes running to make sure nothing is using a considerable amount of bandwidth. On Windows you can open "Resource Monitor" and check under the Network tab to see which processes are using the most bandwidth.
If your Steam is downloading workshop content while you are experiencing issues, your connection throughput is likely unable to handle content downloads without degrading your experience. This could be due to a temporary connectivity issue, ISP throttling, or simply because the speed of your connection is too slow. You can limit the speed of downloads in Steam settings to well below your connection speed to prevent it from saturating available bandwidth. If you still experience issues while content downloads, lower the limit further until it is resolved. If your issues persist while limited to the lowest speed, content downloads are not the cause of your issue.
If you have ruled out everything on your connection, you likely have packet loss, high latency or throttling caused by ISP routing issues. Routing issues between different backbones are very common in South Africa and will usually be resolved after some time. Keep in mind that it is not unusual for your connectivity to other servers (hosted on different backbones) to be completely unaffected by these kinds of issues.
If your issues persist for an extended period, you should open a ticket with your provider. If you have access to an ISP account which utilizes a different backbone to your current provider, or you can borrow one, you may be able to use that until your providers issues are resolved. There are also a bunch of providers who give out free trial accounts such as 1GB per month which you can use to rule out your ISP as the issue.
If you continue to experience issues using a provider who utilizes a different backbone, your line is likely the issue. If you are using a DSL line, you can try requesting a port reset, else you will have to log a fault and get a technician to resolve it.
If your provider is unable to resolve your issue, you will have to consider moving to another provider on a different backbone.
If you get stuck while "Receiving data" on the loading screen, you are experiencing a major connectivity issue which is preventing your game from being able to download the required data within a reasonable amount of time. Keep in mind that it is not unusual for your connectivity to other servers (hosted on different backbones) to be completely unaffected by these kinds of issues.
Your connection to the server is likely being throttled due to one of the following reasons:
- An issue with routing between you and the server is throttling your ISP connectivity
- Your provider is shaping/throttling you due to their policies
- Congestion at your exchange is throttling your DSL line
- Someone using your connection is saturating your connection
Some servers wipe weekly, others every second week and some only when forced to once per month. You can find the wipe cycle information for a specific server on the website or in the server description using the in-game server browser. The last map wipe date can be found on the website and at the end of the server name in the server browser.
The first wipe of each month is forced by the Rust terrain update which is released between 6pm and 1am GMT+2. Mid-month wipes are done on a Thursday between 4 and 6pm GMT+2 as that is the most convenient time for the majority of regular players.
Public branch updates are released every Thursday sometime between 9pm and 1am GMT+2. Players get a few minutes warning before a server shuts down to update. The warning will tell you if you are required to restart your game to download a client-side update, and in most cases the server will be back online before you have installed the update.
Staging branch updates are released almost every day, as every change that the Facepunch developers make will automatically trigger a new build to be created. Staging branch servers will only kick players to update if the update released is not optional.
Prerelease branch updates are released only when there are major changes which require substantial testing before being released.
You can change your games branch by going to your Steam library, right clicking on Rust, going to properties and selecting the branch from the dropdown in the BETAS tab.
You should be using the public branch most of the time, which is called "NONE" in Steam BETAS. This branch contains the latest stable build which is compatible with the vast majority of servers.
The staging branch is updated frequently and contains changes which will be released in the next public branch update. You can use it to test out changes before a public branch update is released, just make sure that you remember to change back again later. If you change from the staging branch to the public branch right after a public branch update has been released, you will not need to download anything.
Although updated just about daily, the staging branch is compatible with the public branch most of the time, which means staging clients can connect to public servers and public clients can connect to staging servers. Compatibility with the public branch is broken when the changes made are not compatible, as well as before updates get released on the public branch.
The prerelease branch is only updated when the developers have major changes which require substantial testing before being released to public (such as the XP system and graphics overhaul). You should only ever change to the prerelease branch if you know there are changes on prerelease that you can't wait to test out.
Normal servers despawn corpses after 5 minutes, dropped items take between 3 and 15 minutes depending on how rare it is.
Battle Royale servers never despawn corpses or items during a match.
There is absolutely no admin influence on the game servers, which means you are completely on their own when it comes to anything directly related to gameplay. Nothing will ever be manually removed by an admin for any reason.
Depending on the grade and placement of the block, you can either destroy it slowly over time, ask friendly players to help, or possibly wait for it to decay.