Register to post in forums, or Log in to your existing account
 

Play RetroMUD
Post new topic  Reply to topic     Home » Forums » CMUD General Discussion
hyperion
Newbie


Joined: 12 Nov 2007
Posts: 6

PostPosted: Tue Aug 15, 2017 1:06 am   

#COND XML issue
 
Hi all,

I've noticed an issue with #COND after I added it to CMUD for the first time. Fairly simple example (although it occurs with -all-):

<trigger priority="854130" id="85413">
<pattern>(%w) tells you~:</pattern>
#COND {^%s} {#CAP tell} {Dur|Param=100}</value>
<trigger name="" type="Duration" param="100">
<pattern>^%s</pattern>
<value>#CAP tell</value>
</trigger>
<trigger name="" type="Duration" param="100">
<pattern>^%s</pattern>
<value>#CAP tell</value>
</trigger>
</trigger>

Notice it is repeated. It will continue to add to the XML duration section (it also happens with other types of #COND, doesnt matter) for EACH tell I receive.
So, after a few, I have a bunch of extra firing #CONDs.

I noticed it because each of them were capping extra lines; pretty soon it gets large and caps a ton. Same if I change it to loop lines, or whatever.

Anyone know what is up here?

Thanks!
Reply with quote
mikeC130
Wanderer


Joined: 03 Jul 2006
Posts: 58

PostPosted: Tue Aug 15, 2017 6:02 pm   
 
#COND is only used from the command line to create a new condition. Using it as a command WITHIN a trigger will cause it to add that as a new condition every time that line executes.

Delete that command and use the trigger editor to manage the additional stages within your existing triggers.

Mike
Reply with quote
Display posts from previous:   
Post new topic   Reply to topic     Home » Forums » CMUD General Discussion All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

© 2009 Zugg Software. Hosted by Wolfpaw.net