1.35 Custom Game crashes when player clicks minimap

Steps to Repeoduce:

  1. Play custom map from Custom Campaign.
  2. Map is bigger than 192 x 192
  3. Map contains custom units that use custom models
  4. make intense fight in few places in the map
  5. Click on minimap when unit is attacked

Actual Result: Game crashes.

UPD: reproduces only if custom map has DEFAULT data Set in Map Options

27 Likes

We need to fix this bug. I have the same problem on a map (maximum size possible in the editor) with custom models/skins.
If you click on the minimap sometime it just fatal error. I don’t know if it’s linked to fight, sometime I got it without units even fighting.

5 Likes

A very important bug and obviously game breaking for any situation.
Many if not all modders will have their projects pretty much unplayable because of this.

As we suspect it could have something to do with aggressive-caching of the newer patches.

5 Likes

This needs attention! Hopefully it can be addressed ASAP

3 Likes

Just when things were starting to look promising for Custom Campaigns…

2 Likes

From my playtests, a fight is not even needed. The game can crash by clicking on the minimap even if nothing happens. And if you save a game while a lot of things happen on screen, the save is not usable because the game instantly crash on loading.

4 Likes

Bump for importance

3 Likes

bump, it is very needed

1 Like

This is important

1 Like

PLZ FIX this.
Very important
Très important
sehr wichtig
heel belangrijk

Seems like it can bve avoided by setting CUSTOM data set in Map Options.
Thank God it works now.

This occurs on the Night Elf campaign mission. I’m really fed up.

Confirming 29 Oct 23 this bug is still active. FIX THIS NOW Blizzard! This is game-breaking. WC3 is (was?) one of my favorite games. This breaks my custom games and makes them unplayable. Also tested it on basic maps, and the bug still occurs. This should be the #1 priority fixing things like this, instead of more monetization for World of Warcraft and Hearthstone…

23 Days later, bug is still not fixed

Seems like fixed in patch 1.36.1