| 
	
		|  |  
		| Zhiroc Adept
 
 
 Joined: 04 Feb 2005
 Posts: 246
 
 
 | 
			
			  |  Posted: Tue Jul 03, 2007 4:50 pm 
 [1.34] #STATE not acting right
 
 |  
				| This happens in zMUD too, btw. 
 I think the trigger set up would be:
 
 
 
	  | Code: |  
	  | #TRIGGER {pattern1} {#SH saw1} #COND {pattern2} {#SH saw2; #STATE 0}
 #COND {pattern3} {#SH saw3}
 |  If I do #SH pattern1 then #SH pattern2, I get the "saw1" and "saw2" lines. But according to the docs, #STATE is supposed to default to the current trigger if only a state number is given. Yet, it doesn't seem to work. The state of the trigger is clearly left at 2 in the settings editor, and doing #SH pattern3 gives "saw3". You need to explicitly say "#STATE pattern1 0"
 
 zMUD's docs also suggest that both the id and state number are optional, and that #STATE by itself should reset the trigger.
 |  |  
	  |  |  
		|  |  
		| Zugg MASTER
 
  
 Joined: 25 Sep 2000
 Posts: 23379
 Location: Colorado, USA
 
 | 
			
			  |  Posted: Tue Jul 03, 2007 5:01 pm 
 |  
				| confirmed and added to bug list. 
 |  |  
	  |  |  
		|  |  
		|  |  
		|  |  
  
	| 
 
 | 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
 
 |  |