#Mudlet create alias skin#
#Mudlet create alias plus#
#Mudlet create alias series#
#Mudlet create alias free#

A green checkmark is displayed to the left of each trigger that is enabled. You can disable a trigger by clicking the Enable/ Disable button located just below the Command field in the dialog, or you can double-click on the trigger in the list box on the left. When you create a new trigger, it is enabled by default.

Click the OK button to save your changes and close the dialog.

#Mudlet create alias skin#

Click the New button in the Trigger dialog, then type You are thirsty into the Pattern field, and type drink skin into the Command field. Let’s create a simple trigger that keeps your character from getting thirsty. Then enter the pattern for the trigger in the Pattern field, and the commands you want to execute into the Command field. To create a new trigger, click the New button in the lower-left corner. On the right, you will see the fields for the trigger Class, Pattern, and Command, along with several options. As you select triggers in the box on the left by clicking on them with the mouse, the information on the right will be updated. A list of your triggers is shown in the box on the left side of the dialog, while the right side of the dialog displays information about the currently selected trigger. A trigger is not required to have a class.įigure 1 shows the zMUD Trigger dialog. Classes also provide you a way to organize your triggers into categories. Triggers within the same Class can be enabled and disabled as a group. The Trigger Class is a name given to a group of related triggers. A large range of example actions will be demonstrated in this chapter.

#Mudlet create alias series#

This action can be a simple string of text to send back to the MUD, or can be a complex series of zMUD commands. The Trigger Command is the action that you want to take when the pattern is received from the MUD. Patterns can range from simple text, to complex expressions, and we’ll explore some of the possibilities in this chapter. The Trigger Pattern is the text received from the MUD that causes the trigger to 'fire.' Whenever a line of text is received from the MUD, zMUD checks this line against each trigger pattern to determine which triggers to execute. In addition, there are several options for triggers that let you modify their behavior. There are three primary components of a zMUD Trigger: the pattern, the command, and the class. Both will be used in examples throughout this chapter.

#Mudlet create alias free#

Feel free to use either the Trigger dialog or the command language. Into the zMUD command line at the bottom of the screen. For example, to execute a command when a pattern of text is received from the MUD, you can enter In addition to using the Trigger dialog, you can also define Triggers using the zMUD command language. You can also display the Trigger dialog by pressing CTRL-T.

The easiest way for new users is using the Trigger dialog by selecting Triggers from the View menu, or by clicking on the Triggers button in the button bar. There are several ways to create Triggers in zMUD. In this chapter, we will work from simple triggers to complex triggers, building a useful library of functions for players of combat MUDs along the way. With Triggers, you can do anything from simple actions, such as automatically eating when your MUD character is hungry, to complex actions such as completely automating your character into a 'robot'. Triggers are the key to unlocking the tremendous power of a MUD client like zMUD. It should pop up in the Registered Event Handler box.As introduced in the last chapter, Action Triggers (or just Triggers) allow you to execute commands or send text to the MUD whenever a certain pattern of text is received from the MUD.

#Mudlet create alias plus#

So, if you're writing a function that you want to fire every time you get new character vital data, like HP, balances, all that, you would write '' into the 'Add User Defined Event Handler' box, and click the plus button. In the box labelled 'Add User Defined Event Handler', you need to write the exact table name of the GMCP data that you would like to cause the event to fire. This function will be called whenever your event handler is called. I don't know why this is, it's just a thing I discovered back when I was learning Mudlet. So if your function is called onVitalUpdate, your script needs to be called onVitalUpdate.

It needs to contain a function and an event handler, and the script file needs to be named the same as the function. GMCP events are fairly straightforward - events in general are a bit trickier and I haven't messed around with any player-created ones, so I'll leave that for someone else.īasically, you make a script (click the Scripts button on your menu bar, then click Add Item). I like talking about this because it makes me feel useful.