Quote from monsieur Kaivax in the patch notes.
Video proof of how its still not fixed:
xhttps://drive.google.com/file/d/1Yh2hzWtTmz6ckKxKuQSOv-HURSs-0d8N/view?usp=sharing
The link opens a video uploaded to my Giggle Droves account.
Just exclude the starting X when copying.
Thanks in advance.
There is an inaccuracy in your video. On my computer, whenever I use Battle.net App to do an update to a new version of Warcraft III, typically I always copy the game first so that I can keep a backup of the previous version. Since each install is 26-30 GB, obviously I am using 100s and 100s of gigabytes for this, but it gives me the ability to launch previous game versions and compare against them.
Just now, to help review this bug, I launched the last version of patch 1.32 – which was the 1.32.10.18820 from 2022 – and that version DID NOT have the bug that you are demonstrating in your attached video. So the video says the problem is from 1.32 – and broadly the version number 1.32 was used from 2019 until 2022 for all of the Reforged versions made during those years – but none of those versions have the bug.
I think it is worth pointing this out, that in a certain way of thinking there was a functional Reforged client with functional systems, and it was the new people, maybe PlaySide studios, maybe Microsoft who have lower attention to detail and who published changes that caused this bug without testing and it is NOT in fact a bug that existed on all of Reforged that you are pointing out in your attachment.
So, if I were the author of your video, I would have specifically noted that the old bug started in 1.33 and not in 1.32, even though as you identified it appears that recent patches are making this bug even worse and making the technology systems even less stable.