I bring up a trigger of mine, type in a group name and click OK. I go back to the trigger. The group name is blank again. Any idea why it would do this? Group name is "g1".
Group not saving on trigger
Posted by Zeno on Mon 06 Aug 2007 10:55 PM — 8 posts, 19,118 views.
Seems to work for me. Do you close the trigger list too? Or just edit the trigger, add a group name, click OK, and edit it again?
The strange thing is that this is the only trigger it doesn't save on.
And yeah, I've tried hitting Ok on the trigger list too. Still doesn't save.
And yeah, I've tried hitting Ok on the trigger list too. Still doesn't save.
Maybe you have a script that is changing the group, or deleting and re-adding the trigger?
The only script I have is on a macro, so that isn't being set off at all.
Here is the trigger that fails to set a group name on it:
Everything else has a group name. This one just won't let me add a group name.
Here is the trigger that fails to set a group name on it:
<trigger
custom_colour="17"
enabled="y"
match="(.*) tells you '(.*)'|(.*) says '(.*)'|(.*) whispers to you '(.*)'|(.*)Tion(.*)|(.*)tion(.*)"
regexp="y"
send_to="12"
sequence="100"
sound="C:\DXball\DX-Ball 2\DX-Ball 2\sounds\Peow!.wav"
other_back_colour="white"
>
<send>SetStatus ("Last trig: %0" )</send>
</trigger>Everything else has a group name. This one just won't let me add a group name.
Well, I can reproduce it now. :)
Isn't that strange? I'll run it through the debugger.
Isn't that strange? I'll run it through the debugger.
I can reproduce it reliably, even in the debugger, but can't work out why it is doing it. There is a big "if" test to see if anything has changed (eg. the group) but it fails that, and since it thinks nothing has changed, it doesn't write the change to the trigger.
You can work around that by changing something else at the same time (eg. "send to" to something else), which will force the group to be recorded, and then change the "send to" field back again.
I will keep trying to work out what it thinks it is doing.
You can work around that by changing something else at the same time (eg. "send to" to something else), which will force the group to be recorded, and then change the "send to" field back again.
I will keep trying to work out what it thinks it is doing.
I found the problem - a misplaced bracket that made the fact that you had a sound there make it think the trigger hadn't changed.
It was one of those things that compiled OK, it just had a different sense to what I thought it did.
It was one of those things that compiled OK, it just had a different sense to what I thought it did.