Zugg Software :: View topic

Apprentice Joined: 30 Oct 2004 Posts: 127

I just recently made a trigger system to restore all guards within a city, and part of that is a multistate to capture the guards in the room.

This trigger is a multistate trigger that grabs the initial line ^Number of objects: (%d)
Now, I have a second line trigger for ^(*)$ to capture the full line. I've tried setting it to manual state or within 1 and just having it do #STATE 1 when a guard line is caught, then #STATE 0 when the prompt is captured (which is where the trig would end).

Now, I run this system, it captures perfectly fine for about 10 rooms and then magically stops. Nothing has changed, but it's almost like the trigger is broken. I can't reset it, I can't use #STATE to restore it to its first state. If I delete the trigger and remake it exactly as it is, it once again works for a random length of time and disables itself again. Thing is, this worked for like ....days and then all of a sudden its like it doesn't want to reset to state 0....any help would be appreciated as I'm baffled why this isn't working.

Wizard Joined: 22 Mar 2007 Posts: 2320

The most likely cause is that it gets stuck in a different state, but the #STATE command should fix that. Perhaps if you give us the actual code, and the exact steps you have tried to reset it.

Apprentice Joined: 30 Oct 2004 Posts: 127

Unforatunately it's a pretty big pile of code for it. But I've used #STATE and #SET as I've seen in other threads, to no avail. But the weird thing is, without changing anything, its magically started working today without disabling itself so ....I dunno. Thanks anyhow

Apprentice Joined: 30 Oct 2004 Posts: 127

Reviving this thread because I still can't find the issue and it's bothersome.

Basically the trigger fires properly about 20-100 times, then magically stops working. I figured it was something to do with my code disabling it or changing the state to an improper state....this doesn't seem to be the case

I put an ID to it, and I do #echo %state(IDNAME) and it shows 0 which is the first trigger in the state if I remember correctly. So this means the original trigger, which in this case is "^Number of objects: (%d)" , should fire no problem off "Number of objects: 1" no problem, but for some reason it doesn't.

I've searched for similar trigs, I've tried '#SET' to reset it, no change. But randomly, without me running the program for a while, I can start it randomly just to see if it's started working, and it does! Sometimes for a random amount of times as listed above, and sometimes it makes it through the 600 steps that the system does.....so I don't understand.

Posted: Wed Jan 19, 2011 11:22 pm

Have you exported the XML for the package then imported back into a clean session to test for corruption? This would be a good starting place if you have not already done so.

It sounds like you have a trigger that fires and then runs one huge script all from that one trigger? If that is the case, perhaps the next step if the export/import doesn't work, would be to break down the script into smaller sections. This would allow you to use a combination of the other settings in CMUD, giving more control over the script should it malfunction and more debug information. You could use aliases or events, that say added 1 to a variable each time one of these settings were fired or raised. This would give you a defined place to look for the problem if it persisted. You could do the debug variable thing within the large script too. I could be misunderstanding your implementation of the system you have though.

Apprentice Joined: 30 Oct 2004 Posts: 127

Well, the trigger isn't too massive, it just is a lot of if/switches to do what's required, based on the lines below

The first line trigger is about 60 lines, which is just more about resetting variables from the previous' rooms capture so nothing terribly complicated. The multistate, which I set to manual as well so I could control them better is about 140 lines of code, which has a lot of #delitem, and #send commands for dealing with the items in the room based on what they are....Do I need to split this up? Cause I like code to be a little cleaner by keeping it all together. And also, I did try the export/import option. Exported, deleted it out of Cmud, deleted the package file, remade the package file in Cmud, imported back in and saved. Once again, it would work for a bit, then stopped working again....so I don't know

Code Follows, in case I'm missing something:

State 0 Trig: ^Number of objects: (%d)
Code

Wizard Joined: 22 Mar 2007 Posts: 2320

You have a #WAIT in the first state. This could be the problem. #WAIT puts this thread into the background. which means that this trigger could accidentally fire twice before it finishes. That could mess you up badly. Do you actually need the #WAIT? You are multithreading here without any protection against thread collisions.

Apprentice Joined: 30 Oct 2004 Posts: 127

Yes, but that #wait only fires if I walk too fast in the program, which happens very rarely. Now I haven't confirmed it, but I'm pretty sure I never got to that point where it was walking too fast. ((this is more just a lag protection program)) I can try changing that to an alarm, but not sure that'll change things