TahxaGen Report

[Rubik]

What was the sit on Prove for specifically?  Was it related to the raid at all or some other random issue?

[TahxaGen]

It was kinda part of the raid. Prove was raiding and then tried to kill rumbly when he was no where near the raid area. 

[Dilfs]

4 hours ago, Abstergo McStubbins said:

After reviewing this video evidence, I'm honestly more confused than I was before. It does seem like Tahxa legitimately believes the locations he is showing you are what his logs are showing him. What I think would help here is to see the conversation had between you and Tahxa in discord. At 11:45 you also say "I'm just being difficult at this point" and that kind of thing does start to make me question the validity of this report. What I'm really concerned about here is somebody being allegedly pulled out of a raid and stripped then returned, because that sounds like an actual issue. Do you have anything from that particular sit?

Sadly I do not have really any evidence of him stripping me. The closest screenshot of that I have is this https://prnt.sc/10jv7oy. I asked him multiples times why he stripped me and if I can get my items back, he tells me to just "Just kill bind". When Prove wakes up I can see if he has anymore of the clips and such.

[Rumblykibles74]

"Also i gave other staff plenty of time to take the sit, i pinned it and waited but no one took it" 

[Chirs]

8 hours ago, Abstergo McStubbins said:

After reviewing this video evidence, I'm honestly more confused than I was before. It does seem like Tahxa legitimately believes the locations he is showing you are what his logs are showing him. What I think would help here is to see the conversation had between you and Tahxa in discord. At 11:45 you also say "I'm just being difficult at this point" and that kind of thing does start to make me question the validity of this report. What I'm really concerned about here is somebody being allegedly pulled out of a raid and stripped then returned, because that sounds like an actual issue. Do you have anything from that particular sit?

There's a glaringly obvious problem that I believe you're overlooking. This video is recorded before we ourselves reviewed the evidence presented to us by Tahxagen, which was the screenshot. The problem in this situtation is staff bias. According to the TitsRP Sit Guidelines, one of the very first guidelines is "Ex. BAD/BIASED STAFF Uses bias against a user to further the stance of a sit, doesn't use concrete evidence to come to a conclusion, but uses personal grudges against a user to further the stance of a sit." The evidence provided by both Prove and Swizzle shows that Tahxagen provided, either knowingly or mistakenly, false evidence to support his friend in his sit.

• Instead of reading all of the information for the sit, which he had ~15 minutes to do during the sit and plenty of time afterward to double check himself, he doubled down on wrong information and decided to warn Prove and Swizzle to intimidate us from continuing the raid.
• We know TahxaGen was a part of the base because his name is at the very top of the door. We have tested this ourselves and staff can confirm it as well, but when you're the first person to buy a door your name stays at the top of the list. Now it could be that staff somehow overrides that list and gets to the very top of the door list, but we have no way of testing that as we are not staff. He can also be seen in their group from the screenshot that he was kind enough to provide us.
• We know the screenshot that TahxaGen provided that he alleges shows RumblyKibles74's position when he was damaged was not his actual position. We were fortunate enough to have a screenshot of the 'slogs' of the moment Prove damaged RumblyKibles74 and where his actual position was. Please refer to Citation 10 for the slog and true coordinates. If you go to the coordinates from the slogs it is very different from the coordinates provided by TahxaGen. He has access to the same slogs we do, so he had the opportunity to double check himself to ensure he was not falsely punishing us. 

There is plenty of evidence to make this a valid report. When you're put in a situation where you, as the player, are doing everything right and you get stripped and punished it can be quite frustrating as you can tell from our voices in the video. We knew there was something fishy about the situation when Tahxagen decided to call the sit only after he made his way into the sewer, went near the base, and got smoked like a brisket. He knew that he and his team lost the raid defense and instead of moving on, he decided to escalate the situation and punish us without "concrete evidence." We, as the players, were able to dig up more concrete evidence about the situation than someone who was trusted to protect the integrity of the playerbase and that should be very concerning. I hope the higher-ups will look into this thoroughly and check the information that is not available to us the players. I believe if you check out the coords of the base, the damage logs of Tahxagen and RumblyKibles74 from ~11:40pmEST, and cross-reference the two; You'll find that Tahxagen and RumblyKibles74 were both within eyeshot AND reasonably close to the base. 

 

Edited March 12, 2021 by Chirs
Added the reference to Citation 10 and an extra argument for the case.

[Crabroll]

My main concerns after reading this entire report is this. "DO NOT attack a base member while raiding they must be both within eyeshot AND reasonably close to the base" Tahxa has provided evidence that you guys were shooting at base members who just entered sewer entrance. Rumbly just entered lower sewers and reasonably he would barely be able to see people knocking on his door so I do not think that this is fair.

With that being said, if he calls a sit on you for attempted rdm for essentially taking potshots at a random dude walking around sewer, that would be a valid sit. Tahxa is allowed to take the sit. There is nothing in guidelines saying that he HAS TO get another staff to take the sit. What if there wasn't another staff member on? Or what if there is staff who is basically friends with many many people on the server. 

 

The things Tahxa couldve done better was to let you guys finish the raid before taking the sit. Pulling you into a sit like that is very disruptive of RP but i do not see any bias in his actions. If he wanted to push biasm, he could've banned you both for RDM. Instead of just leaving it at a warn. 

I would not blame Tahxa for this as you have also said that he just became moderator (even though tmod and mod have barely any difference in power on the server) but I would chalk it up to inexperience and lack of foresight. 

I would not see this as blameworthy in anyway. However, since you did not lose the SBC cannon due to rp reasons, I feel as though you are owed one. Whether from Tahxa or I will supply it.

 

Another thing. Raid zones. These are very dependant on the judgement of staff but we usually have a space that is somewhat collectively agreed upon. Since there are so many areas of the map you can base at, Obviously there wont be defined boxes for each and every one. I think this is a crucial point that staff should talk about. 

 

One last thing. Ownership of the door/party binds. You claim that tahxa was on the door but Ive heard from the other side as well that they were moving bases so ownership on the door was different than your screenshot showed. They claim that the screenshot was taken when everything was over and done with and settled. I would like to see any timestamps for that as well. 

 

TLDR: This is extremely messy from both sides, I dont blame either party for anything said in the heat of the moment. Stripping the player was probably excessive and the timing for the sit could've waited til after. I do not see any biasies from Tahxa and -1 for punishment for lack of experience. 

 

Will add more as I have more time. 

Edited March 12, 2021 by Reiko

[Blue.]

I think at this point, we need the SA's to verify the gaps in this report that can be verified. If this wasn't abuse, and a genuine mistake, such as making a strip bind and pressing it on accident, that's not the worst thing to happen. A fuck up, but a unintentional one. One you can learn from. With the way spectate works, you shouldnt move your mouse at all when using the spectate at position, as it will show exactly where the log was created. This may have been an error on his part perhaps? If it was intentional to strip or give different positions, that is bad.

Once the doors are actually verified, and the kill spots are verified I think a decision can be made. If tahxa wasn't on the doors at the time of the attack, it would be RDM and he would be justified to bring you to a sit. I think jailtping can give a bad taste for the sit, but what's important is his behavior in the sit. Which did seem to get slightly heated at a point.

I think tahxa should have apologized about stripping you, and telling you why you need to kill bind, vs just saying "just kill bind". I dont agree with you calling him a joke either.

 

Tahxa picking up a player in the mainland and tossing him away and making his boombox go down a waterfall wasn't very cool.

 

Looks like Tahxa could have definitely conducted himself much better in this situation. I think considering this a strike and taking it as a lesson to learn from might be the best outcome if he wasn't abusing any staff abilities on purpose with intent to gain an advantage.

 

[Rubik]

I initially thought we had door logs but I guess that is only stored in /slogs. Either way, if Tahxgen used their staff powers to interfere with a raid then that would be a big problem.

 

I do see that RumblyKibles74 called a sit himself so that pretty much throws out the question of Tahxgen getting involved without a sit, but I think he should have waited until the raid was over to intervene. Hopefully this will be a learning lesson for him. I don't want to get into what is or was a "raid zone" and all of that, I'm going to leave that up to the other staff, but I have no more info to provide from logs.  

[Dilfs]

8 hours ago, Rubik said:

I initially thought we had door logs but I guess that is only stored in /slogs. Either way, if Tahxgen used their staff powers to interfere with a raid then that would be a big problem.

 

I do see that RumblyKibles74 called a sit himself so that pretty much throws out the question of Tahxgen getting involved without a sit, but I think he should have waited until the raid was over to intervene. Hopefully this will be a learning lesson for him. I don't want to get into what is or was a "raid zone" and all of that, I'm going to leave that up to the other staff, but I have no more info to provide from logs.  

Understandable, I would like to get confirmation on some of the position logs, because Tahxgen, claimed I RDMed him, but from our screenshot you can see where I initially shot him the first time which was right next to the base we were raiding. We also have the position logs of RumblyKibles when he first got shot too, which was also in near the base, why did I get warned for RDM and Prove get warned for ARDM, it doesn't really make sense to us. It feels like everything he said to us was a lie so he wouldn't get himself in trouble, You can see in the video where he shows Kibles was standing but the logs don't say that, the logs don't say that, Now i'm not sure if the logs are wrong or what but in my years of playing this game I've never experienced a wrong log. It just seems like everything he was saying to us was a lie to protect himself/party. I hope whoever makes the final decision on this can thoroughly look at everything we've said and match it up with logs in game.  

 

Edited March 15, 2021 by Symere

[Blue.]

So I'm going to go ahead and ACCEPT this. The staff member in mention will take this as a lesson learned on how to better handle situations like this, as well as the removal of Proves warn.

Edited March 18, 2021 by Blue.