I find this tends to happen when a rogue group aproches the speaker. They rattle off their line, but since it wansn't the player who set him off, you don't get the replacement text.
I haven't experienced this, myself, but I've heard friends mention the issue.
Apparently some type of dialog will not use $name at all. I suggest we compile a list of which dialogs can use it so our nice SFMAs do not look silly when $name and $himher pops up all over the place.
Ambush lines seem to work properly.
Is it not just a problem with text that doesn't have the substitution variables in the popup menu? If so I'd guess that th evariables are unsupported on those fields - Even if the odd one does work.
By my mohawk shall ye know me!
my toons
Funny: Ee-Ai-Ee-Ai-Oh! #3662 * The foul-mouthed Handyman! #1076 * City of Norms #132944
Serious: To Save A Single World (#83744) * Marketing Opportunity (#83747)
I think it's just patrols, maybe?
Please fight My Brute: http://2hero.mybrute.com
Mission Architect 54161 - Michael Mundano, Megan Malloney and the Secret Senate.
Mission Architect 91838 - Constantinople Jones' Family Secret. A One Mission Story arc.
Certainly not just patrols that I've noticed not substituting (and without rogue patrols in th emission).
By my mohawk shall ye know me!
my toons
Funny: Ee-Ai-Ee-Ai-Oh! #3662 * The foul-mouthed Handyman! #1076 * City of Norms #132944
Serious: To Save A Single World (#83744) * Marketing Opportunity (#83747)
I have had it occur in one of my arcs with a standard inactive boss dialogue as the heroes approach. That was what prompted me to start this thread.
Seen this couple of times, mostly exactly as in OP's case, - inactive boss intermittently forgets $name and $pronouns.
Unlike with patrols, where it isn't working by design, it works most of the time.
[ QUOTE ]
I find this tends to happen when a rogue group aproches the speaker. They rattle off their line, but since it wansn't the player who set him off, you don't get the replacement text.
[/ QUOTE ]
I have just made a test mission where I placed $name into any text field imaginable. All dialog fields is designed to handle the $name but some are more error prone for the reasons above.
Patrol and battles have a high chance of being activated by other opponents than the players and that leads to this behavior.
My test also revealed that you can also put your $name into:
<ul type="square">[*]Mission title [*]Mission subtitle[*]Accept text[*]Navigation text (objectives)[*]Glowie interation bar[*]Popup windows[*]Chat text (Glowies etc.)[/list]
I wasn't sure whether to post this on the technical issues board but decided the response was likely to better here, given the highly specific nature of the problem.
Is anyone else experiencing intermittent problems with the "$name" function?
I have had several occasions with the arcs I have worked on when things work absolutely fine in testing and on a run through after publishing then mysteriously start going wrong later on another run through, with no editing to the arc having been done in the intervening time.
So for example, text will show correctly as "I sense Liberty Lass approaching. Be on your guard."
Then on another run through the same text will show as "I sense $name approaching. Be on your guard," where the "$name" shows as exactly that rather than inserting the name of the hero.
It is rather frustrating as it can make a highly polished arc or mission look rather unprofessional.