MudWrestler is a MUD client that works on 68K and PPC Macs.
FEATURES:
Ticker
You can set the Tick length and the alert time. Currently, the only Alert action is a beep and hard-coded feature that makes you say "x seconds to tick!" when it's x seconds to the tick. Be nice to me, and I may add the ability to directly link actions to alerts. In the mean time, you can make your own Trigger that looks for the phrase 'seconds to tick' and initiates actions. In fact, I've included a sample Trigger that does just that. I might also add a feature that automatically reset the ticker based off of definable parameters, like cues sent from the Mud.
Macro buttons
These are located above the Send field.
The macros can be fired by Command Keys:
Look: Command-L. Eat: Command-E. Drink: Command-D.
Sleep: Command-B. Help: Command-H.
The user-defined macros are Command 1-9, and all the f-Keys. And the End button.
Note: Any of the macros can be altered, even Look, etc.
Open, Abort buttons
These control the current connection to the mud. Pick the Mud you want to connect to through the PopUp menu, then hit Open. It's just that easy. NOTE: It's quite possible to open multiple connections in the same Sessions window! To phrase this more simply: You could be connected to ten different muds at the same time in the same Session window. I don't bother stopping you. You'd see all the incoming text from all the Muds. But you'd only be able to take actions in the last Mud opened. This is a feature of MW, so don't bother reporting it as a bug. =) If you don't want this behavior, make sure you Abort each connection as you're done with it.
Variables
Variables are derived from the last string sent by the Mud. They take the form ^0 through ^9. The ^ symbol is achieved by typing Shift-6. Variables can be used in Triggers, Macros, and Aliases, or typed directly into the Send field of the Main Window. (I don't personally suggest using them in the Send field. It can be bizzare, because you don't have much control over them.)
Example:
The Mud sends: Crystal hugs you.
You type: hug ^0
MW sends to the Mud: Hug Crystal
Variables are best used in Triggers, since response time is instantaneous for that function. Typing Variables into the Send field can be risky; let's say Crystal hugs you. You type "Hug ^0" into the Send field, and hit Return. BUT, the split second before you hit Return, Brutag the Homophobic says "Any of you wimps touch me, I'll rip your head off!" Because the Variable simply looks for the first word in the incoming text to determine it's own value, "Hug ^0" ends up being sent as "Hug Brutag".
Aliases
Description: Alias is useful for replacing a large command or a set of commands with just one word or set of words.
Example:
You make an alias /ff, which translates to 'cast fireball'.
typing '/ff mayor' into the Send window translates into 'cast fireball mayor'. Aliases can contain multiple commands in the Action field; each command must be seperated by the ## symbols that indicate Newline.
Example:
An alias called '/eat!' could do the following:
get bread from bag##eat bread##say Boy, that tasted good!##
Note: MW searches string framents for instances of Aliases. If you have "th" as an alias, MW turns ALL instances of th into the Alias Text. So, if you had an Alias "th" that referenced "cast sanctuary" and you type "Thank Gandalf", MW would assumed that you meant to type "cast sanctuaryank Gandalf." Please don't report this as a bug, it's not. It's how aliases work. =) I strongly suggest that you use some sort of naming convention for aliases that you're not likely to use in regular typing. I myself use a slash: "/th" instead of "th". Another good convention is to repeat the first letter: "tth" instead of "th".
(Note: Yes, I could test to make sure that aliases weren't part of larger words. I'm not going to, though, because it'd slow down text parsing a LOT, and it's just not worth the speed hit.)
Triggers
Triggers are fired by incoming text from the mud. Let's say that every time the mud tells you that you're hungry, you want to automatically eat bread. You'd make a Trigger named 'you are hungry' or whatever the exact text your Mud sends in such cases may be, and define an Action like 'eat bread'. You can define multiple commands in the action field by using the ## newline command.
Example:
get bread from bag##eat bread##say Boy, that tasted good!##
You can also have MW automatically respond to various situations by using Variables with Triggers. I've included a Trigger that responds if anyone hugs you.
Example:
Mud sends 'Crystal hugs you.'
Your trigger responds to 'hugs you' like so:
hug ^0##say ^0's the nicest person!##
Thus sending to the Mud: Hug Crystal, Say Crystal's the nicest person!
Gags
List gags like so:
horse##dog##cat##mouse##
Any incoming text that includes ANY of these words will be nuked. You'll never see it.
Example:
Grundy the Vocal has been doing Hollers all night, and you're really tired of reading his crap. Your Mud doesn't support NoHoller, and it's not worth hunting him down and killing him, so you simply open the Gag dialog and type:
Grundy## into it. From then on, NOTHING Grundy says or does will be shown to you.
THIS CAN BE DANGEROUS! Grundy is thereafter *totally* invisible to you. This might actually work to Grundy's advantage. He could walk up to you, steal everything you own, slap you around, and insult your manhood/womanhood right in front of your bestest Mud girlfriend/boyfriend, and there's not a thing you could do about it because you'd never even know it happened.
Replacement
This replaces the specified phrase with a DIFFERENT phrase. Let's say that you'd rather see "you freakin' DESTROY Koofy" instead of "you slash Koofy." You'd set 'slash' as the replacement name, and 'freakin' DESTROY' as the replacement action. This has a practical use; you can use it to condense large descriptions into small descriptions. Replacements do *NOT* utilize the ## newline protocol. If you try and define an action like: 'freakin DESTROY##totally mangle' then that's literally what you'd see when the text was replaced: 'you freakin DESTROY##totally mangle Koofy'.
Send
This happens when you type into the Send field of the session window and hit 'Return'. It's the basic method of interaction. You can type simple commands, or you can type compound commands by using ## to separate each command.
Examples:
say Hi, mud!
say Hi, mud!##look##say The place needs a good cleaning!##
alias1##alias2##
Speedwalk
This is a bit different than TinTin's speed walk. For one thing, MW will accept ANY single word/letter as a Speedwalk command. So, you could define a one word/letter Alias, and use it directly in the Speedwalk field. Speedwalk is different than Send in many ways, but the most basic is this: You do NOT need the ## command to execute a Newline. Each and every word is considered a separate command. Each word/letter MUST be seperated by a space.
Example:
n n n s e n look
would take you: North, north, north, south, east, north, then make you Look.
Speedwalk is all about speed. Thus, it bypases many of the text filters that other commands must go through. Aliases are the only feature supported for Speedwalk.
Here's a chart of legal commands for each feature:
Macros: ## Variables Aliases
Triggers: ## Variables Aliases
Aliases: ## Variables Aliases
Gags: ##
Replace: Variables
Send: ## Variables Aliases
Speedwalk: Aliases*
*Speedwalk ONLY supports simple aliases. Compond aliases are not supported.
That's it for the Seth Gecko release. Happy Mudding!
-Kyle
(371.63 KiB / 380.54 KB)
/ Binary encoded, use Stuffit Expander

7 /

2020-09-15 /

3097853aceff4161d224a83ce0cf09a80321bb9a /

/
Architecture 

Motorola 68K
System Requirements 
From Mac OS 7.0
up to Mac OS 9.2
Compatibility notes 
Architecture: 68K
Mac OS 7.x - Mac OS 9.2.2
Emulating this? It could probably run under:
Basilisk II