
Settings here are profile-independent - so they're applied equally to all profiles. If you want to edit profile-dependant settings, head to Profile - MUD settings.
Besides the Global Preferences, which are applied equally to all profiles, there are also Profile preferences, which can be found in / . Profile-based settings are specific to each particular profile only, so feel free to customize these for each character.
Here are defined profile-specific settings on how your connection is generally handled.
Use colorized output (if avialable) - selects whenever KMuddy will display MUD text in color. If unchecked, all text will be displayed in the default color.
Enable trigger loop detection - this is a special feature in KMuddy that'll watch out for looping triggers. If one is detected, it'll temporarily pause all triggers so that you have time to disable and fix your triggers.
Do not allow more than 100 repeated commands - this limits the amount of repeated commands (used with the repeat string) to be sent to 100. Useful if you accidently send too many by accident.
Enable telnet negotiation on startup - special negotiation when you're connecting to a server. Some don't support this properly, so this is useful to disable when needed.
Auto-append newlines on prompt - if enabled, KMuddy will append a newline onto each prompt - this is useful if some servers don't end the prompt properly.
Show prompt in a separate field - this'll have KMuddy display your prompt to the left of your input line.
Show prompt in the status bar - displays your prompt in the status bar at the bottom of the screen.
Show prompt in the console - if unchecked, KMuddy will gag your prompt. This option, combined with the previous two can be very useful.
Start advanced transcript when session starts - if enabled, KMuddy will automatically log everything as soon as you connect to a MUD. Log files are stored in your home folder, and a new one is made daily (if necessary).
All of the commands listed here, save for the last one, are expanded as specified by the speedwalking string (so .ne will cause kmuddy to send "North" and "East"). The last one, quit, is sent to the server when you select the - option.
Here, you can select which directories KMuddy will be using.
Default script location - this selects the location where you have placed your external scripts, and this is where KMuddy will look for them.
Default working directory - this is a directory for scripts that do not have any specified. Working directory is like the current directory that you "cd" to in a shell - so if the script tries to open a file without specifying any path, it'll look in that directory.
Default transcript directory - selects the directory where all transcripts (logs) will be saved to.
Here, you can configure settings for the MSP sound protocol. In the big box, you can add directories where KMuddy will look for sounds when it needs them.
Use MSP even if not negotiated - When this option is enabled, KMuddy will interpret MSP sequences all the time, even if no negotiation took place. Useful for MUDs that don't support telnet negotiation of MSP. But beware - only turn this on if your MUD really supports MSP to prevent other players from sending malicious MSP sequences, if you allow downloading of sounds.
Allow mid-line MSP sequences - Mid-line MSP sequences are a zMUD extension to the MSP spec that some MUDs seem to be using. You can enable support for this feature here, but ensure that other players cannot say/tell/whatever these sequences, or disable downloading support; otherwise players could instruct your client to download any file on the internet.
Here you can configure the long, and short names of the directions for the mapper to use. Generally you won't need to do this unless your MUD has specified them differently.
Here, you can configure triggers which will tell the mapper that you couldn't move to the room that you were going to. So you might want to list any closed doors, invalid room, or any other triggers listed here.
Enable valid room checking - if enabled, this will check all of the invalid movement triggers before adding the new room when you're mapping/following in the mapper. If it matches any of the triggers, it won't count the movement as a sucsessful one.
In the main window, simply add the regular expression trigger that matches the invalid move message, and they'll be taken into account.
These settings control options for the main KMuddy window.
Show the tab bar even if not needed - if this option is checked, then the tab top-left of KMuddy will always be displayed, even if you only have one profile open. The tab bar will also be displayed if you have multiple profiles open.
Show auxilary input line - allows you to have two input lines, each acting independently. This is a very useful feature if you're multi-tasking.
Always notify - if this option is enabled, KMuddy will notify you when new text is received - it'll be blinking in your window bar when that happens.
You'll only get notification for text lines that match some of the notification triggers.
Global notification - There are two different sorts of notification, global and local. Global notification takes effect when the KMuddy window is inactive and some text arrives from any of the MUD servers you're connected to. It causes the window caption and the appropriate field in the taskbar to start flashing. (Note: this isn't supported in older, 3.0 and below, versions of KDE).
Local notification - only applies to one connection. When it is not active and some new text arrives, the caption in the tabbar on the top of KMuddy window starts flashing in the same way as with global notification. It keeps flashing until you switch to that connection. This flashing never happens for the active connection, so keep this in mind when using both local and global notification (some text may have arrived to the active connection; even if its tab is not flashing).
These settings control the options for the output area - it's where you see all the MUD output.
Default background color - this selects which color KMuddy will use as the background color for text coming from the MUD - black is usually the standard on MUDs.
Default text color - this will be the color of non-colored text - grey is usually the set color on most MUDs.
Command echo color - commands sent by KMuddy will be colored in this color.
System message color - KMuddy's messages to you will be colored in this color.
Indentation - if KMuddy wraps your text into multiple lines, the level of indentation will control by how much the wrapped lines are indented.
Wrap at position - KMuddy will wrap to be the specified length, if they're over this limit.
History buffer size - specifies the amount of lines that KMuddy will keep in it's buffer (the output area). By default, it's set at 1,000 - and keep in mind that changing this will only take affect the next time the profile is opened.
Forced redraw after - specifies the amount of lines after which the whole output screen will be redrawn - only useful on old computers, and should be disabled (scroll the amount down to 'Never') if you aren't on one.
Enable command echo - if enabled, this will echo the commands you sent in the output area (in yellow by default).
Enable blinking - sets the option of text to blinking or not (used by certain MUds).
Enable system messages - if enabled, this will echo system messages in the output area - you should keep this option on, as system messages are very important (they are colored in cyan by default).
Enable word wrapping - if enabled, KMuddy will word wrap the incoming text, to a lengh specified by 'Wrap at position'.
This controls the fonts to be used in various places of KMuddy.
Server output - this controls the font, font style, and size for the text that's incoming from your MUD.
Input line - this controls the font of the input line (where you type commands to be sent to the MUD).
Multi-line output - this controls the font of the multi-line input line.
This controls the options for the input line - where you type commands to be sent to your MUD.
Keep sent text - if enabled, the text that you just sent will be kept in the input line, and not cleared. Useful if you're doing repeated actions.
Select kept text after it's sent - this handy feature, combined with the keep sent text option, will select the text you just sent - if you start typing a different command other than the previous one, it'll clear the previous one automatically.
Cursor keys to browse history - if enabled, this will allow you to use the up and down keys on your keyboard to browse the history of last sent commands.
Telnet-style paste - if enabled, this will cause text pasted into the input line to be sent directly to your MUD, and each line will be split up as it's own command.
Trim spaces - this will remove the spaces before and after the commands you send - for example, if you send " s ", it'll only send "s".
Enable auto-completion - enables/disables the feature of when you're typing something into the input line, KMuddy will suggest previous lines that you sent to use.
Type of autocompletion - autofill - this type of autocompletion will only complete when there is one match possibility left. shortest match - this type will keep suggesting possible suggestions as you type the command out.Popup list-box - kmuddy will display all previous commands that you entered that match the current one in a popup box above he input line.
Background color - sets the background color for the input line.
Text color - sets the text color to be used by the input line.
Swap ENTER and CTRL+ENTER for multi-line - this controls whether Ctrl+Enter inserts a newline into the input box and Enter sends the commands to the server, or the other way round.
In this menu, you can select how KMuddy interprets, and displays the colors that it receives. This is useful if you want to change some shades of a color for whatever reason. To select a new color, simply click on the color box beside the color name, and select the new color.
In this menu, you can select the values for special strings in KMuddy. Note they are called strings for a reason - their length isn't limited to one.
Command separator string - this string will cause your input to be split up. So for example, if you do "n;ne", kmuddy will send "n" and then "ne". Note that this'll cause a winking smiley to be split up too, but to avoid that, you can prefix the "Send as-is" string before your command - read on for an example.
Speedwalk string - to start a speedwalk, just prefix this string, and then put in your speedwalk path. For example, the speedwalk character is a dot, then you could do .3n2e to walk 3 north and 2 east.
Speedwalk even if empty - if enabled, and you send the speedwalk string without any commands after it, it'll effectively do nothing. Otherwise, if the option is disabled, it'll send the string itself.
Internal command-call string - this defines the string to be used for calling KMuddy's internal scripting commands (ie. set, echo, etc.)
Repeater string - the syntax to use this is #<string> this'll cause any text after the string to be repeated x number of times. For example, #5 hi will cause five 'hi's to be sent.
Focus string - this will cause text to be sent to a different tab - useful when multiplaying. The syntax is <string><tab name><string>commands to be sent.
Send as-is - this'll cause text after this string not to be parsed by KMuddy and sent directly to your mud exactly as you put it in. This is useful if you want to avoid an alias or a internal command going off on text that you want to get sent.
Expand backslashes - causes special strings that start with \ to be expanded and interpreted. The complete listing of them can be found expanded_backslashes here.
Select MSP (Mud Sound Protocol) - based settings here.
Enable sounds globally - enables sound for all profiles. This can be disabled in each profile setting individually.
Allow downloading sounds - if enabled, and KMuddy receives a URL from the MSP protocol, it'll download and play that sound.
You can select directories where MSP sounds will be sought for if a server needs them (so if your MUD doesn't use MSP, this is no use) in the big box.
You can edit your shortcuts here. To search for a particular shortcut, just type it's name in the top bar. To edit a shortcut, just double-click on it. Pressing the little white x on a red background will clear the shortcut, and to set a new one, just press the new key combination.
On the bottom, you can either disable the shortcut by selecting 'None', set it to the default value, or customize it. The button on the right shows the current key combination for that shortcut.
Here, you can select new colors that will be used by the mapper. Simply click on the current color, select a new value then save for the change to take effect.
Would you like to make a comment or contribute an update to this page?
Send feedback to the KDE Docs Team