Zombie Land

Fair Treatment For All

Administration Policies

How our admin team operates, and why. One set of rules applied equally to everyone, from the newest spawn to the most tenured veteran. These policies keep it that way.

Same ruling for everyone Tickets only Proof drives support

The three pillars

Doctrine

Every policy below is one of these three ideas applied to a specific situation.

Fair treatment for all is the whole point. The moment we take one person's word for it, we have to take everyone's, and the moment we pick who to believe, we have opened the door to favoritism claims. That is a server killer. So the line holds for everybody.

Corpse Recovery

Support scopeTicket immediately

In general we do not recover player corpses if the corpse death was due to normal game play or the corpse is reachable via normal gameplay methods. Keep in mind normal game play includes Rust glitches such as riding a horse under a low hanging entity that clips you and kills you. That is but one example and there are many more. Reachable via normal gameplay includes, but is not limited to, things such as having to crouch jump to reach the corpse, or requiring a minicopter to reach the corpse.

What we do help with

Bugs in our plugins, maps, servers, or other things completely out of player control, not intended by our design, not already posted in the known issues, and not a vanilla Rust issue. A mistaken hole in the map or a server crash are the classic examples.

What we do not

Normal deaths, Rust glitches, and anything you can reach with a crouch jump, a ladder, or a minicopter.

If you die by one of the things we help with and cannot retrieve your corpse, place a support ticket immediately or we will not be able to assist you. Rust does not log these things. Once that corpse is gone it is pretty much gone, unless you were smart enough to press your Shadowplay hotkey and clip some footage that shows your inventory.

Falling under the map

Proof requiredVehicles

If you fall under the map we require one of two things to recover your corpse:

  1. Physically see the hole you fell through, or reproduce it ourselves by you showing us where it is so we can patch it.
  2. A video clip showing how you fell through the map if you cannot provide the first. Shadowplay or similar software makes this trivial.

There are no exceptions to this. We are now taking a hard stance on this as the new "meta" has been to do stunts and other reckless activities in vehicles, causing players to clip through the map and die. If you cannot provide one of the two, do not put a ticket in. Your best bet is to swim towards the closest water on the map, because it will let you clip back out from under the map. See also the Angel plugin note on Known Issues: if you are in a vehicle, dismount.

Moving stuck vehicles

VehiclesNot supported

We do not get involved in moving any stuck vehicles for any reason. Vehicles (even the plugin spawned ones) are vanilla objects. How they interact, get stuck, or collide with things is strictly in Facepunch's hands. If you have a plugin vehicle use /recall to get it back. If you have a vanilla vehicle (not from the plugin) just be more careful. It is pretty much impossible to get a vehicle stuck without you doing something reckless that caused it. Hate to be mean, but you need to own your mistakes and learn from them. We are not there to fix things that are not broken.

Server Crash

No items spawnedRollbacks

Unfortunately server crashes are an inevitable side of Rust. There is no amount of hardware that can avoid these situations. Our two largest servers at full capacity with queues typically only use about 6 to 10% of their CPU and RAM. RustDedicated.exe (the software that runs server side) is just not very optimized and frequently has issues. They are unpredictable and completely out of our control.

Any server crash will almost always mean a roll back because servers do not save constantly (that would be impossible). The most it can be is 10 minutes. The least is 0. But it is inevitable that some progress will be lost. Other major actions could not be saved either, such as completing a quest. Plugins typically save their data immediately upon action. If you put something in your backpack, it gets saved right then for you personally. If you complete a quest, that completion gets saved to the quest data file for your SteamID immediately. But a Rust save file is global and only saves every 10 minutes.

The rockets example

You pull 10 rockets out of your backpack into your inventory. The backpack plugin saves instantly: no rockets in the backpack. The Rust save file has not saved your inventory yet. The server crashes. You reload before the move happened, so your inventory has no rockets, and your backpack, which saved immediately, does not have them either. They are gone.

The lucky version

Reverse it (inventory into backpack) and you get the opposite effect. The backpack saved instantly, then the roll back restores your inventory from before the move. Now you have the rockets in both places. Multiply either case by 100 players and it is an impossible task to sort out after a crash.

There are no exceptions. We will not spawn in items as a solution to a server crash. Players and admins alike (admins earn their items just like players) are most likely going to lose some progress in the event of a crash.

This does not mean the admin team just sits back and watches the world burn. In the event of a crash we issue an "all hands on deck" in our staff Discord and work through this list:

1Rescue the dead

As the server comes back online we search the console activity log for player deaths, assemble names and coordinates, and teleport to each one to save the player's inventory. We deposit it into their base if one can be located. If not, it goes in a box in or around Town with a sign carrying the player's name, and we use the /share command to grant that specific player access to the box.

2Restore the raids

We clear all raid timers for the entire active player base on that server. Players in the middle of a bought raid submit a ticket, we verify via activity logs that it was purchased and not completed, then spawn a raid locked to that player, making every attempt to spawn the same one.

3Rebuild the progress

For players running Shadowplay (which should be 100%) who captured a clip when the server went down, we use admin abilities to spawn the same base and destroy entities to get the player as close as possible to how far they had already progressed.

Spawning items

Firmest stanceProof required

The short statement on this is that we do not spawn in items for players under any circumstances without concrete proof through video or an admin physically witnessing the loss themselves in person. Seeing a player complain in chat about it does not constitute an admin seeing it happen. There are many ways for players to lose items and we provide countless resources to cover yourself from being a victim to losing items.

The backpack

A backpack that does not drop on death (except during PVP), with a command you can bind to a hotkey to pull specific items straight to your hotbar. Set as many hotkeys as you wish. You could carry all of your important things in it and pull them as you need them.

The trade plugin

A trade system so players do not need to throw items on the ground to pass things between each other. Items thrown on the ground have been known to disappear.

Clip software

Shadowplay, AMD ReLive, Medal, or any similar DVR style software. It is mentioned in every meeting, in the filing of every support ticket, and posted with flashing red lights in our support channel as a requirement for all tickets. Yet 80% of tickets ignore it.

These recording apps do not flat out "record" your gameplay and they do not lag your system. We have seen players run them on bare minimum spec laptops with no issues. You pick a time length, set a hotkey, and just play. If something happens you want to record, press the hotkey and the software saves the last X minutes of gameplay to a file. It is that simple.

Our policy for not spawning items is firm. No amount of cussing at us (yes, this is a common occurrence with these ticket types), no amount of "but why would I lie?", and no amount of "bro, you know me though" is going to change that stance. It is probably the most firm stance we have on our servers. But not for the reasons one may think.

We believe in fair treatment for all players. From the newest, to the meanest, to the most tenured and polite. We handle all support situations equally. We really do believe you most often. We do know you would not lie to us most of the time. And we do "know you" and like your presence in our community. But that does not mean we can spawn items in for you without proof, because that would mean we would have to do it for everyone. The problem does not fall on you for lying, it falls on other players knowing we will take someone's word and spawn in items. With fair treatment for all, if we take the word of someone we know and like and are sure would never lie to us, we also have to take the word of everyone. And that is where the issue comes in.

This means that anyone at any time could just claim they lost whatever stack of anything they desire, and we would have to spawn it for them. We have no way of differentiating the truthful from the untruthful, and it would spread like wildfire. Rumors of "just put a ticket in, the admin team will spawn whatever in for you" would spread. And if we then applied scrutiny to who we believed and who we did not (the only logical solution to taking someone's word for it) we would open ourselves up to massive claims of admin favoritism or admin abuse. That is a server killer, period.

So our stance is firm. We make every effort to alert players to this stance, to provide players with means to never be a victim of losing items, and to make sure players always have ways of providing proof. We have done our due diligence on this topic, so if a player refuses all of those methods, it is the player's fault when they do lose an item. We cannot force you to read or educate yourself on all of these methods of protecting yourself, but that responsibility still lies on you.

You can lead a horse to water but you cannot make it drink.

Support Communication Methods

Tickets onlyStaff conduct

The staff and admin team on our servers are strictly forbidden from handling any administrative business via voice, DM, or any other method outside of a support ticket. While this may seem restricting it has many valid reasons.

Training

We use our support ticket history for training. It is quite common for new staff to spend countless hours pouring over old tickets to see how we handle all of the unique situations that arise.

Integrity

Handling everything through tickets keeps checks and balances on ourselves. The team can see how each other handles tickets and talks to players, and leadership can quality control answers, actions, and boundaries.

The right admin, fast

We know which admins are on which server, which are busy with tickets, and which are swamped behind the scenes. A ticket lets the team pick who is best suited and most available for your issue.

Players might see an admin in game and not realize he or she could already be working another ticket, could be working a serious server issue, or could even be taking some personal time to just enjoy themselves, not realizing there are a dozen other admins on stand-by that could easily help. It is quite common for players to type "admin!" in chat, which will get you nothing more than a snarky answer from our automated chat bot.

Ultimately, if you are having a true time sensitive emergency, such as falling under the map and slowly freezing to death, then yes you can scream out "Admin I fell under the map!" and we will assist you if there happens to be an admin present in game. Even then, it would be smart to get a Shadowplay clip of your inventory and of you being under the map just in case. But if your issue is something that could still be solved without an immediate reaction, please put a support ticket in. It is extremely important to us and a very strict policy we have.

Teammates: moving sleepers and deleting items

Not supportedWe are not an Uber

If your teammate logged out in a bad spot and you need them moved, they will need to log into the server and move themselves. We are not an Uber.

If your teammate built or deployed something and you need it removed or destroyed, your teammate will need to log in and /remove the item for you.

We do not assist in these types of situations. There are no exceptions.

Related reading: General Rules, Known Issues, and the Explicit Content policy.