 |
ReedN
Wizard
Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon
|
 Posted: Sun May 17, 2009 3:46 pm
[3.07] "Command Input" Triggers no longer fire.
|
None of my "Command Input" type of triggers are firing in this release.
Here's an example. It doesn't look like it changed anything on me between versions, but for some reason it isn't working.
Version 3.06:
| Code: |
<trigger name="alertness_on" type="Command Input" priority="38560" case="true" regex="true">
<pattern>^alertness on$</pattern>
<value>i_failsafe_eq alertness</value>
<trigger type="Duration" param="10000" case="true" regex="true">
<pattern>^You prick up your ears\.$</pattern>
<value>i_aeon_executed
i_queue i_gaindef alertness
i_queue i_baleq_clear eq alertness
#sub {%ansi( brown)ONDEF%ansi( gray) alertness}
#state 0</value>
</trigger>
|
Version: 3.07
| Code: |
<trigger name="alertness_on" type="Command Input" priority="38560" id="1722">
<pattern>^alertness on$</pattern>
<value>i_failsafe_eq alertness</value>
<trigger param="10000">
<pattern>^You prick up your ears\.$</pattern>
<value>i_aeon_executed
i_queue i_gaindef alertness
i_queue i_baleq_clear eq alertness
#sub {%ansi( brown)ONDEF%ansi( gray) alertness}
#state 0</value>
</trigger>
</trigger>
|
|
|
Last edited by ReedN on Sun May 17, 2009 4:11 pm; edited 3 times in total |
 |
|
|
ReedN
Wizard
Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon
|
Posted: Sun May 17, 2009 4:06 pm
|
This being a rather large road-block for me, I can't test too much with command input triggers broken. Half my scripts are going to malfunction without this working. I'll be happy to continue alpha test the new version after this bug has been resolved.
|
|
|
|
|
Rorso
Wizard
Joined: 14 Oct 2000
Posts: 1368
|
Posted: Sun May 17, 2009 4:27 pm
|
Are you sure it doesn't work? When I try that script and write "alertness on" in the command line cMUD sends "i_failsafe_eq alertness" to the MUD.
|
|
|
|
|
ReedN
Wizard
Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon
|
Posted: Sun May 17, 2009 5:02 pm
|
That alias is defined for me.
The issue is that "You prick up your ears." isn't detected by the multi-state trigger after I type "alertness on". It should detect the text after it advances to the next state, but for some reason it isn't working. |
|
|
|
|
Rorso
Wizard
Joined: 14 Oct 2000
Posts: 1368
|
Posted: Sun May 17, 2009 5:12 pm
|
The two scripts differ. For example the regex="true" and case="true" is missing from the 3.07 version example in your post.
|
|
|
|
|
ReedN
Wizard
Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon
|
Posted: Sun May 17, 2009 9:31 pm
|
I didn't remove them so I suppose its like the other case I posted where the new version altered it.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon May 18, 2009 4:49 pm
|
Looks like the new version is having some problems importing or exporting some settings options. I've added this to the bug list to look into. If you change your trigger and enable the RegEx and Case Sensitive flags, then does it start working again?
|
|
|
|
|
ReedN
Wizard
Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon
|
Posted: Wed May 20, 2009 2:27 pm
|
It is a very odd. I look at the xml tab and it tells me that regex and case sensitivity are not selected, but if I look at the options, they are selected.
So if I physically remove them by unselecting their box and then saving, then add them again by selecting their box and saving, they will appear in the xml.
They will also function normally if this is done. It looks like it strips them out of the xml for some reason, but why they still appear in the normal options as selected if they are gone from the the xml is beyond me. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Thu May 21, 2009 12:45 am
|
Yep, I found the bug with the trigger (and button) properties that are getting reset. So it should be fixed in the next version. It's definitely weird that they show up in the options but not in the XML. But the XML is really the correct low-level data view, and if they don't display in the XML then the trigger isn't going to work. But it's good to hear that the trigger works once you fix the options. That means the next version should work fine for you.
Although anything saved with this 3.07 version might need to be edited again to fix it in 3.08. |
|
|
|
|
|
|
|
