Register to post in forums, or Log in to your existing account
 

 Related 
Contents
See also:
  Triggers
Triggers
  Pattern Matching
  Auto Login
  Trigger Types
  Trigger Tester
  Multistate triggers
Related Links:
  Quick Start
  Basic Usage
  Character
Auto Login [[cmud_autolog]] 
CMUD automatically creates Triggers for automatically logging into your MUD character. These triggers are created in a special class folder called "AutoLog".

The AutoLog class folder is automatically disabled after more than five command lines have been sent to the MUD. This prevents your autolog triggers from firing automatically (and maybe sending your password) after you have already logged in.

The Autolog triggers are created automatically only if the Character and Password fields in your Session Properties are blank. When these properties are blank, CMUD monitors the text received from the MUD and the commands that you enter. When it detects that you have logged into the MUD, it will display a popup dialog box showing what information it has collected and what it thinks your username and password are.

CMUD only performs this autolog detection on the second time you connect to a MUD. Typically, the first time you connect to a MUD you are creating a new character, which has a different login sequence on most MUDs. By waiting until the second lgin attempt, CMUD can more accurately determine the proper login sequence.

If you confirm the popup autolog creation, then the Character and Password fields in your session properties are filled in, and the autolog triggers are created.

Typically, you will see two triggers created in your Autolog class folder: one for the username, and one for the password. Here is an example of what those triggers might look like:
Code:
Pattern: Username
Script: #CH

Pattern: Password:
Script: #PW

The #CH and #PW commands are used to send the character name and password values that are stored in your session properties. Your character name and password are not stored in your *.PKG package file with your scripts (aliases, triggers, etc). Instead, they are stored in your Sessions.db session database along with the hostname, port, and other information about your sessions. This allows you to share your *.PKG package scripts without worrying about sending sensitive information such as character names and passwords.
Viewer Comments [0 - Post your comments]

Jump to:  

© 2009 Zugg Software. Hosted by Wolfpaw.net