tent persistence after the outage needs a real rule

Restarts, loot tables, vehicles, complaints about all three.
Post Reply
User avatar
grud
Posts: 54
Joined: Tue Feb 19, 2013 12:00 pm

tent persistence after the outage needs a real rule

Post by grud »

I still think we should have gotten the host's word in writing before we let the server sit for three days. I'd argue the problem was never the outage itself but that nobody could agree on the restart rights. Per the rules as written, the admin team has the final call on manual restarts, but that isn't the same as having a rollback policy, and we don't. The blood bag that ran out in the field back in '13 is the exact same pattern: everyone stood around deciding instead of doing the one thing that was already allowed. We need a written emergency procedure with a named backup before the next thing hits. I know it's just a game, but the precedent is there and pretending otherwise is how wipes happen. The host's maintenance window is another issue entirely. I'd rather spend a thread on this than on who gets to keep the Ural after a restart. That's the part that will actually split the server.
User avatar
VLK
Posts: 110
Joined: Thu May 30, 2013 1:00 pm

tent persistence after the outage needs a real rule

Post by VLK »

grud, the tent camp despawn was the same pattern. Everyone assumed the restart rights were with someone else and nobody acted. A named backup would have helped there I think. The server is quiet at 4am.
User avatar
grud
Posts: 54
Joined: Tue Feb 19, 2013 12:00 pm

tent persistence after the outage needs a real rule

Post by grud »

VLK, the etnt camp thing is exactly why I keep bringing this up. Nobody wants to be the one to make the call, so nobody does, and then we lose everything and blame the host. We had the same problem after the ban, everyone chose a side instead of checking what the actual rule said. I'm not saying a written policy fixes everything. I'm saying we spent three days talking about restart rights and never once put a timestamp on a forum post. That's not a host problem, that's a us problem. I stayed up through most of that outage and the weird part was the daylight cycles kept running lkie nothing happened. If we cant agree on a named backup by the next maintenance window we'll do this again in June. Anyway I should get some sleep, the 4am crowd is the only one left on.
User avatar
Doc_Mallory
Posts: 185
Joined: Fri Sep 14, 2012 1:00 pm

tent persistence after the outage needs a real rule

Post by Doc_Mallory »

grud, I was at the tent camp when it despawned. Rained all that morning and the ground squelched under our boots while we stood around checking the same patch of grass. We did the same after the great wipe — even after kasper told us it was a config value, half of us kept driving the old routes. I think we were waiting for someone to say it was all a mistake. A written procedure wouldn't have given us that.
User avatar
VLK
Posts: 110
Joined: Thu May 30, 2013 1:00 pm

tent persistence after the outage needs a real rule

Post by VLK »

I can be the named bacukp if nobody else wants it. I am awake at 4am anyway. The shoreline night worked without a rule and the crossroads man just kept coming back. I think I can do the same.
User avatar
Kasper
Posts: 139
Joined: Mon Aug 20, 2012 1:00 pm

tent persistence after the outage needs a real rule

Post by Kasper »

Half the first day of the outage was waiting on a callback from the host. I think the ticket is still open. VLK, backup works if it has an end date. The great wipe was the same gap — nobody had said who speaks up when a number looks wrong.
User avatar
chad
Posts: 132
Joined: Mon Oct 08, 2012 1:00 pm

tent persistence after the outage needs a real rule

Post by chad »

VLK, end date makes sense, otherwise it's just another open job nobody owns. The ammo camp back in '14 was the same – we never found out who'd been there last because nobody logged it. I can put a rota together with two names per month and post it before the next maintenance window.
Post Reply