Zugg Software :: View topic - [1.18-1.15] Triggers firing immediately on connect?

Beginner Joined: 17 Nov 2006 Posts: 12

Ok, this problem strikes me as weird. I just installed a fresh copy of CMUD 1.15 (checked, even the program files folder wasn't there).

Then I create a session, connect, log in, log out, reconnect, log in (this fires off the autologon trigger creator). After that, I create a second trigger, very basic. The pattern (regexp) is as follows: ^You are thirsty\.$
As 'script' to run, all I've entered in it so far is "say Testing?"

So far, so good. If I actually get thirsty, the trigger works. Now for the weird part. When I then log off the MUD and try to connect again, I will see "say Testing?" appear right underneath "Connected to ..."

Somehow this trigger fires when connecting, but I can't figure out why.

I can't recall if this problem occurred in previous versions of CMUD as well.

Update: Today I found that I didn't have this problem on my laptop, where I also ran CMUD 1.15 ... The only difference I had between the laptop and my desktop machine was that the laptop didn't have a clean install of 1.15, instead it had an install of 1.12, upgraded to 1.13 and that upgraded to 1.15. After I uninstalled 1.15, removed the Program Files\CMUD directory and reinstalled 1.15, the problem also occurred on this machine.

Posted: Mon Nov 20, 2006 3:31 pm

Can you email me the *.PKG file (support@zuggsoft.com) that contains the trigger that is firing when you connect to the MUD? I can't reproduce this one.

Novice Joined: 06 Feb 2006 Posts: 48

I'm having a similar problem, one of my triggers in a non-zmud-imported package is firing automatically when I connect to that mud.

Posted: Tue Nov 21, 2006 6:12 pm

Btw, does this only happen when you connect to a MUD, or does it also happen if you open the MUD session offline?

Beginner Joined: 17 Nov 2006 Posts: 12

It only happens on connecting .. when I open it offline, nothing happens, as soon as I then click "reconnect", it fires.

Beginner Joined: 17 Nov 2006 Posts: 12

Just to bring this issue back to the front, even though I seem to be one of the only people having this problem.

In 1.18, this issue still occurs. I even tested connecting to another MUD just to see if the problem was related to that, but it occurs there too.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

I'm getting this too actually, where an alias runs the moment I connect which just echoes a message to the screen. I'm not using #EVENT at all, but I seem to remember it first cropping up in 1.16 when the event syntax was introduced.
I've had a look at it again - it seems like the problem doesn't happen the first time (after starting CMUD) I open the session, but does after that.
As mentioned before, it only happens when connecting properly, not opening offline.

See vid for demo
http://www.filefactory.com/file/9df655/

I can mail the pkg if you'd like Zugg?

Posted: Mon Dec 04, 2006 10:17 pm

Unfortunately I still cannot reproduce this, even on a fresh installation. Please email me the pkg file and reference this forum post in your email so that it doesn't get filed away and lost somewhere.

Beginner Joined: 17 Nov 2006 Posts: 12

I did email you the PKG file before, though that call seems to have been closed.

I just did a fresh install of CMUD 1.19 (uninstalled 1.18, deleted C:\Program Files\CMUD, deleted %My Documents\My Games\CMUD, deleted HKCU\Software\Addictive Software, deleted HKLM\Software\Zuggsoft, reinstalled CMUD).

The same problem still occurs, unfortunately.

Is it possible that I just do something wrong? I can send a new PKG file again if you want ?

Posted: Tue Dec 05, 2006 5:40 pm

What was the name of the package file that you sent? I got so many that I don't know which one it is.

And yes, support issues actually get closed as soon as they get added to the official bug tracking list. Our help system shows all open issues, so to avoid looking at 500+ crash dumps everyday, I have to mark them as closed and then assign them to a category so I can find them later.

Anyway, remind me what the filename was and I can see if I still have it.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

I sent ElysiumRPG.pkg this morning and referenced this post

Posted: Tue Dec 05, 2006 10:18 pm

Right. I tried it and couldn't reproduce the problem. I sent you an email, but I need the exact hostname and port that you are connecting to. All I can think of is that the MUD is sending something wierd that my test server isn't.

Edited: I did make a minor change to how events are loaded that could possibly effect this, so maybe that's why I didn't see it.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

elysium-rpg.com:7777

I'm not sure it would be the mud though, because it only happens the 2nd (and all subsequent) time I open the session.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Have a way to reproduce with a new PKG file on any mud.
It wasn't the alias that was firing, it was a trigger that was calling the alias.
Anyway...
** Note: You have to pick a mud that actually works, because the problem only occurs upon a successful connect **

Open CMUD
Click the 'All MUDs' tab, pick a random mud and 'Connect to session'
CMUD will connect to the mud (and create a new, empty pkg in the process)
On command line, #TRIGGER {whatever} {#say Test}
Close CMUD
Open CMUD
Double-click the new session you just made
It'll connect fine and the trigger does not fire
File -> Close Session
Double-click the same session as before
The trigger will now fire the moment you connect

If you now just reconnect any number of times without closing the session then the trigger will not fire upon reconnects.
If you close the session and reopen it then the trigger will fire again.

Guinn

Posted: Wed Dec 06, 2006 5:52 pm

OK, I'll try that and let you know what I find. Sounds like maybe it's a problem with the Close Session rather than with reconnecting to the MUD.

When I did my test I was just using the Disconnect and Reconnect menu options...I'll try it with Close Session.

Posted: Thu Dec 07, 2006 11:30 pm

Is anyone still seeing this in v1.20?

Beginner Joined: 17 Nov 2006 Posts: 12

Installed 1.21 this morning (fresh install) and the problem seems to be gone at first glance.
Haven't been able to reproduce this yet at least (while previously, it occurred on every session I created that had triggers)

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Looks fixed here too
Noticed just before I upgraded to 1.21 that it was fixed in 1.20 too

Cheers Zugg