Dear Blizzard devs, I want thank you again for fixing the bugs in the last live patch 2.03 (Fix these bugs in next patch (All fixed in 2.0.3) - General Discussion - Warcraft III: Reforged Forums). As long as you got some staffs really working on this long beloved game, I hope you can look into and fix these bugs in the incoming patch:
- “MalFurionNoStag” rides a deer. (#3)
Details
units\nightelf\MalFurion\MalFurionNoStag was a standing Mal’Furion model, but after Reforged, it is merged with units\nightelf\MalFurion\MalFurion which is a rider Mal’Furion. Even classic graphic mode is affected. Please give us back the standing Mal’Furion, at least in classic mode. Fixing this will not harm the lore. You can use units\nightelf\MalFurion\MalFurion in campaign instead.
- Low multi-board performance on non-English versions (#7)
Details
In some non-English (e.g. Chinese) game client, when in game and you open the Multiboard the first time, the game will got freeze for a while. If the multiboard has a lot of rows and columns, the “while” can be longer than you could imagine. I remember a Reforged patch changes the typography or something related, which might cause this bug.
- Low performance for TriggerRegisterTimerEvent (#9)
Details
I know that there was an intentional change in 1.32.10 to change the limit of timer event to 100 times per second. As is observed by a HIVE user, TimerStart runs at the old frequency but TriggerRegisterTimerEvent is limited to 100Hz. We all know that many custom maps use 0 second timer to run some immediate async code, so a 0.01s time gap is unacceptable! For 5 years, this has been affecting maps that use TriggerRegisterTimerEvent for zero second timer events. I suggest you make an exception for 0 seconds timer events (i.e. TriggerRegisterTimerEvent(t,0,false)), to make it run at the original speed.