[Soviethooves]

Why was intervention required in the first place is what I want to know? I’m all for investigating after the incident, but why in the middle of a raid? Wouldn’t it make sense to allow the RP situation to continue and end before interrupting the IC scenario?

I’m all for staff doing what they need to do, but when they interupt a IC situation instead of letting it roll till there is a good time to pull everyone aside really annoys me. It’s the worst when you have a good raid or RP going and out of the blue *BAM* staff sit.

[Hungames]

I'm not sure why your drawing inferences from completely different statements given to you in-game. I would know seeing how I gave said statements.
Please explain what you mean by this? I'm not exactly sure what you are referencing.

Note how because this was Oneshot's situation and I was present dealing with it (to avoid the possibility of bias interfering, as I'm not involved with Interitus, the group you raided), no punishments would have been issued without me issuing them myself. I'm not sure you recognize this.
How is this relevant? No matter who could have issued punishments, all staff members involved had a presumption of guilt rather than innocence. When we tried to explain ourselves and repeatedly told you that I had been shot with a deagle by one of the people inside the base, you would not believe it. In fact, I am led to believe that you didn't even check the logs since a bullet hitting someone, causing damage and blood to be released, should be logged (if the system broke or something, disregard this).

I saw you molotov and enter the base.
Conveniently, you only saw the retaliation, not the provocation. Shouldn't you have a replay tool, as Gungranny mentioned, to view the entire situation instead of just flat out believing your fellow staff members?
I didn't stop you because I wasn't called until you'd already breached through the barriers. I wanted to see how far you'd go, and if it was just a show of force by molotoving the base.
When exactly were you called? When we first threw molotovs? When we gunned down two defenders who were firing at us? When we waited minutes for the first molotovs to extinguish? When we threw molotovs at the second wall and waited a few more minutes for those molotovs to go out? Or was it when we reached your buddy's weed room and were stopped before we could take the fully grown weed?
Of course, you entered the base and then I asked what was going on to avoid disrupting the RP as best I could, which is when the entire sit happened.
We were asked "what was going on" as soon as we reached the weed room. We were stopped from taking the weed out of 20+ pots, which I would say is disrupting the RP.
You were not "automatically labeled as guilty", as you claim. I asked you for explanation, which we tried to follow up but because my tools were broken at the time, I asked for the video that Gregory mentioned he had.
We were asked for an explanation, gave one, and told it was contradictory to previous statements (which was literally just saying what happened using different words). Until greg provided the video, it was full well assumed that we were guilty of randomly raiding and molotoving the base. We told you numerous times that I was shot first and to check damage logs, only to be ignored from our perspective.
As the video link emerged, another member of staff gave me a log which backed your side of the story, so I let it be.
Why did it take over 10 minutes to find one damage log? I told you I was shot and to check the logs, which shouldn't take 10 minutes. Isn't there a search feature?
I had the evidence I needed, and dismissed everything, no punishments were given, no punishments were even discussed by me, not even the possibility of a blacklist, ban or a warning so I'm not too sure why your trying to make out as if you would have got punished without it.
Punishments were not discussed since we thankfully had a video of the situation. Had greg not been recording, we most certainly would have received bans or blacklists for raiding the compound. Until the very moment that greg provided the video, we were guilty in the eyes of the staff involved. I don't know if they withheld that their team member had shot me, but nevertheless, our explanations were met with a blind eye.

[Nev]

Definitely a disappointing situation to be in as an ex-staff member and I fully believe that, had Gregory not been recording the situation, this entire group would have been in a presumably sticky situation.

What I find to be most certainly disappointing was OneShott's involvement only at the point where it most affected him and repeatedly stating that, "

Limelight - Link watcher

You're about to enter the following site: Limelight - Link watcher You're about to enter the following site: https://youtu.be/tdG9gRJABaQ Please note: You should only visit trusted sites. We are not responsible for any loss of your privacy. https://youtu.be/tdG9gRJABaQ Please note: You should only visit trusted sites. We are not responsible for any loss of your privacy.

not a single shot was fired I was there," which was disproved by the video and a video recording of this statement can be found by clicking the quoted text. He was either lying about the situation or making a biased assumption based on what his clan member(s) were saying via Discord. He didn't know the situation in it's entirety, but still decided to go and take OOC-action on that premise... something that should not happen from any staff member. 

Is it abuse? Is it negligence? I obviously can't be the one to make an assessment, but I think using your power and rank as a staff member to provide inaccurate statements that have the implication that they're fact is not something I like to see. Staff members need to be fair and should not jump to conclusions. If your tool(s) were broken, why did OneShott fail to provide accurate DamageLogs that showed who fired first? Was he withholding this information?

[bismo]

Why was intervention required in the first place is what I want to know? I’m all for investigating after the incident, but why in the middle of a raid? Wouldn’t it make sense to allow the RP situation to continue and end before interrupting the IC scenario?

I’m all for staff doing what they need to do, but when they interupt a IC situation instead of letting it roll till there is a good time to pull everyone aside really annoys me. It’s the worst when you have a good raid or RP going and out of the blue *BAM* staff sit.

either that or stop us right when we throw the molotov, not the second we get to their weed room and start taking it lmao. if we lost the raid there never wouldve been a sit. just a staff member upset he lost.

[pufitee]

whos messing with greg ur going to get slapped

[Jeff Ford]

Excellent sob story.

Better than those on XFactor.

[Night]

So we've just had a chat in staff channels surrounding the situation.

I didn't stop you because I wanted to see what your actual intentions were. This stems from my days as mod. Back in sits, I'd be hit with "Oh, you stopped me, if you didn't then I was going to do xyz", I waited to see exactly what you planned on doing, what you were going to do, how you were going to do it to avoid any unknowns during the sit. Makes it easier for everyone that way.

Without discussing staff tools as I'm restricted from doing so in depth by HR, they come with their flaws. They aren't exactly the easiest things to use either. In this case, the logs I was looking for were on the edge of an hour, making it impossible for me to see it without adjusting my search, which I didn't do because I was under the impression it would have been recent enough to show up without search parameters. This wasn't pointed out to me until the video link came up and as I mentioned in the sit, I raised it and asked why one of the Interitus guys opened fire.

The call for me to check damagelogs was not ignored - I did, but as I explained it wasn't visible to me at the time for the reasons I explained. From what I'm told, Oneshot's guys were telling him no one shot until the evidence came up. No one said a thing on their side until the evidence came to light. Not only the video you provided, but the logs uncovered by the moderator whilst the video was uploading. This made no difference to the outcome of the case.

Oneshot didn't check the damagelogs either, and was going off what he saw and heard, as well as the word of his guys. He didn't check them as I was the staff member handling the sit, and as he wasn't expected to make judgement in the sit as that was left to me, there was no need for him to do so. There were other staff members there as well, so there was no need to dive into logs seeing how I was handling it and until the questions started occuring, other members of staff raised that I was looking at the wrong thing. Speaking to Oneshot, he now agrees that in the future, if this situation were to repeat, after the shots were pointed out then he should try to help. The reason he didn't in this case was because a senior staff member, me, already checked them.

I didn't arrive until you guys had already threw what must have been 3-4 molotovs already and were hanging around. I'm not sure if you intended to hang around or wait for it to burn, which is why I made the call as the most senior staff member on to hold on and see what you planned to do. Again, refer to my first point as to why I do this. I stopped you when I was sure it was obvious what was happening (when you breached the weed room), and asked I believe Nev and possibly greg what's going on and what the reason for the raid was, so we could discuss it. This isn't meant to be disruptive, and is obviously subjective as to how disruptive it can be. I only meant to keep you there until I could quickly clarify the reason and then have you continue, which is why I didn't drag you to a roof and force you out of the RP.

Greg's recording was helpful, but not pivotal as to whether a punishment was going to be issued or not. Like I said, punishments were not discussed, nor were they going to be discussed. You guys weren't even given a verbal warning in that situation. Even without it, I would have still had the damagelog that would show you were engaged upon first. This emerged pretty much the same time you posted the video link to the chat, which is why it perhaps wasn't brought up until the video emerged, but HR can confirm that I was made aware to the damagelog around the same time if they do their own investigation into the matter.

I'm not sure what leads you to believe I didn't check damagelogs, as I repeated told everyone in that sit that the only logs I'm seeing were ICEKILLER vs Brittania. So yes, I did do my checks, but perhaps not correctly as I missed information which was later raised to me as explained.

I'm not saying that we as staff members are completely clear of mistakes in this situation, as I know I personally made a few in not checking staff tools to clarify the wider situation, not seeing if there were preceding logs prior to what I was seeing that were relevant and perhaps not being as clear as I should have been, but hopefully now I've identified these mistakes they won't happen again in future. Obviously, apologies for the issues. You should understand though that the attitude we were presented (whilst I can't say it was perfect from other team members), from you guys didn't help the situation. I understand frustration and I understand anger, but there's ways to manage it without it being flung back and forwards at staff members.

As part of the review with other staff members, I've decided it best to issue a permanent warning to the person who made the call that no shots were fired from their side when they did in fact open fire first. Had they been honest from the start, then we could have quickly identified the issue and concluded the situation a lot quicker, but because that information was withheld, it caused investigations to take much longer. Thankfully, this didn't have a direct effect, so it's being met with a permanent warning.

[Nev]

I think I can agree with some points you made - but I think being a staff member comes with the need to do your own due diligence and that doesn’t excuse the fact that we had a certain someone taking the word of his clan members over the word of another community member. This is the most straight-forward example of being biased.

To say that he isn’t responsible for checking logs just because the situation wasn’t being handled by him isn’t an excuse. He still came there to the @ sit with the mentality that we did something wrong and attempted multiple times to pin us for varying reasons that I have on recording, which includes making it seem like we were “lying in an @ sit,” followed by the unprofessional act of calling one of the individuals there “fucking dumb” which should never be acceptable.

[Night]

Of course it comes with due diligence too. We had no reason to suspect that shots weren't fired until the point was raised by you guys, the only struggle was trying to find the log lines to support it, which is why we asked for the video instead. I'm not sure if I'd go with biased, but instead just inaction. We've had a talk about it though and in future I believe Oneshot understands to prevent similar situation from happening again.

My posts, the first one posted, the last, and this were not about excuses whatsoever - we accept that mistakes have happened during this sit, and hold our hands up to them but there were mistakes on both sides, the main one on your side being the attitude we received back. Perhaps the main one on our side was a failure to do our due diligence as you say.

I'm completely with you on the insults though, that's unacceptable and I've outlined to Oneshot I'm not impressed. He's recognized it was a bad thing to do as well.

I'm going to close this thread seeing how I've answered every point raised, and don't want it to be circling. Any further concerns though should be passed to HR, who are aware of the situation may I add.