Since this whole situation has been blown out of proportions I feel its fair for me to be transparent about what I was actually doing. First thing I want to get out of the way is that this ban had nothing to do with my demoknight and is entirely about my heavy in hl.
The first time I got banned (''Continued exploit usage'') was because of a simple misunderstanding on the anti cheat's end regarding what exactly was causing my demoknight turns to be so sharp. It is important to note that I'm going slightly from memory because everything I was told was in a private discord call with Biohazard. The misunderstanding boiled down to them thinking that m_filter 1 (bind mouse1 "+attack; m_filter 0" bind mouse2 "+attack2; m_filter 1") was the whole reason for my sharp turns. When in reality it was entirely due to my high framerate. After a very professional talk and me showing that I could make the same turns without m_filter 1 I was unbanned.
Also note that m_filter 1 makes players with bad framerates turn more like people with high framerate do, while giving 0 bonus to people with above 600fps(like me). This is probably where the misunderstanding initially came because it explains why the admins would think it gave me an unfair advantage if the testing they did on their end was on a bad pc. You can argue and say that AC should of known better but come on, its 1 unlock that was never used in competitive play until I decided to play it in 6s.
Moving onto the second ban it was simply me using interp 0.188 in an official and not turning it on/off like the person was doing here https://www.youtube.com/watch?v=qBXQwmazf-o. I have used default net settings on heavy like 0.100 interp ever since I started playing HL which explains why most people have a negative experience fighting me around corners. I used these settings because I didn't know any better until around the time this vod was created -https://www.twitch.tv/videos/2036603563 in which I experimented in scrims using 0.188 with a theory that I could shoot people for longer around corners(I will explain why this theory is incorrect later). After that vod I received a lot of hackusations and I decided to contact the AC team and ask if this was allowed or not, to which I was told a rule will be implemented and I shouldn't go above the default interp of 0.100 until further notice. A whole year and a half passed of me using lowest interp on heavy and only occasionally going to 0.100 in some scrims and this leads us to the recent ashville game in which I made a stupid decision to go 0.188 interp. The reason I went against what AC told me was simply a mistake on my end, I just forgot I had that conversation with them on the 1/22/2024. I know forgetting is not an excuse but in my defence 1.5 years of no rule update contributed to my forgetfulness.
After talking with Brian and some testing on my end it turned out that the theory behind it delaying how fast shutters closed/opened turned out to only be a visual bug and not affecting the hitbox of the shutter. This videos explain it www.youtube.com/watch?v=98_P-tugTOk. And the other theory of making people stay on my screen for longer was also incorrect. At it turns out 0.188 interp barely gave any advantage(At least on heavy) because people simply had delayed positions on my screen and weren't staying on it for longer like I thought. Basically if you were to peek me you would peek 0.188ms later, meaning I had no means of attacking back during those 0.188ms, but if you decided to unpeek you would still be visible on my screen for an extra 0.188ms, resulting in an extra bullet or two hitting people behind cover. It is literally just extra ping for no good reason.
TL:DR I was told not to go above 0.100interp and I went 0.188 in one single ashville official, resulting in a 4 week ban.
Now to address what Clark posted starting with the "ragehacking badwater pov" from 2019 https://youtu.be/qEpEWvTbtnQ?si=rPqqHLwzWgHjNEBS&t=522
This is simply a bug with how demos display player positions sometimes.
Showcase: https://www.youtube.com/watch?v=I5yD0sePVgU
How to replicate: Open tf2, join a private/online map and then play any demo of your liking. The resulting demo will have incorrect player positions, resulting in the person recording reacting insanely fast to people changing directions.
Addressing the "cancelselect'' in this clip - https://www.youtube.com/watch?v=wEqtbSo_LUc
Cancelselect is to do with hud_fastswitch 0. Here is a demonstration - https://youtu.be/oYT2V5C1GOs
I understand the confusion around this one since no one played with hud_fastswitch 0 at the time aside from me. And with regards to that medic flick, I do the exact same flick motion many times in this clip, most of the time my crosshair lands on nothing. This is simply how my aim was back in the day and if this demo was available in its entirety you would be able to see for yourself.
The demo dying behind rock - https://www.youtube.com/watch?v=Scv60GtGW7M
I have nothing to add except that I used 0.100 interp. This scrim was played on the 03/08/2024 and I was already aware of not going above 0.100 interp.
Addressing the soldier flick - https://www.youtube.com/watch?v=P44lxIj1h5Q
We had a big discussion prior to this game about how Blanc likes to play on this map. We discussed that if Blanc ever plays on cliff, the cliff rock bomb was his only reliable way of getting in. So when he was called bombing(timestamped clip of coms for evidence: https://youtu.be/ZZ8Qm0UzfGA?si=8395GuVWHUpX9gfn&t=2089) I knew exactly where to place my crosshair. It just so happened that I predicted him perfectly but if you still think this is cheating consider this, I didn't land a single bullet on him, and before you tell me that I missed because of minigun spread consider that minigun is pin-point accurate on the first shot.
Addressing the flicking away from spy - https://www.youtube.com/watch?v=3fCutmzoL-4
Saying that you can't know that as a legit player is somewhat true but it completely ignores the context of what was happening at that moment. I simply flicked away because the spy went around cover and it just so happened that the last bullet before I flicked killed him. You might argue that I locked onto another enemy but my aim flicks onto the middle of base cliff and pocket. It is impossible for an enemy to be standing on the other side there.
Addressing the clip Adje sent - https://www.youtube.com/watch?v=c6aejYlUsIU
I don't have this demo but I remember when this clip was posted. My medic got backstabbed and yelled, so I flicked towards where my medic was and my crosshair landed almost exactly on the spy(With some micro correction). You could say its a cheat but look at the amount of times I make the same flicking motion onto pure air. In case its related to me being aware of that scout, I vaguely remember him being called and you can confirm that by looking at my demo shooting there. (There isn't even a log of this game lol)
And lastly addressing the funniest one of all, the double milka bar -https://www.youtube.com/watch?v=dq1BDE9c2Mw.
I knew about this glitch and did it because it was a scrim and because the mini pack was missing to refill it. From what I remember I never ever did this anywhere else. You can make the argument that its a d*ck move to use silly bugs like this in scrims but tell me, how many times have people used double demoman on steel to hold A and B at the same time? How many times have snipers intentionally cornersniped in scrims? How many times have people offclassed to engineer to speed up the building process of the main engineer's buildings in setup? You are severely overreacting if you think eating a second chocolate impacted that scrim in any negative way.