SATVIK, during CS Rank play, spotted suspected hacks like wall-penetrating attacks and abnormal movement, and analyzed the situation across servers.
During continuous engagements, a situation occurred where shots seemed to come from beyond a wall, raising the possibility of the opponent using hacks.
SATVIK closely watched to see if the opponent was using a 'wallshot' hack, which causes damage through walls.
It was determined that due to the nature of CS Rank games, abnormal play could occur at any time.
The opponent showed threatening gameplay by knocking down three players consecutively, raising the possibility of hack usage.
Teammates were instructed to play cautiously rather than rushing in, judging the opponent's movements to be excessively accurate.
An attempt was made to distinguish between the opponent's play, which consistently landed headshots, and actual hack usage or simply being 'good'.
They got three knocks. Can we not check if something is wrong? Are they just good? They're only hitting headshots, be careful.
In the next match, they encountered an opposing team named 'SD क्यूट बॉय', whose average rank was displayed as 'Elite Master'.
This was presumed to be Grand Master rank in reality, due to the game system's highest rank display limit.
The opposing team showed powerful performance, knocking down three players using the M10 shotgun.
When the opponent was seen passing through walls or moving and attacking abnormally fast, hack usage was immediately suspected.
Teammates clearly identified the player as a 'hacker', concluding they were using unauthorized programs rather than normal gameplay.
SATVIK confirmed the situation as a hack upon witnessing it.
Numerous unexpected hack users appeared during CS Rank games, causing chaos. Unlike the normal first two matches, abnormal players sharply increased afterward, and some were strategically responding to maintain their winning streaks.
Despite previous news that all hackers were banned, it was confirmed that abnormal players still existed.
Players had to devise strategic countermeasures against hackers to protect their current winning streaks.
To avoid breaking the current winning streak, it was decided that all four teammates would stick together as a strategy.
To counter the hacker's rapid movement speed, they primarily moved inside buildings, adopting a defensive posture.
A cooperative tactic was employed where if one person was attacked, another teammate would immediately provide support, aiming to nullify the hacker's attacks.
After achieving a 4-game winning streak on the Indian server, the game was concluded. The plan was then to move to the Bangladesh and Nepal servers to check the CS Rank environment there.
It was planned to verify whether unfair players would appear in CS Rank on other servers as well.
After moving to another server, CS Rank games were started with random matchmaking due to account issues with existing friends.
During this process, mistakes in game settings occurred, such as forgetting the backpack hide setting.
The game proceeded with two randomly joined teammates.
The player experienced difficulties in communication due to microphone noise and sound issues.
SATVIK went through a process of checking whether he was a normal player, a hacker, or an abnormal user.
Questions arose about whether the opposing team was legitimately skilled or using hacks.
With an ongoing 11-game winning streak and a goal of 5 additional wins, the importance of winning or losing increased.
Concerns about fairness deepened as the opponent's movements were judged to be beyond the normal range.
An opposing player appeared, consistently landing headshots with an AWM (sniper rifle).
Immediate headshot firing without an aiming process was observed, raising suspicions of aim hack usage.
Abnormal mobility was also detected, suggesting the possibility of speed hack usage.
SATVIK concluded the situation was a hack and heightened his vigilance.
Upon moving to the Brazil server, our team's rank was all Bronze, while the opposing team was Master rank.
A problem occurred where network ping soared to 300ms, making normal gameplay difficult.
SATVIK questioned why his ping was 300ms, 100ms higher than his opponent's.
It was recognized that the opposing team encountered on the Brazil server was in the process of ranking up.
SATVIK decided not to necessarily win, out of concern that the opponent's rank would drop due to a loss.
As part of video production, instead of forcing a victory, the play style was shifted to help the opponent's rank push.
Initially, there was a resolve to eliminate hackers and win, but on the Brazil server, the stance changed.
It was decided to intentionally lose so that the opponent's rank would not drop, joking that it was essentially providing a 'free rank push service'.
SATVIK played to intentionally lose to help with the rank push.
It is necessary to check through the next game whether a comfortable environment will be maintained.
SATVIK decided to further verify if the relatively comfortable game environment would continue in the next game.
He gave a positive assessment of the comparatively fair game environment.
To determine hack usage, they aimed to test whether the opponent's shots could penetrate a Gloo Wall. All teammates gathered densely inside a Gloo Wall to verify if it was truly penetrated.
This tactic was to clearly determine hack status by testing if the opponent's shots penetrated the Gloo Wall.
All members gathered within one defensive barrier to induce abnormal attacks from a hacker and secure evidence.
Answers come from the transcript, with the exact spot cited.
Want the next article from SATVIK?
When SATVIK publishes, we'll write it up like the one you just read and email it to you.
