Zugg Software :: View topic

Wizard Joined: 26 Mar 2008 Posts: 1547

Can I #RAISE a pre-defined event, such as onDisconnect?

When I quit out of the MUD using the quit command it won't immediately disconnect as CMUD waits to make sure I'm not actually still connected and receiving stuff from the MUD (which is a good thing, I dont want to adjust this setting!). Anyways, I'm creating a session to run all of my characters instead of having separate sessions for each character with a shared package. I'm doing this for a number of reasons, but, in the end, I believe it will cause less hassle in the long-run.

In any case, it resets a lot of the character-specific stuff onDisconnect. However, sometimes I want to switch characters and I do this via "quitting", "disconnecting" and "reconnecting" (never have to close the session window, one of the biggest advantages). It just occurred to me that I could check for the onReconnect event to solve my issue, but the question is still an important one in that onDisconnect doesn't fire immediately when I quit and I can't make quit run #DISCONNECT since it, for some reason, event though it's placed after sending quit to the MUD, means that I never see the quit echo for the MUD, which makes me worried that it doesn't get sent through. Thus raising the question: Can I manually raise a pre-defined event?

Apprentice Joined: 03 Jul 2006 Posts: 110

Yes, you can #RAISE predefined events. Specifically, I just tested and onDisconnect can be initiated from the command line with #RAISE.

More generically, I manually call onRoomCreate to identify and renumber rooms using the new GMCP messages.

Mike