Known Issues
Periodically certain problems arise that just cannot be resolved. These can be map Rust related, plugin related, map related, etc. Things listed on this page will not be supported by the admin team as they are known issues that do not have an available solution to them. Players are encouraged to keep an eye on update-log or announcements in our Discord for new issues that arise and might be added to this list.
When adding a large stack of fuel to a miners hat or candle hat, drag the stack to the hat on your clothing bar. Do NOT just click the hat and then drag the stack to the hat inventory panel (that appears above your inventory panel) as this is a bug with Rust that will delete your entire stack of fuel
Killing an NPC at a raid base does not always lock the base to you. Neither does fire damage. You need to use something explosive on the base and/or actually break something on the base to guarantee it gets locked to you.
Example: "Too close to airfield" even though you are across the map from it trying to build on a river or something. Something with Facepunch's patch has the build error messages all jumbled. Just pay no mind to them. Nothing we can do about it, another core rust function we have no control over.
This just means your computer was not able to communicate with Dropbox (where our maps are hosted). When you connect to a server Rust downloads the map to your local hard drive. These are stored in the maps folder of Rust (typically "Program Files (x86)\Steam\steamapps\common\Rust\maps"). This directory can be completely cleared out anytime you wish without harming anything. But if your ISP or some other factor is stopping you from downloading our map you will get this error. Some countries even block Dropbox. Just open a support ticket and we will provide you with an alternative download of the map file which you can just manually stick in your Rust maps directory and then you will be able to connect just fine.
If 2 players call heli too close to each other, its possible the crash sites will mix-up loot and apply loot locks to the wrong party. You can simply wait out the loot lock timer and both helis will be lootable.
Players transferring RP among themselves, selling items to the /s store for RP, completing quests, etc. within 5 or so minutes of a restart have had that RP disappear and not save. Even worse is that the server logs show the RP as have being given. We highly advise against doing anything in the minutes leading up to a serve restart that gives you RP you won't mind possibly losing.
There has been an ongoing bug that if you get disconnected from the server during a raid base you might not get credit for the completion of that raid base (RP reward, even quest completion). Sadly this bug has been extremely elusive. Nivex has been working on this bug for almost the entirety of 2023 and has not been able to solve it yet. It is being listed as a known issue until it can be resolved.
With the most recent update a new glitch seems to have been introduced. If players are "trading" by throwing items at each other's feet there seems to be some sort of player hitbox collider issue that forces the items under the map. It seems to only happen if players stand close together and throw items at each other's feet. Once an item falls under the map there is no chance of recovering it as there is no terrain under there. The item will fall and throw an "invalid position" error which causes Rust to delete it. We suggest players use /trade for now. Without a Shadowplay or similar video clip we cannot replace lost items.
The recent updates appear to have sparked off a new type of error that is being spammed in some of our plugins error logs. This can eventually cause a server crash if left unchecked. The names that are causing this are when players write their name with emojis are strange format characters. The easiest way to tell would be to open up any GUI in game that shows player names (ie. /tp, /transfer, etc) and look for a name with just "???" or completely blank with " ". If that is you, we need you to pick a different name and relog immediately.
Players are able to 'self damage' on our servers. Meaning that if you own an object and you 'own' the damage it is allowed to pass. This is mainly configured for base mechanics but has some side effects such as destroying your own corpse bag. Players using incen or other tactics to kill NPCs need to be cautious that the fire they carpet the area with is capable of destroying their corpse (if they die) and contents of that corpse. After months of investigating random corpse disappearances we finally tracked it down to fire used by the player. This was confirmed in a log entry recently showing the player's fire as the cause for the bag to be destroyed. Be warned!
There have been numerous reports across all servers (not just ours) that weapon racks are randomly wiping their contents. There are also known issues with players being able to steal from them despite any locks or protection plugins. This is a Facepunch thing so we have no ETA on a fix. This listing will get deleted and announced in update-log if they ever fix these issues. But for now, use weapon racks at your own risk of randomly losing their contents.
When skinning certain DLC items that have a different short name it will remove all of your enchantments from that item. A good example would be skinning a metal facemask into an ice facemask. The ice facemask is a completely different item behind the scenes. So when you skin your facemask into that, the game is actually just deleting your old facemask and giving you an ice one. There may be other items than stated in this example. To figure out if your DLC item is indeed a whole new item you can check the list of Rust Item Shortnames. For example you can search "facemask" and see that there are multiple types. That is the indicator of the issue described here.