Cheat Report

[wsk]

Hello everybody,

This is actually my first post in this forum, althought I´m an old supcom fan & player and just started playing on FAForever for this summer.
I´ve never had any problems with cheating on supcom but I think this might be the case:

It´s a 2 vs 2 game in Daroza´s Sanctuary (replay: id=1143168) starting today at 0:16 between my friend mitor & myself(wsk) vs. Popsniper (the possible cheater) & Wiza.

Everything was going OK for us when it happened (14th minute aprox.) that Popsniper wrote a gg. Suddenly with no aparent reason (no ctrl+k at all, the commander wasn´t even selected for me) my ACU exploded. Afterwards Popsniper exploded too. This is really strange since there was no tactics or snipes on the other team and mitor had omni.

I don´t really mind the result of the game (which continued and was lost and probably wouldn´t have been lost otherwise). I just find this extremely annoying on my gaming experience. You can see the replay here

Greetings!

[Astrofoo]

Well I think the best thing you can do is to remove the player's names from your post and instead PM a moderator with the information so he can take action if it is cheating.

[BRNKoINSANITY]

It looks like you CTL-K'd..... there was a countdown and everything. It appears that the other guy was already quitting and threw out the GG, and somehow you triggered CTL-K at that moment. Don't feel bad, I think that at some point most everyone around here has CTL-K'd their com on accident one way or another.

[Nombringer]

It looks like you CTL-K'd..... there was a countdown and everything. It appears that the other guy was already quitting and threw out the GG, and somehow you triggered CTL-K at that moment. Don't feel bad, I think that at some point most everyone around here has CTL-K'd their com on accident one way or another.

Been there done that.... :L

[Mr-Smith]

I dont know what game you played but when cheats are enabled its possible ctrl+k any unit even those from the enemy.

[wsk]

I dont know what game you played but when cheats are enabled its possible ctrl+k any unit even those from the enemy.

For sure it was a rated game so I guess cheats were disabled and, seriously, I´ll put my hand on the fire I din´t ctrl+k at all and less to do it exactly when he sais "gg"... Indeed my commander was patrolling to recover mass, I didn´t have him selected. There´s almost no possibility that all this would happen at the same time, there were too many coincidences in my opinion to be classified as a mistake on my side: we winning, he saying gg, my commander starting countdown at the same time, afterwards he doing same to avoid any issue...

[ColonelSheppard]

For sure it was a rated game so I guess cheats were disabled and, seriously, I´ll put my hand on the fire I din´t ctrl+k at all and less to do it exactly when he sais "gg"... Indeed my commander was patrolling to recover mass, I didn´t have him selected. There´s almost no possibility that all this would happen at the same time, there were too many coincidences in my opinion to be classified as a mistake on my side: we winning, he saying gg, my commander starting countdown at the same time, afterwards he doing same to avoid any issue...

see, nobody would be so stupid to write gg in the moment he cheats, that would be so incredible silly, you accidently crtl-k, can happen.. get the crtl-k-confirm mod

[SC-Account]

Can't start replay...

[Hawkei]

Ctrl + K is very easy to do by accident. Because it is possible you may have gone to select all land, which is Ctrl +L, and only one key apart. It is also possible that the "gg" of the other player could have been intended as a sign of defeat. It could have been that you killed yourself in the very moment of victory.

I've done it before too. It does happen.

[Plasma_Wolf]

The replay can't be loaded, but I've seen this situation before. The same complaint, there hadn't even been exchange in fire yet and the killed player immediately accused his direct opponent (Isis) of cheating. I checked the replay and he had a countdown, pressed ctrl+k instead of ctrl+l. The same thing probably happened here.