Its usually happening when teamfights occur so I been box selecting my hero again quickly but i think it just deselects my hero not sure 100 percent ill try to pay more attention next time it happens
https://entgaming.net/findstats.php?id=12256907
a game where it happened I even said it in chat at around 28 minutes elapsed time as earthspirit
Remaining known DotA 6.83d bugs
- Hunter91
- Treant
- Posts: 432
- Joined: Sat Jun 16, 2012 1:27 am
- Has thanked: 5 times
- Been thanked: 11 times
Re: Remaining known DotA 6.83d bugs
h3rmit wrote:That's... very weird. Nothing in relation to unit control should have been affected. All changes, including Lanaya were very specific and very limited, and none of them had any distant relation to unit control.
How would you describe this "loss of control"? What is it that you're experiencing?
Also, I should clarify the following: Warcraft III is actually a "turn-based" game. In each turn, each player can choose to do one action, or pass. Afaik, the bot latency is currently set to 100ms. Meaning that each "turn" has a duration of 100ms, and you're allowed to send up to 10 actions per second. Issuing more than one command in the same turn results in overwritting the previous one.
What you see on your screen is a playback of your past actions, after you send them to the bot, the turn ends, the bot publishes what actions were taken by everyone, and you receive them. The playback of your actions starts then.
Is there any chance that you're temporarily exceeding the allowed 600 apm?
P.S.: The only other possible explanation I can think of is that some mysterious and undocumented bug or limitation of WC3 1.30.1 was triggered by recent changes.
We could verify if it's latency related or not, by testing the map on a bot with a very low latency (e.g. 20ms) that can fully cover your high apm, if your ping can afford it.
I think it is due to a few skills that cause this including Astral Imprisonment from Obsidian Destroyer.
- h3rmit
- Armored Tree
- Posts: 60
- Joined: Sat Aug 27, 2016 12:15 am
- Has thanked: 4 times
- Been thanked: 54 times
Re: Remaining known DotA 6.83d bugs
Frank wrote:Its usually happening when teamfights occur so I been box selecting my hero again quickly but i think it just deselects my hero not sure 100 percent ill try to pay more attention next time it happens
https://entgaming.net/findstats.php?id=12256907
a game where it happened I even said it in chat at around 28 minutes elapsed time as earthspirit
Thanks for the detailed info! I watched that teamfight, been 27:00 and 28:00 in slow motion. Indeed, your hero gets deselected 3 times!

It's certainly not related to latency. It's right there, recorded in the replay and played all the same in everyone's Warcraft III.
I somehow need to find a way inspect the replay actions... DotaReplayManager doesn't seem to load WC3 1.30.1 replays.
-
- Treant
- Posts: 254
- Joined: Sun Sep 15, 2019 8:24 pm
- Has thanked: 51 times
- Been thanked: 64 times
Re: Remaining known DotA 6.83d bugs
Should be possible (and maybe even easy) to write a tool to parse replay actions based on this: http://w3g.deepnode.de/files/w3g_format.txt
I don't know if it will actually provide any valuable info though. It likely comes across as a 0x02 (Deselect) in the replay which wouldn't really explain anything. I think triggered deselects just look like deselects.
I don't know if it will actually provide any valuable info though. It likely comes across as a 0x02 (Deselect) in the replay which wouldn't really explain anything. I think triggered deselects just look like deselects.
Return to “Defense of the Ancients”
Who is online
Users browsing this forum: No registered users and 78 guests