I have seen that this problem with PARAM/Value/ has been adressed before, but what is the cause for this.
I didnt have this problem until today when I opened a old map and should do some terraining and started it to test it and everything was PARAM/Value/.
Is there any solution to this? My other two maps are ok at the moment...
@Hultmanable: Those occur when the game can't find the text for those entries. I'm sure other people around can tell you why it happens in your case, as I haven't experienced it myself.
Happens if localization file is corrupt or missing. Here are some causes.
Map was made with now deprecated enUK localization. All future edits are made on enUS which does not automatically copy from enUK. You need to export enUK, manually merge it with enUS (best done by adding enUK contents after enUS contents) and then import it back into the map. Delete enUK from the map to reduce file size as it will no longer be used. This problem only affects maps which were edited at any stage by someone using enUK SC2 installations such as sold in the United Kingdom and possibly other areas.
Map was being made in a localization different from your installed localization. When modifying it you accidently forgot to change localizations and so automatically created a new localization to place all new text into. This localization is incomplete and missing most strings yet it declared as your language so will be used over the more complete one. To fix you need to export this localization, manually merge it with the main localization (place one after the other in the text file, the localization to use is up to, as long as you only keep what you maintain) and then import it again. After this remove any incomplete localizations from the map to solve the error.
The number of localizations your map has should be the number you plan to maintain. If you are only writing in English then it should only have enUS localization. Some maps targeting Asian or European communities can have other localizations but it is important that they are maintained otherwise the localizations will be incomplete and look like what is shown above.
Ok thanks for the answer, can't say I know what the it all means hehe.
I have tested a few thing and it seems like when I moved my maps before updating to 3.0 and then didn't move them back afterwards, the problem only occurs when Im trying to change the loadingscreen text (body, title etc).
Now I tried to move the map back to it´s original folder and changed the title and so on...and it works now.. Does it have anything to do with what you tried to explain to me? =)
Did you try anything I said? It sounds like you did not...
If you want to know the actual problem you will need to give out the maps so people can look at the cause. Mentioning what localization your SC2 uses currently will also be useful.
I am pretty certain it is the result of something going wrong with map localization.
Sorry for not replying sooner. I found the problem. I have to set the right "Locale" in the editor. Thanks for helping.
You might have an additional problem.
If you have all the locales populated, then any player users the map for that locale will have issues.
So ... _IF_ you are not actively populating the content of all the other locales, then you should make sure they are not enabled.
MENU: Map... Locale... Modify Locales...
and then in the list DESELECT all locales that you are not supporting (ie: If English EN(US) is only one SELECTED, then that's pretty normal for people with english as first language).
Hi guys
I have seen that this problem with PARAM/Value/ has been adressed before, but what is the cause for this. I didnt have this problem until today when I opened a old map and should do some terraining and started it to test it and everything was PARAM/Value/. Is there any solution to this? My other two maps are ok at the moment...
Custom Campaign initiative StarCraft: Pandora , StarCraft: Replicant
@Hultmanable: Those occur when the game can't find the text for those entries. I'm sure other people around can tell you why it happens in your case, as I haven't experienced it myself.
Happens if localization file is corrupt or missing. Here are some causes.
The number of localizations your map has should be the number you plan to maintain. If you are only writing in English then it should only have enUS localization. Some maps targeting Asian or European communities can have other localizations but it is important that they are maintained otherwise the localizations will be incomplete and look like what is shown above.
@ImperialGood: Go
Ok thanks for the answer, can't say I know what the it all means hehe. I have tested a few thing and it seems like when I moved my maps before updating to 3.0 and then didn't move them back afterwards, the problem only occurs when Im trying to change the loadingscreen text (body, title etc).
Now I tried to move the map back to it´s original folder and changed the title and so on...and it works now.. Does it have anything to do with what you tried to explain to me? =)
Custom Campaign initiative StarCraft: Pandora , StarCraft: Replicant
To bad it did not work on my other two maps =(
Custom Campaign initiative StarCraft: Pandora , StarCraft: Replicant
Did you try anything I said? It sounds like you did not...
If you want to know the actual problem you will need to give out the maps so people can look at the cause. Mentioning what localization your SC2 uses currently will also be useful.
I am pretty certain it is the result of something going wrong with map localization.
Hi
Sorry for not replying sooner. I found the problem. I have to set the right "Locale" in the editor. Thanks for helping.
Custom Campaign initiative StarCraft: Pandora , StarCraft: Replicant
You might have an additional problem.
If you have all the locales populated, then any player users the map for that locale will have issues.
So ... _IF_ you are not actively populating the content of all the other locales, then you should make sure they are not enabled.
MENU: Map... Locale... Modify Locales... and then in the list DESELECT all locales that you are not supporting (ie: If English EN(US) is only one SELECTED, then that's pretty normal for people with english as first language).