[LTD] MadRobot europe

[Keelay]

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.

[Unitil]

Below is what I've found while reviewing the chat logs and DRM for the claim mentioned above.

MadRobot@Europe.battle.net
Intentional Desync

Spoiler!

Chat logs leading up to and including the desync

Code: Select all

(27:28 / Allied) MadRobot: fk me
(27:37 / Allied) Marshall: why did u do that?
(27:41 / Allied) MadRobot: those were some shit rolls
(27:44 / Allied) Marshall: -rolls
(27:51 / Allied) Marshall: just dont build geomancer
(27:55 / Allied) MadRobot: lul
(27:57 / Allied) Marshall: oj gets dropped if u do
(28:08 / Allied) MadRobot: really?
(28:10 / Allied) Marshall: y
(28:19 / Allied) MadRobot: sweet im doing it
(28:23 / Allied) Marshall: once clockwreck uses skill, oj gets desynced
|
|
|
(29:54 / Allied) Marshall: the geomancer bug is known and is currently being addressed btw
(30:05 / Allied) MadRobot: im doing it
(31:56 / Allied) MadRobot: i got desync for oj
(32:18 / Allied) MadRobot: nope dosnt work
(32:43 / Allied) MadRobot: u lied to me teal
(32:59 / Allied) Marshall: told not to do it
(33:00 / Allied) Marshall: lol
(33:25 / Allied) MadRobot: why not its didnt desync him
(33:26 / Allied) Marshall: hopefully they fixed it
(34:07 / All) SonOfABokChoy: Warning! Desync detected!
(34:07 / All) SonOfABokChoy: Players in game state #1: SonOfABokChoy, savagex, Marshall, MadRobot, zephenrique, LaBrother, Legacy403
(34:07 / All) SonOfABokChoy: Players in game state #2: alorias
(34:07 / All) SonOfABokChoy: alorias was dropped due to desync.
(34:07 / QUIT) alorias: Left
(34:14 / Allied) Marshall: TOLD YOU
(34:14 / Allied) MadRobot: HAHA
(34:23 / Allied) MadRobot: IT DID WORK
(36:33 / Allied) MadRobot: im such a dick
(36:57 / Allied) MadRobot: his fault for buying a mac

Action Log of building a Geomancer/Clockwreck being built:

Code: Select all

 31:30 <MadRobot> 0x11: Point order: [Geomancer] (X: -832.00, Y: 1856.00, flags: 0x0004)
 31:33 <MadRobot> 0x19: Select subgroup: [Geomancer], 0x0019563A00046777
 31:38 <MadRobot> 0x10: Immediate order: [Clockwreck] (flags: 0x0040)

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]

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

[Unitil]

@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.

[Jabba41]

Madrobot banned 5 days.

[FalenGa]

No definite dodge. Processing.