with Patch 3.0 for SC2 just around the corner, and it being one of the biggest patches for the game in its recent history, I thought it would be a good idea to have a thread where all pitfalls of the new update get collected and solutions figured out.
Maybe we can use a simple format such as:
New pitfall: ... Solution: ...
As such, I will start with the first issues and solutions I found with the new update:
New pitfall: All "Text Tags" are gone/invisible, but there are no trigger errors observed Solution: In this case, you probably have the default game ui hidden. Simply show the "Text Tags" UI frame to get your text tags back!
New pitfall: "Set Playable Map Area" not behaving correctly Solution: In the new update, one can no longer "Set Playable Map Area" to a region with bounds larger than 1-255 in the x- or y-axis. The function simply throws an error in this case, not having any effect. Make sure that every region you are using is fitting within the new bounds.
New pitfall: The game is displaying all sorts of errors that I never saw before! Solution: It seems like Blizzard has added new warnings and error messages to the game engine. This new messages are a good thing because they can help you to find errors. Make sure to pay close attention to new errors and try to fix them properly.
New pitfall: There seems to be an issue with compiling script that contains actions or functions with the "native" flag checked plus having a custom script identifier, pointing to a custom function. Solution: Instead of using a custom script identifier and the native flag, use the new "inline" flag to achieve the same.
New pitfall: The "Extra Data" feature allows editing multiple files (documents) at once. However, there seem to be some issues with script containing text values. The editor is not creating the proper entry within the GameStrings.txt file when changing text via Extra Data, so in game the text will show up as "PARAM/Value/...". Additionally, when opening the changed document the traditional way, the newly inserted text values get erased. Solution: Be careful with the "Extra Data" feature until all bugs have been fixed. :(
Pitfall: Mod folder in sc2 will be wiped of non-mod files. I can only assume that the map folder will be wiped of non-maps too. This includes any file type. Solution: BACKUPS. EVERYWHERE. Oh and your backup folder is subject to the same rule.
Seeing as how people are clearly looking in editor, it'd be nice if one person could give me a yes or no if they are getting this same error... no prefixes/suffixes.
Pitfall: enUS is now forced on as a locale each and every time you open a map. Furthermore enUS will be set to the default language, even if no text exists for it, making it appear as though all your game text has been deleted. Solution: Switch to enUS as your default locale. I guess there's no fix for this besides Blizzard fixing it themselves.
Edit: Seems like enGB is just gone as a locale?
Edit2: Okay, if you're on enGB like me, follow these steps to get your text back. Do not do anything else.
Go to "Mod" or "Map" dropdown menu. Go to "Locale". "Modify Locales". Now check enUS and press okay. Then open the menu again and uncheck enGB. Now restart the map, and your text should be back. It's important to do this in order or else you'll just lose your text.
Pitfall: Mod folder in sc2 will be wiped of non-mod files. I can only assume that the map folder will be wiped of non-maps too. This includes any file type.
Solution: BACKUPS. EVERYWHERE. Oh and your backup folder is subject to the same rule.
THIS CAN'T BE HAPPENING!
I had no backup of my main trigger map. My data mod with all the abilities and units are fine, but my triggers... four months worth of work is gone!
Well, I guess that's it with Rock the Cabinet 2015 for me...
For maps and mods surviving deletion, is there any changes that seems to be noticeable when playing, say, a trigger not working terrain having become fucked up?
Okay, if you're on enGB like me, follow these steps to get your text back. Do not do anything else.
Go to "Mod" or "Map" dropdown menu. Go to "Locale". "Modify Locales". Now check enUS and press okay. Then open the menu again and uncheck enGB. Now restart the map, and your text should be back. It's important to do this in order or else you'll just lose your text.
Okay, if you're on enGB like me, follow these steps to get your text back. Do not do anything else.
Go to "Mod" or "Map" dropdown menu. Go to "Locale". "Modify Locales". Now check enUS and press okay. Then open the menu again and uncheck enGB. Now restart the map, and your text should be back. It's important to do this in order or else you'll just lose your text.
Ah yes, I knew about the "Locales" before.
I had to learn the hard way that, unless you export and import your default text (enUS for example) to all other languages, players with a non-enUS would see a param/value error while playing your map.
I didn't knew that this also works via "Modify Locales". I only ever used "Export/Import Locales". Good to know!
New pitfall: Some function parameters (like the alliance settings) get translated to the user's locale causing compiling errors.
Solution: Comment the functions trowing errors, save and close the map, change the locale to english, reopen the map, uncomment the commented functions and save again.
Ah yes, I knew about the "Locales" before. I had to learn the hard way that, unless you export and import your default text (enUS for example) to all other languages, players with a non-enUS would see a param/value error while playing your map.
I didn't knew that this also works via "Modify Locales". I only ever used "Export/Import Locales". Good to know!
No, no, it's not that. enGB is no longer a valid editor locale and so the text needs moving if enGB was your only locale.
I've got an odd problem: when I try to open my map, which uses the standard Blizzard Warcraft III Assets (not Renee's mod), I'm getting an error that the dependency cannot be found. I tried finding it through the Editor, looking at Blizzard dependencies and I can't find it anywhere.
Any idea of Blizz removed their Warcraft III assets? Or maybe it's just in a different place or something?
Hey guys,
with Patch 3.0 for SC2 just around the corner, and it being one of the biggest patches for the game in its recent history, I thought it would be a good idea to have a thread where all pitfalls of the new update get collected and solutions figured out.
Maybe we can use a simple format such as:
New pitfall: ...
Solution: ...
As such, I will start with the first issues and solutions I found with the new update:
New pitfall: All "Text Tags" are gone/invisible, but there are no trigger errors observed
Solution: In this case, you probably have the default game ui hidden. Simply show the "Text Tags" UI frame to get your text tags back!
New pitfall: "Set Playable Map Area" not behaving correctly
Solution: In the new update, one can no longer "Set Playable Map Area" to a region with bounds larger than 1-255 in the x- or y-axis. The function simply throws an error in this case, not having any effect. Make sure that every region you are using is fitting within the new bounds.
New pitfall: The game is displaying all sorts of errors that I never saw before!
Solution: It seems like Blizzard has added new warnings and error messages to the game engine. This new messages are a good thing because they can help you to find errors. Make sure to pay close attention to new errors and try to fix them properly.
New pitfall: There seems to be an issue with compiling script that contains actions or functions with the "native" flag checked plus having a custom script identifier, pointing to a custom function.
Solution: Instead of using a custom script identifier and the native flag, use the new "inline" flag to achieve the same.
New pitfall: The "Extra Data" feature allows editing multiple files (documents) at once. However, there seem to be some issues with script containing text values. The editor is not creating the proper entry within the GameStrings.txt file when changing text via Extra Data, so in game the text will show up as "PARAM/Value/...". Additionally, when opening the changed document the traditional way, the newly inserted text values get erased.
Solution: Be careful with the "Extra Data" feature until all bugs have been fixed. :(
Pitfall: Mod folder in sc2 will be wiped of non-mod files. I can only assume that the map folder will be wiped of non-maps too. This includes any file type.
Solution: BACKUPS. EVERYWHERE. Oh and your backup folder is subject to the same rule.
good idea. Will add stuff here
good idea. Will add stuff here
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIs anyone else getting no prefixes/suffixes for blizzard data? Custom map stuff still has them.
Pitfall: Negative charge use values are no longer supported.
Solution: Change charge location to something other than "Ability".
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSeeing as how people are clearly looking in editor, it'd be nice if one person could give me a yes or no if they are getting this same error... no prefixes/suffixes.
@MaskedImposter: Go
Not only this, but also the terrain tileset names, as well as all the doodad names are listed as Unnamed.
holy shit, this is terrible news
Pitfall: enUS is now forced on as a locale each and every time you open a map. Furthermore enUS will be set to the default language, even if no text exists for it, making it appear as though all your game text has been deleted.
Solution: Switch to enUS as your default locale. I guess there's no fix for this besides Blizzard fixing it themselves.
Edit: Seems like enGB is just gone as a locale?
Edit2: Okay, if you're on enGB like me, follow these steps to get your text back. Do not do anything else.
Go to "Mod" or "Map" dropdown menu. Go to "Locale". "Modify Locales". Now check enUS and press okay. Then open the menu again and uncheck enGB. Now restart the map, and your text should be back. It's important to do this in order or else you'll just lose your text.
THIS CAN'T BE HAPPENING!
I had no backup of my main trigger map. My data mod with all the abilities and units are fine, but my triggers... four months worth of work is gone!
Well, I guess that's it with Rock the Cabinet 2015 for me...
Blizzard starts contests. Blizzard patches away coming contributions. Good job, Blizzard.
For maps and mods surviving deletion, is there any changes that seems to be noticeable when playing, say, a trigger not working terrain having become fucked up?
Okay, if you're on enGB like me, follow these steps to get your text back. Do not do anything else.
Go to "Mod" or "Map" dropdown menu. Go to "Locale". "Modify Locales". Now check enUS and press okay. Then open the menu again and uncheck enGB. Now restart the map, and your text should be back. It's important to do this in order or else you'll just lose your text.
Ah yes, I knew about the "Locales" before. I had to learn the hard way that, unless you export and import your default text (enUS for example) to all other languages, players with a non-enUS would see a param/value error while playing your map.
I didn't knew that this also works via "Modify Locales". I only ever used "Export/Import Locales". Good to know!
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNew pitfall: Some function parameters (like the alliance settings) get translated to the user's locale causing compiling errors.
Solution: Comment the functions trowing errors, save and close the map, change the locale to english, reopen the map, uncomment the commented functions and save again.
Check out my kitbashes! Custom Campaign Initiative: Lots of great Custom Campaigns!! Check out and Support!!
No, no, it's not that. enGB is no longer a valid editor locale and so the text needs moving if enGB was your only locale.
Oh, they got rid of enGB! Sorry, I didn't catch that from your first post.
http://www.sc2mapster.com/forums/player-zone/warcraft-modding/83613-tutorial-things-that-may-break-your-map-in-the-void/#p1
I've got an odd problem: when I try to open my map, which uses the standard Blizzard Warcraft III Assets (not Renee's mod), I'm getting an error that the dependency cannot be found. I tried finding it through the Editor, looking at Blizzard dependencies and I can't find it anywhere.
Any idea of Blizz removed their Warcraft III assets? Or maybe it's just in a different place or something?
Double-post, sorry.