So, I decided to post this because it was happening to me practically every 5 minutes.
1). When you have a dialog that uses text and you go and change anything, and I mean anything to do with your map, the next times you try to test your map out, Param...(something) replaces your dialog texts. The only way to fix this is to copy everything you had, delete the triggers, and paste in what you copied before.
2). Rather randomly, the editor will derp and set all of your trigger and variable names to nothing. I literally means that every little text-thing that you can edit is turned into a blank space. To get your map working again, you have to go through the monotonous and confusing process of renaming all of your variables, and remembering what you had in the text of something. For example, I had text that said "Make an achievement." When I looked at it, all it was was "".
Really really bad and annoying bugs. It seems to only have happened to me after the latest patch.
Animated Achievement Library
I have a problem similar to the first one. I found out that you're not technically ruining the text or something. It's still there. So if you open a map, make some changes, then test it, the "/param" will appear. However, if you just save, re-load and re-test (in other words, opening the maps without doing any changes), the map is fine. I have - sadly - gotten somewhat used to it, but it still bugs me.
Quote from EivindL: GoI have a problem similar to the first one. I found out that you're not technically ruining the text or something. It's still there. So if you open a map, make some changes, then test it, the "/param" will appear. However, if you just save, re-load and re-test (in other words, opening the maps without doing any changes), the map is fine. I have - sadly - gotten somewhat used to it, but it still bugs me.
Actually, that was what was happening to me before. Then it evolved to be so bad that now the only way to fix it for me is to copy/paste the triggers.
Check the locale the editor is using, if that happens again. If everything is empty, it might change the active locale.
If you upload a file with that problem, it might be easy to tell what is going wrong.
At least I doubt that it rewrites all text in the map.
Get my GameHeart Observer Interface here!
All my maps from Amber Sun have that problem, so uploaded files exist.
Try this solution... It's a bit crude, but it may work:
1) Leave only your region's locale (or the one you're working with in the editor).
2) Activate diferent texts for each region's localization (it creates the folder for each locale copying the only one existing).
4) When you modify anything that involves text, redo the process, or the regions excluding the one you're working with will have the older text used.
My project: Exodus - SC Co-op Campaign. Just alpha... I'm taking my time. If somebody wants to help me, he's welcome.
Check out my kitbashes!
Custom Campaign Initiative: Lots of great Custom Campaigns!! Check out and Support!!
Quote from EivindL: GoAll my maps from Amber Sun have that problem, so uploaded files exist.
I checked "Amber Sun 03" and the only thing I noticed is that the file uses the enGB locale. So, I guess, that for some reason, the editor seems to alter the active locale for some reason.
My editor is set to use enUS and I altered all of my maps to use enUS, so my editor has that locale activated after opening a map. When I would change something in your map, it would create a new locale which would only contain the text entries I add. This would lead to the problems you experience.
So, verify that your editor is set to have the enGB locale active in its preferences -> General -> Locale.
If that problem persists, I fear you need to verify the active locale under:
Map -> Locale -> your locale needs to have the checkmark, if there is no checkmark, then it has a non-existent locale active which leads to the problems you experienced.
Maybe there is a scenario in which the editor changes the active locale for some reason to something that isn't enGB. If you find a scenario for that, you should tell Blizzard when this is happening.
Whenever that problem happens, you can save the map as a new file and then check Map->Locale or the import manager (-> activate checkbox) to find out which locales are present in the map. There should be a wrong one then.
-> Settings problem or editor bug/problem that alters the active locale...
Here is screenshot from the map with param/??/?? problem,
the one I point out is the only one isn't activate, so I only need to active that one and goodbye param problem?
Nope, didn't work, still getting param/??/??
You have to leave only YOURS (the localization of your map). That's the one that has all the language data. After that, copy it to all the other regions. Then, they should have the same language data, and you shouldn't have the error anymore.
How do I know which one is localization of my map which one is not? they all already have been selected with the exception of the one I point out.
There must be an easier way, but what you can do is to save the map as a folder with the components and then open it with an archive explorer.
In each region's folder (for example enUS.data), open the folder "localized data" and then the .txt file GameStrings.txt. If the txt has the text that you've written in the maps, then that's your locale.
You can simply erase the folders of all the locales but that one, or go to "Map-> Regional Configuration -> Modify" and unmark all but that one and accept.
After that, mark in the editor all the locales and accept again.
Thank you for the explanation, ver 5.9 is up, could you please kindly make a quick check if it fix the problem or not.
Saw it. It works (in esMX at least). But I've found 2 bugs:
1- I don't know if it must work like this, but in the first cinematic there's a line of tosh from the liberty campaign.
2- The marines have duplicated models. Is an actor issue I believe that caused by the actor of the marine (copy).
It works? great! the credits is already given on credits page
1. Not a bug, it is suppose to be like that.
2. The problem is noted, will be fix on next update.
You must login to post a comment. Don't have an account? Register to get one!