Are admins allowed to abuse rules if they know a Dev?

[john@thesmileyone.co.uk 7]

The clan has some kind of personal relationship with one of Rocket's Dev's, this seems to mean to them that Rocket's rules dont apply to them.

Several groups of players who have played on their server, specifically US 46, have noted that every time they raid an SAS camp, the server is quickly rebooted and everything they have taken inc vehicles that they have saved has magically reappeared at an unharmed SAS camp in the same place. Including myself, I have personally blown up the same camp in the same spot three times, only for a reset to take place.

Anyway they say a picture speaks a thousand words so here is Rocket's main quote and here is a picture that I have highlighted for you

Meta-gaming (like the infiltration that happens in EVE) is part of DayZ

If there are servers that are banning people for this meta-gaming' date=' report them and they will be warned. Continued violations they will be blacklisted.

Banning for cheating? It depends what you mean by cheating. I've heard some admins who think that teamspeak ghosting is cheating.

Betrayal and shit like that is part of the game.[/quote']

[ispecter 55]

I think your right, I don't think its fair they abuse the system I'd strongly advise you not use that server if they abuse the privilege of owning one. Granted its inconvenient to you but if everyone does it sends a message that the community as a whole doesn't put up with it.

Kind Regards,

Ryan

[rocket 16567]

Its certainly not allowed.

It will become less of a problem with some of the planned updates, as the move to string updates means your chances of rebooting before a change is applied is, well, very unlikely. It is tied in with some disconnection and respawn abuse fixes that I am working on as we speak.

So, it is something we need to keep an eye on and keep doing as much as we can.

[Chauz 166]

Its certainly not allowed.

It will become less of a problem with some of the planned updates, as the move to string updates means your chances of rebooting before a change is applied is, well, very unlikely. It is tied in with some disconnection and respawn abuse fixes that I am working on as we speak.

So, it is something we need to keep an eye on and keep doing as much as we can.

Glad to hear, is it something worth to report if you stumble upon and can devs check up on it?

[ZedsDeadBaby 2287]

Glad to hear, is it something worth to report if you stumble upon and can devs check up on it?

I would say let's let him focus on actually fixing the issue rather than running around frantically trying to stamp out fires.

I'm not against enforcing the rules, I just think in this case the best method of enforcement is just to fix the database commits so that reboots don't "roll back" the game state.