Zugg Software :: View topic

Adept Joined: 18 Jun 2019 Posts: 279

This seems to be a bit of an issue.

Further to the DB ident debacle, I made no provision for a MUD IDENT misfire (Ident what?; You fail, etc), so I decided that the best solution was to fire a temporary trigger from my ID alias. Thus I have

alias LID, which has the following script

lore %1

#TEMP {+----} {#T+ EqIdent}

My EqIdent class has #ECHO "Ident Open" in the activate to let me know if and when it fires.

Imagine my surprise when nothing happened. So, to the trigger commands, I added:

#ECHO "BANG" to see if the temp trigger was firing:

#TEMP {+----} {#ECHO "BANG";#T+ EqIdent}

and, imagine my even greater surprise when I see 'BANG' appear on screen in shiny sky blue text. So the trigger works fine but there seems to be a problem somewhere.

Is there some fundamental setting I am unaware of?

Interestingly enough, when the ID command failed ('You fail'), and I tried the ID again

+----------------------------------etc
BANG
BANG
| Keywords ... etc

Was displayed. How is that possible?

It actually seems that, by not calling the class ( and therefore allowing its activate script to function) from outside a trigger the activate script does not function.

So

ident %1

#T+ EqIdent

will work, but

ident %1
#TEMP {+----} {#T+ EqIdent}

has a problem. The class enables, as all the triggers/scripts under it function correctly. The DEACTIVATE script also fails to work.

Window hangs are commonplace with using the database.

Posted: Tue May 19, 2020 12:50 pm

This is sounding more and more like a corruption issue.
My local activate/deactivate scripts are working when a temp issues a #T+/- command.
Try exporting your settings to XML and recreate your session.pkg file.

Adept Joined: 18 Jun 2019 Posts: 279

It was working. Not so sure it is these days.

Maybe it is just that I have been staring at it for too long.

Adept Joined: 18 Jun 2019 Posts: 279

The things that have ceased to work in the last weeks have been running at one point or another so compatibility report will show no errors - which is exactly as expected. NO errors. The strange but pathetic message that indicates one should syntax check things that were once working is meaningless.