Faruk Pita · @pitaCSGO

4th Sep 2020 from TwitLonger

I fucked up..

Hi everyone,

I just want to be honest and say that the bug happened to me during an official game in 2018. I think it would be better if I said this myself, even though I realize it might potentially ruin any future possibility for me within csgo.
I want to be honest and say that I had this free look cam on for 5-6 rounds (not 100% sure since it was a long time ago). I should have reconnected immediately, but I didn’t and that’s where I did wrong.

The match itself was against mousesports in EPL. It was the last game of the season. We were already in relegation and mouz already in finals. It was just a game to be played out from our end.
I’m not trying to use that as an excuse but rather highlighting that I fucked up for no fucking reason. Us winning or losing this game would not mean anything (apart from fans cheering for us or mouz ofc).

I’m not sure everyone knows how this bug works but it basically from what I understand, happens when you type coach in console and have no other teammate alive to have your POV to be switched on to. That’s when the camera gets stuck on the position you type coach.
In this particular match in EPL against mousesports there’s a plug-in that ESL uses on the server which forcekills everyone on the server before going live. So there’s no typing coach in console. The plugin does that for you as soon as everyone on the server has written .ready. Unfortunately I was the last one to be killed by the plugin, and therefore my camera froze on the position I was at the moment and my bad judgement played its part.
Still this isn’t an excuse but I just want to highlight that I didn’t actively try to get this advantage. It happened randomly and I didn’t do anything to stop it. It took me 5-6 rounds to stop it and this is where I did wrong and admit I did wrong and I’m ashamed of it.
Right after the match I contacted Valve on Twitter in a private message. The reason why I did this was obviously because I was remorseful but also at the same time I wanted to get a fix to this. We didn’t play much online games in NiP so I wanted to get this fixed for the sake of the community.

I’ve had contact with Valve in private prior to this, and that’s why I contacted them in in the same way as before. At this point I didn’t exactly know how the bugged worked. I didn’t get an answer and I contacted them again 4 months later when I found out how it worked. Still no response. All it took was a tweet by Loord and a public opinion for Valve to do anything about this, sadly. If they would have listened to me when I contacted them in 2018 nothing of this today would’ve happened, and I could’ve potentially been the only case.
SS1: https://gyazo.com/0800971f16c4a438c30380679c4cadc1
SS2: https://gyazo.com/01e09badb3e5fad04ad9ced9f45a3a12
SS of previous contact with Valve: https://gyazo.com/a6fc9c459d625209e8aefda7e2ab6531

I’m aware of that my explanation might sound as an excuse, but that is not my intention. I’m 100% aware of my guilt and that I did wrong. My intention is to put some context in what and why this happened.

I accept any punishment handed out to me. I realize this will harm my reputation as a coach but I can’t undo things even though I would like to. I just have to accept this and admit my guilt. I’m sorry to everyone that I know and who knows me. I understand that you might look at me differently after this but I hope you can forgive me one day. The bug got the better of me, I acted irrational and I fucked up. I never used that bug afterwards. The only thing I did afterwards when it happened again was to press the keys 1-10 and the bug would stop. If there’s any admin who want to confirm that from my POVs in online games I’d be happy to assist with my demos.

I hope you guys can forgive me one day but I understand if you won’t.


Reply · Report Post