Cheating Look-Fors

[PartylikeVader]

Greetings All!

Numerous reports of increased auto-win hacking have come up recently within the Star Wars Commander community. One of my squad members fell victim to this hack and provided footage and insight. Attached is a gameplay review of this hack. The video link below shows the hack in action with some player commentary. A special thank you goes to 000 for providing this information and commentary:

Cheating Look-Fors: Auto-Win Hack

Lich defense - auto win hack - 000 - 4.29.18.png

Lich Revenge - 000 - 4.29.18.png

The defense screenshot displays a key indicator that a hack took place as it is RNG (random number generated) impossible to use the loadout shown on the base to achieve 100%. This player Lich of Dota2Fighters is using an Auto-Win Hack.

Replay Glitch vs. Auto-Win Hack
The difference between the replay glitch and the Auto-Win Hack comes is seen from their definitions. The replay glitch is a discrepancy in what a player sees in a replay versus what actually happened, as replays are simulations/reconstructions of the attack and may inherit inaccuracy. Replay glitches do not misrepresent what troops used in the attack, but rather misrepresents how those troops were used and behaved.

Some players will observe that their replay showed their opponent earning ~35% on their base, but the replay shows a 100% defeat, these replays usually reflect "reasonable" loadouts that had the potential to level their base. This is typically a result of the replay glitch.

Other players notice their base suffering a <10% attack with a handful of weak 1 or 2 UC troops that results in a 100% defeat. These replays are typically very short and the loadouts used are impossible to earn the reflected 100%.

A key factor in differentiating between the Replay Glitch and the Auto-Win Hack is the troops used. This helps assess if the replay simulation is impossible with RNG (hack) versus possible (glitch).

Reporting:
Players should be wisely skeptical on replays pertaining to Auto-Win Hacking versus Replay Glitch. Misrepresentation is counterproductive to the game and wastes time the developers use to conduct investigations.
Commanders should be informed on how to review evidence in making the determination to file a report to Disney. Prompt reporting as well as giving date/time is essential to expedite the investigation and ensure a consequence is given. Many players write ambiguous, low evidence tickets to Disney support that result in difficulty performing a thorough investigation. Specific information helps the development track a player even if they are not in a squad.

Please continue to use this thread for additional "look-fors" to known cheats and hacks such as the Auto-Win Hack.

May the Force Be With You.

[mkenobi]

Replay Glitches and Cheaters exist since the very beginning of the game... Disney knows about Replay Glitch but they never were able to fix that. Support always says to not trust on Replays but only in what Battle Log shows, what generate doubts and distrust in many players everytime a rival loses an attack in the Replay but the Battle Log shows that he had a victory.

I remember of doing some Replay Glitches on Windows as Rebel level 6 against Imperial levels 9, after got a CNFO and got stucked on the last rival base. If I started the attack, Dekas got frozen and traps didn't work, what generated a Replay totally different from the real attack. While I had the advantage, I could get the victory by 1, maybe 2 stars, but the Replay showed a defeat because it was created on what could have been the attack if wasn't the glitch...

In doubt, watch the Replay 2, 3, 4 times and maybe you can see a few differences in each repetition for the same attack. And see if the troops the attacker used in the Replay ARE of the same kind and number as showed in the Battle Log. If not, something is really wrong.

In this case (see my complete post here), the attacker used only a few scouters to win over my HQ9 base, and if according to Support the Battle Log is always right, if this wasn't a hack, I don't know what can be:

[FruitBowlMafia]

Greetings All!

Numerous reports of increased auto-win hacking have come up recently within the Star Wars Commander community. One of my squad members fell victim to this hack and provided footage and insight. Attached is a gameplay review of this hack. The video link below shows the hack in action with some player commentary. A special thank you goes to 000 for providing this information and commentary:

Cheating Look-Fors: Auto-Win Hack

Lich defense - auto win hack - 000 - 4.29.18.png

Lich Revenge - 000 - 4.29.18.png

The defense screenshot displays a key indicator that a hack took place as it is RNG (random number generated) impossible to use the loadout shown on the base to achieve 100%. This player Lich of Dota2Fighters is using an Auto-Win Hack.

Replay Glitch vs. Auto-Win Hack
The difference between the replay glitch and the Auto-Win Hack comes is seen from their definitions. The replay glitch is a discrepancy in what a player sees in a replay versus what actually happened, as replays are simulations/reconstructions of the attack and may inherit inaccuracy. Replay glitches do not misrepresent what troops used in the attack, but rather misrepresents how those troops were used and behaved.

Some players will observe that their replay showed their opponent earning ~35% on their base, but the replay shows a 100% defeat, these replays usually reflect "reasonable" loadouts that had the potential to level their base. This is typically a result of the replay glitch.

Other players notice their base suffering a <10% attack with a handful of weak 1 or 2 UC troops that results in a 100% defeat. These replays are typically very short and the loadouts used are impossible to earn the reflected 100%.

A key factor in differentiating between the Replay Glitch and the Auto-Win Hack is the troops used. This helps assess if the replay simulation is impossible with RNG (hack) versus possible (glitch).

Reporting:
Players should be wisely skeptical on replays pertaining to Auto-Win Hacking versus Replay Glitch. Misrepresentation is counterproductive to the game and wastes time the developers use to conduct investigations.
Commanders should be informed on how to review evidence in making the determination to file a report to Disney. Prompt reporting as well as giving date/time is essential to expedite the investigation and ensure a consequence is given. Many players write ambiguous, low evidence tickets to Disney support that result in difficulty performing a thorough investigation. Specific information helps the development track a player even if they are not in a squad.

Please continue to use this thread for additional "look-fors" to known cheats and hacks such as the Auto-Win Hack.

May the Force Be With You.

As much as I hate players using Game Trainers to disable enemy turrets... They do less damage to the player base than the PLV automation squad.

You sir have vacated your right to accuse anyone of cheating in any manner.

[Forceisweaknyou]

Greetings All!

Numerous reports of increased auto-win hacking have come up recently within the Star Wars Commander community. One of my squad members fell victim to this hack and provided footage and insight. Attached is a gameplay review of this hack. The video link below shows the hack in action with some player commentary. A special thank you goes to 000 for providing this information and commentary:

Cheating Look-Fors: Auto-Win Hack

Lich defense - auto win hack - 000 - 4.29.18.png

Lich Revenge - 000 - 4.29.18.png

The defense screenshot displays a key indicator that a hack took place as it is RNG (random number generated) impossible to use the loadout shown on the base to achieve 100%. This player Lich of Dota2Fighters is using an Auto-Win Hack.

Replay Glitch vs. Auto-Win Hack
The difference between the replay glitch and the Auto-Win Hack comes is seen from their definitions. The replay glitch is a discrepancy in what a player sees in a replay versus what actually happened, as replays are simulations/reconstructions of the attack and may inherit inaccuracy. Replay glitches do not misrepresent what troops used in the attack, but rather misrepresents how those troops were used and behaved.

Some players will observe that their replay showed their opponent earning ~35% on their base, but the replay shows a 100% defeat, these replays usually reflect "reasonable" loadouts that had the potential to level their base. This is typically a result of the replay glitch.

Other players notice their base suffering a <10% attack with a handful of weak 1 or 2 UC troops that results in a 100% defeat. These replays are typically very short and the loadouts used are impossible to earn the reflected 100%.

A key factor in differentiating between the Replay Glitch and the Auto-Win Hack is the troops used. This helps assess if the replay simulation is impossible with RNG (hack) versus possible (glitch).

Reporting:
Players should be wisely skeptical on replays pertaining to Auto-Win Hacking versus Replay Glitch. Misrepresentation is counterproductive to the game and wastes time the developers use to conduct investigations.
Commanders should be informed on how to review evidence in making the determination to file a report to Disney. Prompt reporting as well as giving date/time is essential to expedite the investigation and ensure a consequence is given. Many players write ambiguous, low evidence tickets to Disney support that result in difficulty performing a thorough investigation. Specific information helps the development track a player even if they are not in a squad.

Please continue to use this thread for additional "look-fors" to known cheats and hacks such as the Auto-Win Hack.

May the Force Be With You.

As much as I hate players using Game Trainers to disable enemy turrets... They do less damage to the player base than the PLV automation squad.

You sir have vacated your right to accuse anyone of cheating in any manner.

+1000

[Harshit]

Greetings All!

Numerous reports of increased auto-win hacking have come up recently within the Star Wars Commander community. One of my squad members fell victim to this hack and provided footage and insight. Attached is a gameplay review of this hack. The video link below shows the hack in action with some player commentary. A special thank you goes to 000 for providing this information and commentary:

Cheating Look-Fors: Auto-Win Hack

Lich defense - auto win hack - 000 - 4.29.18.png

Lich Revenge - 000 - 4.29.18.png

The defense screenshot displays a key indicator that a hack took place as it is RNG (random number generated) impossible to use the loadout shown on the base to achieve 100%. This player Lich of Dota2Fighters is using an Auto-Win Hack.

Replay Glitch vs. Auto-Win Hack
The difference between the replay glitch and the Auto-Win Hack comes is seen from their definitions. The replay glitch is a discrepancy in what a player sees in a replay versus what actually happened, as replays are simulations/reconstructions of the attack and may inherit inaccuracy. Replay glitches do not misrepresent what troops used in the attack, but rather misrepresents how those troops were used and behaved.

Some players will observe that their replay showed their opponent earning ~35% on their base, but the replay shows a 100% defeat, these replays usually reflect "reasonable" loadouts that had the potential to level their base. This is typically a result of the replay glitch.

Other players notice their base suffering a <10% attack with a handful of weak 1 or 2 UC troops that results in a 100% defeat. These replays are typically very short and the loadouts used are impossible to earn the reflected 100%.

A key factor in differentiating between the Replay Glitch and the Auto-Win Hack is the troops used. This helps assess if the replay simulation is impossible with RNG (hack) versus possible (glitch).

Reporting:
Players should be wisely skeptical on replays pertaining to Auto-Win Hacking versus Replay Glitch. Misrepresentation is counterproductive to the game and wastes time the developers use to conduct investigations.
Commanders should be informed on how to review evidence in making the determination to file a report to Disney. Prompt reporting as well as giving date/time is essential to expedite the investigation and ensure a consequence is given. Many players write ambiguous, low evidence tickets to Disney support that result in difficulty performing a thorough investigation. Specific information helps the development track a player even if they are not in a squad.

Please continue to use this thread for additional "look-fors" to known cheats and hacks such as the Auto-Win Hack.

May the Force Be With You.

+100 Agreed

[erfs]

At the risk of sounding ignorant - what are game trainers and what do you mean by "automation squad" ? Scripts that keep players online non-stop and automatically run attacks ?

[bob1084]

Greetings All!

Numerous reports of increased auto-win hacking have come up recently within the Star Wars Commander community. One of my squad members fell victim to this hack and provided footage and insight. Attached is a gameplay review of this hack. The video link below shows the hack in action with some player commentary. A special thank you goes to 000 for providing this information and commentary:

Cheating Look-Fors: Auto-Win Hack

Lich defense - auto win hack - 000 - 4.29.18.png

Lich Revenge - 000 - 4.29.18.png

The defense screenshot displays a key indicator that a hack took place as it is RNG (random number generated) impossible to use the loadout shown on the base to achieve 100%. This player Lich of Dota2Fighters is using an Auto-Win Hack.

Replay Glitch vs. Auto-Win Hack
The difference between the replay glitch and the Auto-Win Hack comes is seen from their definitions. The replay glitch is a discrepancy in what a player sees in a replay versus what actually happened, as replays are simulations/reconstructions of the attack and may inherit inaccuracy. Replay glitches do not misrepresent what troops used in the attack, but rather misrepresents how those troops were used and behaved.

Some players will observe that their replay showed their opponent earning ~35% on their base, but the replay shows a 100% defeat, these replays usually reflect "reasonable" loadouts that had the potential to level their base. This is typically a result of the replay glitch.

Other players notice their base suffering a <10% attack with a handful of weak 1 or 2 UC troops that results in a 100% defeat. These replays are typically very short and the loadouts used are impossible to earn the reflected 100%.

A key factor in differentiating between the Replay Glitch and the Auto-Win Hack is the troops used. This helps assess if the replay simulation is impossible with RNG (hack) versus possible (glitch).

Reporting:
Players should be wisely skeptical on replays pertaining to Auto-Win Hacking versus Replay Glitch. Misrepresentation is counterproductive to the game and wastes time the developers use to conduct investigations.
Commanders should be informed on how to review evidence in making the determination to file a report to Disney. Prompt reporting as well as giving date/time is essential to expedite the investigation and ensure a consequence is given. Many players write ambiguous, low evidence tickets to Disney support that result in difficulty performing a thorough investigation. Specific information helps the development track a player even if they are not in a squad.

Please continue to use this thread for additional "look-fors" to known cheats and hacks such as the Auto-Win Hack.

May the Force Be With You.

This is so much like a distant memory I have about being pardoned 2 min too late on death row. It def is like rain that would be on your wedding day. What if you didn’t have to pay for a ride that was already free? What if you got really good advise about something but just didn’t take it? Traffic jam when you’re already late, a no smoking sign when I am on my cigarette break... thank you PLM, I needed a good little chuckle.