Zugg Software :: View topic - Exits trigger issues, and strange placement of created on the fly variables.

Newbie Joined: 28 Nov 2010 Posts: 9

Hey guys,

Im kind of curious to if anyone has encountered a problem like this, and what they've done to fix it.

1) My room exits look like this [Exits: dir1 dir2 etc].... i have a trigger set up to fire on *Exits: * it is set up in a general trigger class that never turns off so long as the script is running. This trigger executes 98 out of 100 times. For whatever reason, the 2 times out of 100 the script doesn't fire anything. No debut messages or anything, its like cMUD just ignores it. Everytime this happens, i look at the scrollback and notice no difference in the look of the room exit line, it always has directions in it, and it never fails to fire on the same room more than once, its always a random room, that i walk time and time again without problems. Sometimes it will go the entire length (about 50-75 rooms each zone) without problem. Any thoughts?

2) I have manually set up through the package editor a "dirlist" string list variable in the root directory, along with all of the other general aliases and variables that i want to keep active all the time. For whatever reason, one out of every five times i fire an alias that updates the dirlist string list variable cmud will create a new one in a random class. Also, going back to see what happened when the alias fired, it sticks it in a class that had nothing to do with the alias that was just fired. Weird huh?

Anyways I know these errors have been posted before and i've reviewed them, but the solutions arent specific to my case. Can anyone give me some pointers? I should also mention, i have approximately 50 aliases and 50 defined on the fly variables, all of which always update in the root directory, its just the one string list variable that is being problematic.

I guess i should also mention incase anyone makes a comment about there being *Exits: * firing in the room description, but i've double checked all room descriptions, and even ran an entire log against the trigger, and it fires when i run the log through it. Even to test, i've set up a timeout function that when i sit in a room too long, i automatically "look" to force the trigger again in a loop until it catches the Exits: trigger... sometimes it works on the first timeout, sometimes it works on the 10th timeout... really strange.

Wizard Joined: 22 Mar 2007 Posts: 2320

1) Give us the actual XML code for your trigger: Select the trigger in the Package Editor. In the code window, click the XML tab at the bottom. Highlight and copy the the entire XML code to the cut buffer with CTRL-c. In a reply to this thread, paste the code. Before the beginning of the code, put: [code], and after the code put: [/code].

Also, open the debugger window. Turn on all the debugger display options. When you find a case where your trigger does not fire as you expect, copy and paste the relevant portion of the debugger display in your reply to this thread, again within code markers.

2) You should not post multiple problems in a single thread. In the future make a separate thread for each problem.

Give us the actual code for your alias, as described in answer 1). Also, if this alias is being called by other aliases or triggers, give us the actual code for those.

You say that you have examined the previous threads on problems similar to this, and that they aren't specific to your case. I remember quite a few relevant threads that gave general things to look for in cases like this. Have you found those threads, and followed those instructions to try to figure out the problem?

Things to look for, off the top of my head: Are there multiple places in your code where the alias is being called? Do you use threads at all (i.e., use #THREAD, #WAIT, and related commands)? Do you use commands that use #CLASS or #MODULE to change your current active class?

Newbie Joined: 28 Nov 2010 Posts: 9

Sorry about the lack of information, in response to your reply;

1) My dirlist variable is only called my "step" alias, its in the root directory and the only line in it is %pop(dirlist)
2) I dont use #THREAD, but i do often use #WAIT to space out the execution of commands. The mud i play on has a "Bot Thwacker" which is intelligent code to identify characters using scripts, and it "Thwacks" the experience, skill improvements and various other things.
3) I do not use commands that use #CLASS or #MODULE, my triggers are set up in seperate classes that i use #T+ and #T- use/disable triggers that are active.
4) I have went through several threads, and in any instance where i could find relavent information, i have attempted to look for/use the fixes that were supplied, but to no avail unfortunately.
5) Sorry about the multiple questions in the thread, i'll remember that for next time.

This is the XML for my exits trigger:

Wizard Joined: 22 Mar 2007 Posts: 2320

Newbie Joined: 28 Nov 2010 Posts: 9

Thanks for the info I will try and rescript it a cleaner fashion. As per violation of mud rules the particular mud I play on does not ban botting. I am not breaking the rules in any way, the bot detection script is for weining out the bots that spam the mud or the bots that camp or are not smart enough to handle themselves in situations involving other players. So not to worry I am not violating the wishes of the admin, ive already talked to him about it. And thanks again for your info.

Wizard Joined: 22 Mar 2007 Posts: 2320

Ah, interesting. Well, then, if you need more help after trying to track down the conflicts, just ask.

Newbie Joined: 28 Nov 2010 Posts: 9

Thanks for the offer. I suppose to avoid spamming the mud I can set up my script to space out the frequency of commands sent to the mud by using the spam filter I think. That will rid myself of the #WAIT commands I use quite often. As for #SEND %pop(dirlist) it sends it directly to the mud and it responds by giving me the "sorry that is not a proper command" send. I'll clean it up and come for help if I still have issues. Thank for pointing me in the right direction.