All my names are displaying as "Button/Name/thename"
Even when I create a new button from scratch. Only the original ones work.
I had this problem back when WoL switched to HotS, too. Had to remake my map.
Now I've gone pretty far with a map to remake it. Please assist. How do I fix this?
Hard for people here to help you solve a problem that we can't replicate on our end. That's extremely weird. :(
What about changing the name of the field via catalog trigger? Could be time-consuming to redo every button, but it might be your only choice if you don't want to scrap your whole map.
If you are a UK mapper then this will be because enUK finally no longer exists as a separate and confusing localization from enUS. As a result all UK and US clients now use "English" as their localization which maps to the old enUS. The old enUK localization inside a map has been retained but is now deprecated so will not be used by the client (unless possibly if it is the only localization present). If you were a UK mapper then chances are your map used the old enUK localization which is why all text appears corrupted now since any change to text would have gone to the enUS localization which is missing all your enUK entries.
Fixing it is simple enough. Start by making a backup of your map in case something goes bad to avoid data loss. Use the localization submenu to export all localizations present in your map. Make sure to include editor only values when doing this otherwise some text might be lost. Open the resulting files in a probably like notepad and copy the contents of the old enUK localizations into the enUS localization files. Once done go to the localization menu and import the edited enUS localization back into your map again making sure to import editor only values as well. Then remove the deprecated enUK localization from the map by toggling it off and confirming the removal. Finally save the map and then close the map. When you next open the map it should have only one localization, enUS, which now contains both the recently changed text and the old enUK text. All text should also be appearing again when testing the map.
If you use a localization other than enUK or enUS then your editor might be defaulting to enUS instead of your current localization which is messing up the localized text. The same approach as above can be used to fix the problem by either moving all test to enUS or back to your native localization and deleting the undesirable localization.
If the above is not sufficient help you will need to provide the map either publically or privately so it can be investigated.
We meet again, ImperialGood. You used to help me with Warcraft 3 maps in The Hive.
Yes, my map does have a "enGB" option but it's not letting me select it. Whenever I do, it reverts back.
Now, I've been searching for a localization submenu but I can't find it. Are you talking about the one in Preferences? Because the export from there seems to export only the preferences, not the text.
Also I want to add that all the default effects have gone (unnamed), which is weird. These are core elements and they are screwed up too.
@Bilxor, I am looking for a quick fix, otherwise it's not worth as I have a deadline for this map.
Edit: I guess you're talking about the Import menu where I can export localization files, I just saw it. Ok, I am gonna try.
Edit2: It's not letting me modify reserved files or import such with reserve file names, what now?
Button Name fixed by deleting a character from the Path name in the button's name field and then reentering it. That would force the Data editor to create a new element for the current loc.
Also I want to add that all the default effects have gone (unnamed), which is weird. These are core elements and they are screwed up too.
That is because their names are editor only. Blizzard removed all editor only text in the last patch. Not sure why, but it makes no difference in game as you could not use or show those values anyway.
Quote:
Yes, my map does have a "enGB" option but it's not letting me select it. Whenever I do, it reverts back. Now, I've been searching for a localization submenu but I can't find it. Are you talking about the one in Preferences?
As I said, you need to export the localization and merge it into enUS. You cannot use enUK anymore for development as it no longer exists. After merging you can re-import using the localization sub menu and delete the enUK localization.
Alternativly if you want to discard all changes make to your enUS localization then delete enUS, save and reload the map. Sdd enUS from enUK (will make a copy of it, should happen automatically when adding), save and reload. Finally delete enUK, safe and reload. All changes added to enUS (changes since 3.0) would be lost then but all text in enUK (probably most of the text in your map) will be retained.
Quote:
Edit2: It's not letting me modify reserved files or import such with reserve file names, what now?
That error makes no sense. You should not be using the import manager at all. You should be using the localization sub menu. If that is failing with the error (did not in 2.0, but not sure about 3.0) then you might need to manual edit the text files by saving the map as components and editing them then.
If you cannot do it still then you can private message me a link to the map file on drop box or other file sharing services. It is always possible something new and strange is happening as the result of the patch which is currently not well documented.
All my names are displaying as "Button/Name/thename" Even when I create a new button from scratch. Only the original ones work. I had this problem back when WoL switched to HotS, too. Had to remake my map. Now I've gone pretty far with a map to remake it. Please assist. How do I fix this?
Hard for people here to help you solve a problem that we can't replicate on our end. That's extremely weird. :(
What about changing the name of the field via catalog trigger? Could be time-consuming to redo every button, but it might be your only choice if you don't want to scrap your whole map.
<Click Here> To See My Epic Single Player Campaign (LifeForceCampaign.com)
Sounds like corrupted localization files.
If you are a UK mapper then this will be because enUK finally no longer exists as a separate and confusing localization from enUS. As a result all UK and US clients now use "English" as their localization which maps to the old enUS. The old enUK localization inside a map has been retained but is now deprecated so will not be used by the client (unless possibly if it is the only localization present). If you were a UK mapper then chances are your map used the old enUK localization which is why all text appears corrupted now since any change to text would have gone to the enUS localization which is missing all your enUK entries.
Fixing it is simple enough. Start by making a backup of your map in case something goes bad to avoid data loss. Use the localization submenu to export all localizations present in your map. Make sure to include editor only values when doing this otherwise some text might be lost. Open the resulting files in a probably like notepad and copy the contents of the old enUK localizations into the enUS localization files. Once done go to the localization menu and import the edited enUS localization back into your map again making sure to import editor only values as well. Then remove the deprecated enUK localization from the map by toggling it off and confirming the removal. Finally save the map and then close the map. When you next open the map it should have only one localization, enUS, which now contains both the recently changed text and the old enUK text. All text should also be appearing again when testing the map.
If you use a localization other than enUK or enUS then your editor might be defaulting to enUS instead of your current localization which is messing up the localized text. The same approach as above can be used to fix the problem by either moving all test to enUS or back to your native localization and deleting the undesirable localization.
If the above is not sufficient help you will need to provide the map either publically or privately so it can be investigated.
@ImperialGood: Go
We meet again, ImperialGood. You used to help me with Warcraft 3 maps in The Hive.
Yes, my map does have a "enGB" option but it's not letting me select it. Whenever I do, it reverts back. Now, I've been searching for a localization submenu but I can't find it. Are you talking about the one in Preferences? Because the export from there seems to export only the preferences, not the text. Also I want to add that all the default effects have gone (unnamed), which is weird. These are core elements and they are screwed up too.
@Bilxor, I am looking for a quick fix, otherwise it's not worth as I have a deadline for this map.
Edit: I guess you're talking about the Import menu where I can export localization files, I just saw it. Ok, I am gonna try.
Edit2: It's not letting me modify reserved files or import such with reserve file names, what now?
Button Name fixed by deleting a character from the Path name in the button's name field and then reentering it. That would force the Data editor to create a new element for the current loc.
That is because their names are editor only. Blizzard removed all editor only text in the last patch. Not sure why, but it makes no difference in game as you could not use or show those values anyway.
As I said, you need to export the localization and merge it into enUS. You cannot use enUK anymore for development as it no longer exists. After merging you can re-import using the localization sub menu and delete the enUK localization.
Alternativly if you want to discard all changes make to your enUS localization then delete enUS, save and reload the map. Sdd enUS from enUK (will make a copy of it, should happen automatically when adding), save and reload. Finally delete enUK, safe and reload. All changes added to enUS (changes since 3.0) would be lost then but all text in enUK (probably most of the text in your map) will be retained.
That error makes no sense. You should not be using the import manager at all. You should be using the localization sub menu. If that is failing with the error (did not in 2.0, but not sure about 3.0) then you might need to manual edit the text files by saving the map as components and editing them then.
If you cannot do it still then you can private message me a link to the map file on drop box or other file sharing services. It is always possible something new and strange is happening as the result of the patch which is currently not well documented.