[2.0.1.22498] Suggested adjustments and fixes list

General Discussion
1

Suggested adjustments and fixes list for the next revision:

  1. Whenever I or my friends enter a battle or custom game, my Blizzard BNet account status will be forced to change to busy, but I and my friends have not changed our game account status to busy! Not knowing what game each other is playing hinders our communication of game invitations! (The status of the game account should not be modified without the player’s consent)

  2. Whenever a custom game room is created and then closed, or whenever a custom game ends, the chat list on the right side of the multiplayer Warcraft III general channel sometimes jumps to the clan chat channel. Create the illusion that other online players in the chat list have disappeared! When this happens, you need to manually adjust back to the Warcraft III general channel to see other online players!

  3. In the multiplayer Warcraft III general channel or custom game room, press ALT+TAB to switch windows and use the Blizzard BNet platform to whisper to other friends. Sometimes the ID displayed is incorrect and not the same person! (For example, if I whisper to player A, it will show that I am whispering to player B)

  4. Unable to set hotkeys to F6, F7
    (F1/F2/F3/F4/F5/F8 can be set as hotkeys)

  5. After you modify the numeric hotkey shortcut, clicking the numeric keys on the right side of the keyboard will be completely ineffective. You can only click the modified hotkey shortcut or click with the mouse!
    (Example: W3Champions’ WIH.v1.1.1.w3c hotkey modification program. After modifying the hotkey, the number keys on the right side of the keyboard can still be clicked and used effectively! It should be usable by both!)

  6. New Skins can be activated in my options, but the localization’s are missing, it shows VER2_SKIN_46_NAME and VER2_SKIN_47_NAME and VER2_SKIN_48_DESC

  7. [L:OPTION_ XXXX_XXXX] The language text represented by this type of check setting in the options is not correctly translated into localized Traditional Chinese.

Traditional Chinese Localization bugged - it shows:

[L:OPTION_CLASSIC_SOUND]
[L:OPTION_CLASSIC_CURSOR]
[L:OPTION_PEON_DOUBLETAP_FOCUS]
[L:OPTION_OLD_TERRAIN]
[L:OPTION_GAME_INFO_MESSAGES]
Options - Hotkeys - General F keys [L:OPTION_HOTKEYS_…SELECTOR_1~3] The text is blocked by the four race and neutral buttons.
(Because the view is blocked, the complete text description of the option cannot be seen)

None of the above options are correct local Chinese translation naming representations.
(Not translated into local Traditional Chinese)

PC (Windows 10) User, CPU i7-8700K, RAM 32GB , Classic/Reforged Key Owner, located in Asia(Taiwan-Traditional Chinese)

If i find more i will add it here.
Thanks Blizzard for the last patches and hotfixes, keep going!
cheers~

6 Likes
2

I also agree that these 6 bugs should be fixed! Blizzard, please fix them as soon as possible, because they seriously affect the progress of the game!

1 Like
5

I know that for many Warcraft it works perfectly, especially for those who use classic, or HD, but for those of us who are used to reforged, the fps are terrible, especially when the elf race is occupied or you integrate that race into any map. The FPS drops incredibly, could you fix that? I occupy 4060 ti and yet it is evil, it is unplayable

6

Haha, I just found two new bugs that need to be fixed! There are now 7 project errors that need to be fixed!

7

why did they mess up with the zooming, It was perfect for 4k and my 48 inch tv, now they put this way too zoomed in…

8

My GPU is NVIDIA 1060 ti 6GB
But my FPS is around 150~190

1 Like
9

I hope Blizzard can fix the bug as soon as possible

2 Likes
10

[2.0.1.22490] There is another serious bug disaster in the version that destroyed many custom maps! Oh my god! It’s incredible!
The reason is due to the “Use Relative Upgrade Costs” being forcibly ticked from “True” to “False.”
as one of the most well known “bug” was left unaddressed, being the constant “Art - Portrait Model File” being forcibly added to every custom map out there. This addition broke the unit portrait of almost every custom unit that used a model, and has not been fixed.
It is likely that this new issue of the constant “Use Relative Upgrade Costs” will also not be fixed and go unaddressed like the above constant in the map editor.

Thankfully the whisper feature in custom rooms has been fixed! This is awesome!
I hope that every time Blizzard fixes, updates and upgrades, it won’t create new serious problems. Please~

1 Like
11

I hope these problems can be solved as soon as possible, so that no new errors will occur.

1 Like
12

So far, a total of 9 issues have been found that need to be adjusted and corrected.

1 Like
13

Oh my god, this is incredible! There are now more than 10 bugs to be fixed! And I have to worry about whether there will be more bugs after the update…

14

Hope Blizzard can fix all the bugs as soon as possible, thanks

15

I just hope Blizzard doesn’t destroy custom maps again!
Don’t create more errors and problems after updating!
Please respect the love of custom players for old custom maps of Warcraft!
I hope the Blizzard team will focus on fixing the reported bugs and obvious errors, please!

1 Like
16

Blizzard needs to fix the above errors as soon as possible!

17

Thanks to Blizzard for changing RelativeUpgradeCost back to 1 ( True ) in the 2.0.1.22498 new patch.
Thanks to Blizzard for making the Warcraft editor support unit module reference support in unitui.slk format to solve the transparency issues of most custom maps!
It saved a lot of custom maps! Thank you!
Please keep working on fixing the other reported bugs and issues! Thanks! Keep it up!

1 Like
18

Thanks to Blizzard for changing RelativeUpgradeCost back to 1 ( True ) in the 2.0.1.22498 new patch.
Thanks to Blizzard for making the Warcraft editor support unit module reference support in unitui.slk format to solve the transparency issues of most custom maps!
It saved a lot of custom maps! Thank you!
Please keep working on fixing the other reported bugs and issues!
Thanks! Keep it up! ^ ^

1 Like
19

That’s right~ Thank you Blizzard staff for their hard work during this period, but please also ask them to continue to fix the seven obvious errors reported above, and don’t derive new bugs after the update!
If I find new errors and problems I will continue to modify and update the post!

20

Please ask Blizzard engineers to deal with the above reported issues as soon as possible after the wonderful holiday, and do not derive new problems, thank you ~

1 Like