Replay Link: https://entgaming.net/findstats.php?id=9602215
Game Name: Legion TD Mega #93
Your Warcraft III Username: Marshall
Violator's Warcraft III Username: Madrobot
Violated Rule(s): Taking advantage of Bug with malicious intent
Time of Violation (in-game or replay): lvl 15/16
Any further thoughts: All players were warned that clockwreck desyncs players, purple built it intending to drop the player. Player dropped at beginning of lvl 16.
[LTD] MadRobot europe
Moderator: ENT Staff
-
- Oversight Staff
- Posts: 5133
- Joined: Mon Mar 20, 2017 5:56 am
- Location: Canada
- Been thanked: 113 times
Re: [LTD] MadRobot europe
Below is what I've found while reviewing the chat logs and DRM for the claim mentioned above.
MadRobot@Europe.battle.net
Intentional Desync
Concluding Thoughts
MadRobot@Europe.battle.net
Easy to see malicious intent in the chat logs alone
Rules Broken this Game:
@Keelay
If you run into anyone else that shows signs of intentionally trying to break any rules or exploiting potential glitches, you should initiate a votekick on the individual as to avoid situations similar to this. I believe there was a good amount of indication in chat and also time available between him building the unit and the two waves of it being on the playing field to explain the situation with a votekick or get him to sell the unit.
I understand that sometimes in the midst of a game it can be hard to track some of these things, however, if you're able to see these sort of signs in the future it'd be best to kick someone like MadRobot before anything occurred.
MadRobot@Europe.battle.net
Intentional Desync
Spoiler!
Concluding Thoughts
MadRobot@Europe.battle.net
Easy to see malicious intent in the chat logs alone
Rules Broken this Game:
Code: Select all
MadRobot@Europe.battle.net
• Do not ruin the game on purpose: Do not purposely glitch or exploit the game
@Keelay
If you run into anyone else that shows signs of intentionally trying to break any rules or exploiting potential glitches, you should initiate a votekick on the individual as to avoid situations similar to this. I believe there was a good amount of indication in chat and also time available between him building the unit and the two waves of it being on the playing field to explain the situation with a votekick or get him to sell the unit.
I understand that sometimes in the midst of a game it can be hard to track some of these things, however, if you're able to see these sort of signs in the future it'd be best to kick someone like MadRobot before anything occurred.
- Indrial
- Treant
- Posts: 328
- Joined: Wed Nov 05, 2014 5:16 pm
- Has thanked: 6 times
- Been thanked: 1 time
Re: [LTD] MadRobot europe
Wondering why isnt it fixed when even random mega players know about that.
Or why isnt hosted any other version of ltd meanwhile it is fixing.
Welcome to ENt gaming i guess.
Ps: For example i didnt know it
Or why isnt hosted any other version of ltd meanwhile it is fixing.
Welcome to ENt gaming i guess.
Ps: For example i didnt know it
-
- Oversight Staff
- Posts: 5133
- Joined: Mon Mar 20, 2017 5:56 am
- Location: Canada
- Been thanked: 113 times
Re: [LTD] MadRobot europe
@Indrial
Currently the issue of Mac players desyncing is known to broud3r who works on this game, and he made a statement HERE saying that he will work on resolving the issue. Debugging code can take time, and most people within the Warcraft III community do things within the community during their spare time. I'm sure broud3r will eventually find the issue within the game code that is causing the desync, however, for now we need to make sure issues such as what was reported above is avoided in general until the issue is patched.
Currently the issue of Mac players desyncing is known to broud3r who works on this game, and he made a statement HERE saying that he will work on resolving the issue. Debugging code can take time, and most people within the Warcraft III community do things within the community during their spare time. I'm sure broud3r will eventually find the issue within the game code that is causing the desync, however, for now we need to make sure issues such as what was reported above is avoided in general until the issue is patched.
Return to “Processed Requests”
Who is online
Users browsing this forum: Google [Bot] and 42 guests