A game-stopper bug has been introduced in the latest patch. To reproduce:
Create a new map in the editor.
In the Map -> Player Properties dialogue box, assign all 16 player slots to be active players (change their Control to something other than "None".
Go to File -> Test Document.
The game cannot load the map!
If this bug occurs when playing a map online with other people, the entire user interface breaks - most buttons disappear, attempting to log out does nothing, and if you attempt to exit the game it crashes. Additionally, if you save and load the map in the galaxy editor, this error appears in the editor's message window:
Unable to load 'Map Info' from ''
After loading, the Map -> Player Properties list bugs out, the map is unplayable until you click "reset to defaults" and re-assign the list. A map with fifteen players works (any empty slot will do), but if all sixteen player slots are assigned, the game can break.
Maps with 16 players worked before the patch without error.
Confirmed, except for the bit about the player properties list exploding. I noticed this as soon as the patch came out, but couldn't link it to anything (all of the maps I'm working on right now use 16 players) until now.
This is an extremely serious bug. We should probably spam Blizzard with this particular bug, since it's easily the worst of any of the game or editor bugs we've seen yet.
Edit: This bug should be posted on the front page somewhere. Lots of people are going to be wondering why their map suddenly exploded.
By "the Map -> Player Properties list bugs out" I specifically mean it appears to reset the player list to default, but not truly because the map won't work until you actually click the reset-to-default button.
My map also has this error (or at least a similar error), but I wasn't using 16 players. I was using 4.
Strangely enough I traced my error to the fact that my loading screen text had a Y offset of -100. Switch to 0 or greater, and I could load it up again.
I believe that the error's related to some change in how the game & editor load map info.
Hmm... does it matter which slots are empty or does it have to be slot 15?
I have 6v6 where player 0 is neutral (mostly just used during hero select), 13 & 14 are shared team assets (buildings etc) and 15 is hostile (unclaimed buildings, zerg).
My map also has this error (or at least a similar error), but I wasn't using 16 players. I was using 4.
Strangely enough I traced my error to the fact that my loading screen text had a Y offset of -100. Switch to 0 or greater, and I could load it up again.
I believe that the error's related to some change in how the game editor load map info.
Oddly enough, I thought the problem with my map was first the loading screen too. I think you're right, it's an issue with map info in general. I believe I had the loading screen problem like you did... I changed the screen to another one, then back to the original, and the map worked until I encountered the # of players issue.
Hmm... does it matter which slots are empty or does it have to be slot 15? I have 6v6 where player 0 is neutral (mostly just used during hero select), 13 14 are shared team assets (buildings etc) and 15 is hostile (unclaimed buildings, zerg).
The slots don't appear to matter, just must have one slot (any slot) set to None for the map to work.
I know this is quite an old thread, but I had to create an account and come here just to thank you guys.
I was happily editing a map and made a couple of changes at once and then found out the game failed to load my map everytime I tried it. When I reloaded the map in the editor, it complained something about unable to load mapinfo.
I tracked the error to a position change in the loading screen. If you want to set a custom position for your loading screen text and you use say top left align, using positive offset numbers moves the text outside of the screen. So you'll probably want to set a negative number then to get some margins, right? Well that seems to be the issue. I was able to set a negative Y offset, but using a negative X offset seems to crash the game when loading. Notice that if this happens to you, it is not enough to change the alignment back to "default". The offset number still stays there even though its greyed out and continues to cause trouble.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
A game-stopper bug has been introduced in the latest patch. To reproduce:
The game cannot load the map!
If this bug occurs when playing a map online with other people, the entire user interface breaks - most buttons disappear, attempting to log out does nothing, and if you attempt to exit the game it crashes. Additionally, if you save and load the map in the galaxy editor, this error appears in the editor's message window:
Unable to load 'Map Info' from ''
After loading, the Map -> Player Properties list bugs out, the map is unplayable until you click "reset to defaults" and re-assign the list. A map with fifteen players works (any empty slot will do), but if all sixteen player slots are assigned, the game can break.
Maps with 16 players worked before the patch without error.
Cross-posted: http://forums.battle.net/thread.html?topicId=24702266874&postId=246998851617&sid=5000#0
Confirmed, except for the bit about the player properties list exploding. I noticed this as soon as the patch came out, but couldn't link it to anything (all of the maps I'm working on right now use 16 players) until now.
This is an extremely serious bug. We should probably spam Blizzard with this particular bug, since it's easily the worst of any of the game or editor bugs we've seen yet.
Edit: This bug should be posted on the front page somewhere. Lots of people are going to be wondering why their map suddenly exploded.
By "the Map -> Player Properties list bugs out" I specifically mean it appears to reset the player list to default, but not truly because the map won't work until you actually click the reset-to-default button.
@Thalassicus: Go
My map also has this error (or at least a similar error), but I wasn't using 16 players. I was using 4.
Strangely enough I traced my error to the fact that my loading screen text had a Y offset of -100. Switch to 0 or greater, and I could load it up again.
I believe that the error's related to some change in how the game & editor load map info.
Hmm... does it matter which slots are empty or does it have to be slot 15? I have 6v6 where player 0 is neutral (mostly just used during hero select), 13 & 14 are shared team assets (buildings etc) and 15 is hostile (unclaimed buildings, zerg).
This error showed up in my map upon opening it in the editor as well. A map that was last saved pre-patch.
@xenrathe: Go
Oddly enough, I thought the problem with my map was first the loading screen too. I think you're right, it's an issue with map info in general. I believe I had the loading screen problem like you did... I changed the screen to another one, then back to the original, and the map worked until I encountered the # of players issue.
The slots don't appear to matter, just must have one slot (any slot) set to None for the map to work.
Thanks Thalassicus, I've just posted your findings in the front page. Hope Blizzard will fix this fast.
I saw it, but how about the map info crash?
Hi guys,
I know this is quite an old thread, but I had to create an account and come here just to thank you guys.
I was happily editing a map and made a couple of changes at once and then found out the game failed to load my map everytime I tried it. When I reloaded the map in the editor, it complained something about unable to load mapinfo.
I tracked the error to a position change in the loading screen. If you want to set a custom position for your loading screen text and you use say top left align, using positive offset numbers moves the text outside of the screen. So you'll probably want to set a negative number then to get some margins, right? Well that seems to be the issue. I was able to set a negative Y offset, but using a negative X offset seems to crash the game when loading. Notice that if this happens to you, it is not enough to change the alignment back to "default". The offset number still stays there even though its greyed out and continues to cause trouble.