Full Version : escaping comparison signs
xmlspawner >>Q&A >>escaping comparison signs
<< Prev | Next >>
Lichtblitz- 10-25-2007
Hi there.
I was trying to automaticly spawn a door that can only be forced open with a strong mace weapon. So I tried out the following:
DarkWoodGate,WestCW/ATTACH/<xmluse/name/forceme/condition/@GETONCARRIED,*,BaseBashing,mindamage>14>
The problem is obvious - the string stops evaluating at the first 'greater than' sign. How can I escape it? I tried out various combinations of {} braces but I had no luck yet.
Thanks in advance :-)
ArteGordon- 10-25-2007
yes, this is an annoying parsing issue. I am looking into modifying the way the literal escape char @ can be used to handle that, but for now you have to do it in two steps like this
subgroup 1: DarkWoodGate,WestCW/ATTACH/<xmluse/name/forceme>
subgroup 1: SETONSPAWN,1/ATTACHMENT,xmluse,forceme,condition/@GETONCARRIED,*,BaseBashing,mindamage>14
first spawn entry creates the gate and adds the attachment, and the second entry sets the condition property on the attachment to the string that you want.
Oh, and you might want to use the 'equippedonly' flag in the GETONCARRIED keyword so that the players have to have the mace equipped.
subgroup 1: SETONSPAWN,1/ATTACHMENT,xmluse,forceme,condition/@GETONCARRIED,*,BaseBashing,equippedonly,mindamage>14
Lichtblitz- 10-25-2007
Thanks for the answer. That really helps a lot :-)