I've looked at this in more detail now. I think the quest itself might actually be wrong here. Here's the reasoning:Jay_H wrote:Interkarma, I'm running across a variable that's defined differently in DFU than in DF. When an enemy name is preceded by =, like =knight_, in DF it displays a name. In DFU it displays the race. Here's a screenshot of L0B40Y04
- =symbol_ for a Person resource resolves to class name. Both Tipton's docs (see QRC symbol table) and my own testing came to same conclusion.
- =symbol_ for Foe resource resolves to foe name. Again, both Tipton's docs and my tests align.
So any text in L0B40Y04 that uses the Person resource should actually use the correct macro _symbol_ for name in QRC section. They are instead using the Foe name macro against a Person resource. My feeling is quest was originally written with a single enemy in mind and later changed to a random enemy, and nobody fixed the macros. If I'm right, the same error should be present in classic (provided it's running the same version of quests). Let me know.
In any case, I've now fixed things up so non-monstrous Foe resources now select a gender and name. You should also be able to call =symbol_ macro on Foe resources and get back correct name in all cases (monstrous or humanoid). The Foe spawn should also match gender of name as well. It was worth just getting these fixed up.
Edit: More detail - because the quest uses a dummy Person for text and a random Foe for the spawn, there's no way the genders are guaranteed to line up in this specific quest. This quest would be much better off using a single Foe as the target and removing the dummy Person altogether. Then all the macros, genders, and spawns would like up properly. The quest itself is just a mess.
Edit2: Also, the pronoun parser does not consider monster genders. I'll look into adding this later.