Exodus

Greetings and well met. Here be some helpful hints and tips for those already playing Exodus...one of my favorite MUDs. It has a very friendly atmosphere and is pretty laid back.

Again, zMUD is the only way to go for me...but when you're done trying to get the Database feature to work the way you want it to, try looking under Silor for some easier methods.

Not much here at the current time..."Under Construction" as they say.

GENERAL USAGE SCRIPTING:

Here is some general usage scripting I have done for Exodus. I'm using zMUD 5.55 32-bit, so older version users (especially 4.x) will probably need to alter some of the scripting slightly to get it to work

Spell Affect Tracker:

This set of scripting allows you to track spells that are affecting your character. Repeat this first set of script for each spell you wish to track. This sets 2 variables per spell, one to let you know you are affected by the spall and the other to tell you approximately how much time remains on in. It updates the time remaining every 59 seconds by doing the affect command and reading the results. The clean-up portion is located below this set. I am currently working on another set that automatically sees what is affecting you and reports it...but ran into some bugs. This one works now.

VARIABLE
Variable Name:	strength
Value:	leave blank
Default Value	leave blank
Use Default Value (Check-Box)	Yes (checked)
Class Name:	affect

VARIABLE
Variable Name:	strengthtime
Value:	leave blank
Default Value:	leave blank
Use Default Value (Check-Box)	Yes (checked)
Class Name:	affect

TRIGGER
Pattern:	Spell: giant strength (%n) hours*
Commands:	strengthtime=%1
Class Name:	affect

TRIGGER
Pattern:	Your muscles surge with heightened power!
Commands:	strength=STRENGTH-;strengthtime=22
Class Name:	affect

TRIGGER
Pattern:	You feel weaker.
Commands:	strength=;strengthtime=
Class Name:	affect

TRIGGER
Pattern:	-::59
Commands:	aff;#CLASS affectgag 1
Class Name:	affect

To clean up some of the spam caused by the above script, add the following. This sets up gags that stop the results of the affect command from showing on the screen but still allows the triggers to update correctly. It then shuts off the gag so you can see the results if you choose to type in affect.

TRIGGER
Pattern:	You
Commands:	#GAG
Class Name:	affectgag

TRIGGER
Pattern:	Spell:
Commands:	#GAG
Class Name:	affectgag

TRIGGER
Pattern:	<HP:
Commands:	#CLASS affectgag 0
Class Name:	affectgag

To make the above scripts useful, add the following onto your status bar:

@strength@strengthtime

Repeat this with every spell you want to track. I use about 3-4 spaces between each set and it's readable at a glance.

This little set of script is nice if you don't pay attention at the bank. As we all know, the only way to find out your balance is to head to the bank and hope it's been a while since your last fight. Put these items in and whenever you want to know your balance, look at your "statement".

TRIGGER
Pattern:	Your balance is (%d) gold, (%d) silver.
Commands:	bgold=%1;bsilver=%2
Class Name:	banker

TRIGGER
Pattern:	Your balance: (%d) gold, (%d) silver.
Commands:	bgold=%1;bsilver=%2
Class Name:	banker

VARIABLE
Variable Name:	bsilver
Value:	leave blank
Default Value	leave blank
Use Default Value (Check-Box)	Yes (checked)
Class Name:	banker

VARIABLE
Variable Name:	bgold
Value:	leave blank
Default Value	leave blank
Use Default Value (Check-Box)	Yes (checked)
Class Name:	banker

ALIAS
Name:	statement
Commands:	#mess Gold:@bgold Silver:@bsilver
Class Name:	banker

While grouped, a mage will many times be asked for a number of spells to be cast on other group members. Below is the script I use for casting haste by request:

TRIGGER

Pattern: (%w) tells the group 'haste out'

Commands: cast 'haste' %1

Class Name: caster

Note that this can be set up a number of ways, but I believe this one is safest. I have also seen scripts that will cause another person to be able to control a mage via remote using a password, but I think that not only is this dangerous to your mage, but might be seen as multiplaying.
Also note that I use the word out at the end to keep from having false triggers. The target must be in your group and must gtell haste out.

Builders Site

Back to Main

TRIGGER
Pattern:	(%w) tells the group 'haste out'
Commands:	cast 'haste' %1
Class Name:	caster