I ran into this a couple times. Not sure what causes it (bug puts unprintable character in trigger name field?), but the only sure-fire way I know of to correct it is to delete the trigger event completely, then recreate it from scratch.
Looks like I figured it out. What I was doing is creating all of my Collect Object quests first & then adding in my Ambushes. It wants you to set it up linear. Ie, Collect Object 1 then add Ambush 1, Collect Object 2, add Ambush 2, Collect Object 3, add Ambush 3.
If you do it as Collect Object 1, Collect Object 2, Collect Object 3, followed by Ambush 1, Ambush 2, Ambush 3. It gives the above error when you try to run the mission. However, the icon that troubleshoots for you in the mission editor doesn't give any errors, which made me think I was doing nothing wrong.
This could make things tricky if you have a very detailed work-up & then stumble on running because the logic is wrong, but the MA design tool doesn't tell you which logic you screwed up on. A Trigger contains white space isn't a meaningful error message.
Thanks,
JKNIGHT
[ QUOTE ]
I ran into this a couple times. Not sure what causes it (bug puts unprintable character in trigger name field?), but the only sure-fire way I know of to correct it is to delete the trigger event completely, then recreate it from scratch.
[/ QUOTE ]
Yeah, I tried that & was getting the same error. I simply created a junk mission with simple defaults & plugged in one collection or ambush at a time to see what was going on. Apparently if the order in which you place your parts is unusual (multiple primary missions followed by multiple advanced missions) then you can get this error.
Basically if you try to do anything too different, such as try to add an ambush & patrol after an object has been collected, it might not give any errors, but it will fail to run with an obtuse "white space" error.
I think from now on, with each new piece that I add to a mission, I'll just do a save/run to see if there are errors.
In fact, it looks like it's probably better to create a skeleton mission with nothing but defaults to make sure it all works within the first 10 minutes of mission creation & then go back & flesh out the details once you know it will work. Looks like I learn a lesson.
Jknight
File a /bug report so the devs know to fix it.
Go to the text box with the bad trigger. Click Ctrl+A and then backspace/delete. Retype the text, problem solved.
I've created a simple mission with 3 collections and 3 ambushes and have linked each ambush to each collection. There are no errors from the error icon in the top right of the screen. So I would assume that means it is all working fine..
And yet, when I choose Save & Run, I get the following error:
A mission has an invalid detail trigger or an ambush with no trigger. The field Trigger begins with white space.
Where on earth is the problem?? I keep running into this but I have no clear idea where the link is broken!
Thanks for the help.