Zugg Software :: View topic - Bug?- Trigers/Aliases not working when CMud restarts

Wanderer Joined: 03 Sep 2007 Posts: 88

Ok, so I just have a weird bug. This is kind of hard to explain... but it is repeatable. Its been happening for awhile now.

If i ever restart my MUD, triggers in my class "Expbot" seem to not work. Or it partially works.

for instance I have this trigger- botkill & lootmob are aliases

#T- death
#wait ((@rt+0)*1000)
#if (@status = 0) {stand;#wait 1000;status = 1}

;attack or search string, action 1 mob is alive, 2 is dead
#sw (@expvalue = 1 && @action = 1) {botkill}
(@expvalue = 1 && @action = 2) {lootmob}
(@expvalue = 2 && @action = 1) {#echo attackSeq off;#T- tm;#T- attackSeq; #T+ roomobvious;look}
(@expvalue = 2 && @action = 2) {#echo attackseq off;lootmob;#T- tm;#T- AttackSeq;#T+ roomobvious;look} {failure}

It returns "failure". I thought maybe my values reset when Cmud reset. So I double checked them, they are fine.

Now, I stumbled upon a way to get everything to "work" again. If i attacked the mob until it died this would trigger.

(Death trigger)
#T+ decays
lootmob<--- alias

This is the lootmob alias:

#wait 1000
stow right
#wait 1000
stance defen
#waitfor {You are now}
get my @skinweapon
#waitfor {You remove}
skin @mobkey

Which then triggers this:

Trigger: yielding {(a|an)} %1 %2.

#wait 1000
stow my @skinweapon
#waitfor {You put a}
get %2
#waitfor {You pick}
stow %2
#waitfor {You put}
stance @stance
#waitfor {You are now}
sea @mobkey
#waitfor {You search}

Which then triggers this:

#T+ roomobvious
action = 1
mobcount = 0
combat = 1
#T- decays
#t- death
#t- obvious
#T+ tm
#T- monsterloot
#T- loot
#echo decay- loot time
l

Ok, so after all this shit happens the first trigger(plus others) starts working again.

Now the delimma... I recently changed the script around so these items do not happen in the same order. Now I can't seem to "jumpstart" it. I am going to keep plugging away tonight until this works.

Has anyone seen anything like this? Maybe I'm missing something... What is my next step? I honestly have nfc how to troubleshoot or debug this.

Thanks guys :P Any help is appreciated.

Posted: Fri Sep 21, 2007 2:04 pm

Check for a class having the "disable on startup" option.

Wanderer Joined: 03 Sep 2007 Posts: 88

Class Expbot is "disabled on startup" .

I of course turn it on before I attempted any of this.

Is there some bug associated with disable on startup?

Wanderer Joined: 03 Sep 2007 Posts: 88

Ok, so I just checked and I indeed have the "Disconnect on start up" box checked. Unfortunately it was NOT disabled.

I know there is definitely something weird going on with the disables/undisables in the class.

For example... until it starts "working." I can't trigger any aliases from inside a trigger. Yet i can do the alias from the command line.

Fun stuff :P