KillerFrost - aimlock/f1

[Kody]

Player Nick: =F2=Killer_Frost
Date:
Reason for reporting: Aimlock/F1 or something like devilkiller
Evidence:(Screenshots, videos..etc) 
Extra notes:Major flicks at 0:03, 0;08, 0:14.. you can see in whole video, his aim was flicking soo fast to heads. +  i was shooting his head continously and he was not getting my shots. You can watch video in slow motion to watch the aim flick carefully.. Also he was not getting my shots maybe head1 or idk

[Killer frost^]

Ok wait

[Killer frost^]

[Decent_946]

It more looks like lag/warp/fps difference. It'd have been more better if I could see the ping of both.

anyways, If it was aimlock, In your video you are standing near to him more than other players. Aimlock would have 1st aimed at you without pointing at other players. Which is not the case here.

for the headshot not being made, It could be because of difference of FPS (on/off). But maybe due to widescreen fix. I'll let other admins / seniors to have a look at this video before I make final decission.
@Aaron , @Lederhos , @DiaZ , @KX  - Please have a review.

[Killer frost^]

Well to be honest let me clear out everything.
First of all i dont have any hacking history you can go through my channel and can watch the video in my channel.I srsly dont use any sort of hacks nor anyother tools.
I have got some good skills tho.So these type of headshots can be easily made by anyone.
About flicks i did that intentionally.You can try it yourself anyways i do have more proofs and i can provide it if its needed.
About lagg it was my pings spiking i can show that too.

[Kody]

I'll give you the logs of that time when i used /fps and /ping

[Decent_946]

After discussing privately about the report, we have decided to add killer frost in our watch list. As the video provided by killer frost satisfies his argument. The only thing putting hindrance is the aim at head. In your video you are aiming at head while in his video we can see bullets passing near by head. It could possibly be due to FPS/jttr/ping/latency issue as well. Or maybe not.

Added to watchlist.

Thanks for reporting.