Random events without accountability and the checker-table fires of Victory-2.

[Conundrum]

---

I don't have to say how annoying this is to deal with. I'm all for random events, but there needs to be accountability and staff absolutely need to attach their names to it. Victory-2 has been set on fire twice since the server opened and both involved spontaneous fires by unidentified admins, the former reportedly due to them seeing it as inactive and 'wanting to free it up' which was not their decision to make in any capacity.

Since it happened to be Victory-2 and their checker table catching fire again I'm just going to guess it is the same admin involved back in the old days. I would like staff to log these random little destructive events somewhere they can all see as these unfair acts can get characters heavily punished (See Sleiters momentary PK over a fire in his store.) If this is not done I'll just completely ignore these store burn downs going forward.

As far as I am concerned this fire will be cleaned up in a day with no consequences whatsoever. So whatever purpose was behind this will not get the desired result.

 

[TheDeNuke]

The #event-logging channel on discord exists for a reason. You cannot start events such as "fire events" which are big and ultimately server wide without first logging the fact that you are doing so.

 

[Gazzpacho]

We have to get used to admins doing random things. First off these fires as you said, after that, I had many rebel friends who played on this server and told me admins randomly spawn hoards of zombies, and then expect the rebels to fight them off, their death counting as a PK.

I don't really see the point in doing all of that, and it pretty much ruins the peace of everyone I guess. But if admins think that is the way to make activity on the server, I'd rather suggest two factions working (or fighting) with each other if you really want activity. Activity is not a real concern anyways as you have around 40 to 50 active players daily. Setting Victory-2 on fire gets people more angry than active, and here it is, they begin to make posts about it.

THINK ADMINS THINK!

 

[Asimo1234]

Let us not forget the bomb at the top of the RDT. It blew up Combine infrastructure, and uh oh if OTA had taken it serious and used it as a reason to sweep.

 

[HOKI]

AGREED. I HATE ADMINS. SOME ADMIN DRUGGED ME UP AND EVERYTHING LOOKED CARTOONY

 

[swagile]

Let us not forget the bomb at the top of the RDT. It blew up Combine infrastructure, and uh oh if OTA had taken it serious and used it as a reason to sweep.

To be fair, a useless 3rd floor RDT room that no one knew existed that later created roleplay for CWU and citizens in cleaning it all up, and caused a fracture and stress in CWU ranks ICly as we were under heavy burden by other repairs and orders at the time, which created long lasting RP and rivalries.

@Neonity did that one I believe.

 

[Sagsworth]

This is a minor thing, but if you're going to do random bullshit rebel events that rebels didn't orchestrate and will get fucked for when cops / OTA sweep like bombings etc.

Please at least contact some rebel groups to get them in on it

 

[Gazzpacho]

and will get fucked for when cops / OTA sweep

I heard rebels made the OTA shit their pants last time they intervened.

 

[Sagsworth]

I heard rebels made the OTA shit their pants last time they intervened.

You heard wrong

 

[Neonity]

To be fair, a useless 3rd floor RDT room that no one knew existed that later created roleplay for CWU and citizens in cleaning it all up, and caused a fracture and stress in CWU ranks ICly as we were under heavy burden by other repairs and orders at the time, which created long lasting RP and rivalries.

@Neonity did that one I believe.

It was never intended to blow up, but blowing it up caused more good than bad in the end. I’m glad it ended up this way.

 

[Rebel RP Philosopher]

Let us not forget the bomb at the top of the RDT. It blew up Combine infrastructure, and uh oh if OTA had taken it serious and used it as a reason to sweep.

Reminds me when an OTA tied a winch from a train to a bridge, so that when the train drove away - the bridge did mass destruction on infrastructure. The same OTA died shortly later kicking some infrastructure. This was back in the beta - D47.

 

[swagile]

So I have ignited a prop and then checked logs.

Ignitions aren't actually recorded, which is concerning, so unless an admin owns up to this its really not something we can check. I could be wrong since the direct database might have more tools to search this stuff up, but as a admin with the ingame logs option I cannot see anything ignition wise.

 

[NEYO]

---

I don't have to say how annoying this is to deal with. I'm all for random events, but there needs to be accountability and staff absolutely need to attach their names to it. Victory-2 has been set on fire twice since the server opened and both involved spontaneous fires by unidentified admins, the former reportedly due to them seeing it as inactive and 'wanting to free it up' which was not their decision to make in any capacity.

Since it happened to be Victory-2 and their checker table catching fire again I'm just going to guess it is the same admin involved back in the old days. I would like staff to log these random little destructive events somewhere they can all see as these unfair acts can get characters heavily punished (See Sleiters momentary PK over a fire in his store.) If this is not done I'll just completely ignore these store burn downs going forward.

As far as I am concerned this fire will be cleaned up in a day with no consequences whatsoever. So whatever purpose was behind this will not get the desired result.

So I have ignited a prop and then checked logs.

Ignitions aren't actually recorded, which is concerning, so unless an admin owns up to this its really not something we can check. I could be wrong since the direct database might have more tools to search this stuff up, but as a admin with the ingame logs option I cannot see anything ignition wise.

Yo,

Votton and myself have looked into this particular situation, as Sawgile has said there are no logs for igniting entities or props with the C menu in the in-game logging system nor is there any logs on the server side. So far no staff member has come forward and there are no logs of a player rping setting the fire, but as this is a "mini-event" that can cost a player their credits, their store, their character, with no staff member coming forward about it and it being the second time this has happened to this exact store and player, we are taking it pretty seriously.

Obviously this isn't hugely helpful to you but there is very little we can do outside of pointing fingers at other staff with no evidence, if an admins behaviour seems off, malicious, trollish or irresponsible etc I'd urge you make a formal complaint/admin abuse report or if you are worried this may make you a target in some way, contact either H.O.S, a CM or most SAs.

 

[verTix]

So I have ignited a prop and then checked logs.

Ignitions aren't actually recorded, which is concerning, so unless an admin owns up to this its really not something we can check. I could be wrong since the direct database might have more tools to search this stuff up, but as a admin with the ingame logs option I cannot see anything ignition wise.

sounds like another issue for the devs who have been transported to another reality it seems

 

[Votton]

I'll close this report, we have an idea who it is, but as said before regarding the lack of logs, it can't be said for certain.

Though, @Aspect could maybe implement a few more logs in, which would prevent cases like this from happening ever again as this is the second time it has happened to the same store.