Code and +help
- 1 +help +3who
- 2 +help +aconnect
- 3 +help +bboard
- 4 +help +bg
- 5 +help +beginner
- 6 +broadcast
- 7 +help +build
- 8 +help +events
- 9 +help +finger
- 10 +help +hangouts
- 11 +help +help
- 12 +help +info
- 13 +help +jnotes
- 14 +help jobs
- 15 +help +kudos
- 16 +help locks
- 17 +help +log
- 18 +help +md
- 19 +help +meetme
- 20 +help ooc
- 21 +help posebreak
- 22 +help +poseorder
- 23 +help +request
- 24 +help +roll
- 25 +help +sp
- 26 +help +selfboot
- 27 +sheet
- 28 +help +spend
- 29 +help +staff
- 30 +help +temproom
- 31 +help +travel
- 32 +help +uptime
- 33 +help +view
- 34 +help +votes
- 35 +help +watch
- 36 +help +where
- 37 +help +who
- 38 +help whois
- This command is similar to +who, but shows the list sorted into three columns. This is useful for games with lots of players where the regular who or +who lists scroll off your screen.
Find this file on the mux by typing: +help +3who
- Toggles whether or not you will receive the global ACONNECT messages. By default all characters receive these messages. To opt out simply type '+aconnect'. If, later, you wish to start receiving them again simply type the command again.
Find this file on the mux by typing: +help +aconnect
- Scans joined bulletin board groups.
- +bbread <#>
- Scans messages in group <#>.
- +bbread <#>/<list>
- Reads message(s). <list> can be a single number, multiple numbers, or a range of numbers (ie. 1-6), or any combo.
- +bbread <#>/u
- Reads all unread messages in group <#>.
- Reads your next unread message.
- +bbcatchup <#>
- Marks all messages in group <#> as read. You can use multiple group #'s/names or may use the word 'all' to catchup on all messages on all boards.
- Totals unread postings (if any) in each joined group. You can place this command in your @aconnect, and it's recommended you do so.
- +bbpost <#>/<title>
- This starts a post to group <#>.
- +bbwrite <text>
- This adds text to an already started post.
- Same as +bbwrite.
- +bbedit <area>=<old>/<new>
- Edits your post in progress. Valid areas are: text, title
- Displays your current post in progress.
- Discards your current post in progress.
- This will post your current post in progress.
- +bbpost <#>/<subject>=<body>
- Posts a message to group <#>. This is a quick way of posting a message with one command.
- +bbedit <#>/<#>=<old>/<new>
- Edits one of your posted messages.
- +bbremove <#>/<list>
- Removes a message by you. <list> can be a single number, a group of numbers, or a range (10-14).
- +bbmove <#>/<#> to <#>
- Moves one of your messages to a new group.
- +bbleave <#>
- Unsubscribe from group <#>.
- +bbjoin <#>
- Joins a group you've previously 'left'.
- Listing of all groups available to you along with their timeout values.
- +bbsearch <#>/<name>
- Shows you a list of <name>'s postings on group <#>.
- +bbtimeout <#>/<#>=<days>
- Changes timeout for a message to <days>.
- +bbnotify <#>=<on|off>
- Turn post notification for group <#> on or off.
Note: You can use the boards name (or abbreviation) in place of it's number.
For a '.sig', set an attribute on you called BB_SIG, and place your signature in that.
Find this file on the mux by typing: +help +bboard
Myrddin's BBS is a global, multi-threaded board with a rich set of features. To see help on a particular topic on game, type '+help bboard/<topic>' (Example: +help bboard/bbread).
This is not currently in use on the game. We use the role section of the archetype role pages for this.
Find this file on the mux by typing: +help +bg
- This command will show you a list of useful game commands. This is a decent primer for people who are new to MU*ing to at least give them the basic commands they'll need to communicate with other players, who can better direct them to what they're looking for. If you have suggestions for commands that might go well on this list for your game, contact staff.
Find this file on the mux by typing: +help +beginner
- Start broadcasting to the Observation Deck.
- Stop broadcasting to the Observation Deck.
Find this file on the mux by typing: +broadcast
- +build (Build Project Name)=(IC Grid Location To Link To)
- Sends a job to staff letting them know your build project is ready to be reviewed. Please be sure to include the IC grid location that you would like it linked to.
Find this file on the mux by typing: +help +build
This isn't used on the game, as players do not have personal builds here. Use temprooms as needed.
- Summarizes all event entries.
- +event <#>
- View details for an event.
- +event/signup <#>
- Sign up for the event, if signup is enabled.
- +event/leave <#>
- Remove your name from an event's signup list.
- +event/create <Title>=<Date>/<Type>/<Summary>/<Max Signups>/<Rating>/<Death Factor>
- <Title>: Name of the event.
- <Date>: Must be in the 'Day Mon 00 00:00:00 YEAR' format. Example: Wed Jan 03 13:00:00 2017
- <Type>: Genre (Horror, Adventure, Crime, Etc).
- <Summary>: A brief summary of the event.
- +event/cancel <#>
- Cancels an event entry.
- +event/summary <#>=<summary>
- Sets the event's summary.
- +event/mail <#>=<text>
- @mails anyone signed up for <Event #> <text>.
- +event/remove <#>=<Player>
- Removes <Player> from <Event #>.
- +event/max <#>=<Max Signups>
- Sets the max signups for <Event #>.
Find this file on the mux by typing: +help +events
Please note: this system is not used often here. Typically, scenes are generated more organically, or are posted to the bulletin board system. Keep up with bbposts as much as possible to stay on top of scheduling for upcoming important milestones in the story.
The core code was created by Cobalt@WORA and modified by The Coder for use on this game.
- +finger <name>
- This command displays useful information about a player. You can also type '+finger me' to see your own finger information. There are a variety of built-in finger fields, but there are also additional fields that you can customize yourself. For more information on setting up your +finger, see the 'finger-setup' sub file.
The following finger categories are built-in. To set them, use &<field> me=<text>
- Your character's full name.
- Your character's true age.
- Your character's apparent age.
- Your character's IC position.
- What your character is famous for.
- Your roleplay preferences.
- The names of your other characters.
- Your character's theme song.
- A quote from your character, or that describes them.
- Your typical online hours.
- A brief synopsis of your character's personality.
- Useful for letting others know if you'll be away.
- Your character website, if applicable.
- Your character wiki page, if applicable.
You can also set up custom finger attributes. If you want to set an attribute called "More Detail" you could type &FINGER-MORE_DETAIL me=<text>, and it would show in your +finger. Note that field names longer than 11 characters are truncated.
Find this file on the mux by typing: +help +finger
+hangouts:Staff can tag certain rooms as being hangouts. By typing this command, you will see a list, along with the number of people currently in that hangout. This command will even show unfindable players in that location, but it will not show you their names.
Find this file on the mux by typing: +help +hangouts
This is not currently in use for the IC grid, as it changes with some frequency.
- The first command shows an index of all +help topics.
- +help <file>
- The second command allows you to read a topic, and the third will allow you to read subtopics. Unlike the built-in help system-- and even some softcoded systems in use elsewhere-- +help files can have multiple keywords to make it easier to find the right file. For example, you can access any +help file whose name starts with a + without typing it. '+help hangouts' is identical to '+help +hangouts'.
- +help <file>/<subfile>
- Pulls up supplemental files if there is an additional index in the help file.
This set of commands allows you access the global +help system. Many players sometimes get confused that +help and help are separate systems, and so it is worth noting that 'help' is traditionally for commands, functions, and features that are built in to the server code, while '+help' is for commands that have been added on to the server through softcode.
Find this file on the mux by typing: +help +help
- The first command shows you your general info, and will list other info sections if you have them set.
- +info <player>
- The second form of the command allows you to see this information for another player (or for yourself if you use 'me').
- +info <player>/<section>
- The third command will view this info, on yourself or another.
The info system allows you to add visible sections of your characters backstory that other players might know.
To set your general info, type &INFO-GENERAL me=<text>. You can set other info sections by typing &INFO-<name> me=<text>. Note that <name> should have spaces replaced with underscores.
Find this file on the mux by typing: +help +info
- +jnotes me
- The first command lists your jnotes.
- +jnotes me/<number or name>
- The second command will view them.
- +jnote/pitch <title>=<text>
- The third form of the command proposes a new jnote for your character. A job will be opened about the note, and if it is approved by staff, your note will be set. You may want to use the +myjobs command to stay apprised of the status of your request.
- +jnote/pitch <obj>/<title>=<text>
- The fourth form of the command functions similarly, but allows you to pitch notes for things that you control.
- +jnote/show <title> to <player>
- The fifth form of the command shows your jnote to another player. They will see your note, and can verify its authenticity with the +verify command.
This set of commands allows you to manage judgenotes on your character-- that is, notes approved by staff that denote additional powers or other information about your character which you may want recorded. You can view notes either by number or by their title.
Find this file on the mux by typing: +help +jnotes
- The +myjobs command shows a list of these jobs, along with various data about them.
- +myjob <#>
- The second command allows you to read a job.
- +myjob/add <#>=<comment>
- The third command will allow you to comment.
These commands provide you with an interface to the Anomaly Jobs system, and allow you to see jobs that you created, or that are tagged for you. For other help with topics relating to jobs, please see +jhelp, especially '+jhelp player'.
Find this file on the mux by typing: +help jobs
- +kudos <person>=<reason>
- If another player is playing exceptionally well to their Archetype, or just very well in general, and adding to the environment in genre-appropriate ways, send them a kudos! Once staff reviews the request they (and you) will be granted some GP and both will receive a warm and fuzzy mail on the subject.
Find this file on the mux by typing: +help +kudos
A +kudo MUST be an explanation of why something someone did exemplifies their Archetype, and MUST provide detail. Do NOT quote a pose in your +kudo and give a sentence on why you liked it. These will be denied outright.
- lock <exit>
- unlock <exit>
The lock and unlock commands allow you to lock or unlock exits that you have keys to. All exits in building projects (areas of the game outside the main "street" areas) have lists that show who controls them.
A lock can be set as 'owners', 'tenants', 'keys', or 'none'. Each level can control locks set to the levels below it. For example, locks set 'none' cannot be locked or unlocked by anyone. Locks set to 'tenants' can only be unlocked by a tenant or an owner, and so forth.
Find this file on the mux by typing: +help locks
The Logger system allows you to seamlessly log, clean and format a scene for posting to the wiki easily. A logger is basically an object you create (you can have more then one if a scene is paused) that you 'make' into a logger, and when it is dropped in a room, it will log what happens in that room.
- Making a Logger
- You only do this once per logger!
- @create <name>
- drop <name>
- +log/make <name>
- get <name>
'<name>' should be replaced with the name of the logger you made. Each one should be unique.
- At start of scene
- drop <name>
- This puts the logger in the room to capture information.
- +log/capture <name>
- What this command does is grab everyone currently in the scene, the current date, the current location name, and stores all of this at once for formatting on output. These details can be set manually, if needed.
- +log/on <name>
- The logger begins recording. Pose as normal. Do not use tabs or indentation; only use linebreaks for paragraph separation. Wiki really hates tabs and indents in raw text. Really.
- During the scene
- +log/undo <name>
- This will remove the last logged entry in the scene, useful if you typo or hit enter prematurely.
- +log/pose <name>=Text
- This will 'feed' a pose directly into the logger, useful if you have a set pose before you remembered to turn the logger on.
- +log/show <name>
- The logging system can also be used to view the scene as currently in progress, and not only for wiki formatting purposes. This will display the entire log to you as plain text.
- +log/last <name>=X
- This is a complete replacement for the +repose command used on some games. Additionally, if lose connection, you can see if you missed anything with this command.
- At end of scene
- +log/wiki <name>=<Short summary of scene>
- Copy/paste the output generated and put into Classic Edit Box.
- +log/off <name>
- Turns the logger off.
- +log/wipe <name>
- Erases the contents, if you know you won't be continuing this scene or have finished posting the content.
- get <name>
- Pick up your logger, don't litter!
Although +log/capture is suggested for use, sometimes its not appropriate. For example, in a long running scene if there was someone in at the start, but they left, and someone else came in later? A second running of +log/capture will pick up the new person but lose the old person. In that case you might want to +log/cast to set who is in the scene manually.
- Manual Commands
- +log/cast <name>=Person1 Person2 Person3
- Sets the people who are in the current scene.
- +log/date <name>=today, yesterday, YYYY-MM-DD
- This will set the date when the scene happened.
- +log/summary <name>=<summary>
- This will set the summary for the logs page.
- +log/locname <name>=<name of location>
- The name of the location is set on the scene.
- +log/story <name>=Story Category Name
- This doesn't usually have to be set but can, as it defaults to what the current active story is. But if, for example, you die early and have Facility RP, you would need to use this to set the log to go into the Facility section.
There are a few miscellaneous options available:
- +log/return <name>
- This is used if you see a logger laying around someone forgot to pick up.
- If you lost a logger and don't know where it is, this will return all loggers you own to your inventory.
Find this file on the mux by typing: +help +log
- Displays the monster's current level of damage.
- +md (#)
- Modifies the monster's level of damage by (#).
Both of these commands are usable by Staff or Directors only.
Find this file on the mux by typing: +help +md
- +meetme <player>
- Invites a player to meet you for RP.
- Joins a player who has invited you to RP.
- Summons a player to you if they have invited you to RP.
- Declines a RP invitation.
Pretty self explanatory. The first command invites a player to meet you for RP. That player may than accept by joining you or summoning you to their location or decline the offer. Both players must be IC for this command to work.
Find this file on the mux by typing: +help +meetme
- ooc <message>
- This command will show an OOC message to everyone in your current room. This is useful for communicating out of character when you are in an in-character area. Note that, just like a channel, you can use ":" or ";" to pose or pose/nospace to OOC.
Find this file on the mux by typing: +help ooc
By default, the game will output a blank line between poses.
If you would like to turn this off, type: &posebreak me=0
Find this file on the mux by typing: +help posebreak
The pose order machine tracks poses and alert when it's your turn.
- Display the current pose order.
- +poseorder <quiet/loud/off>
- Turn it on/off, set it loud/quiet.
- Clears the current pose order.
- +poseorder/here <on/off>
- The Owner can turn off poseorder for the room.
- +poseorder/exclude <here/dbref/!dbref/list>
- Exclude room from pose order.
- +poseorder/skip <name>
- Skips a person.
- +poseorder/remove <name>
- Removes a person from the poseorder
- For help on game.
Find this file on the mux by typing: +help +poseorder
This whole thingy was made by skew.
- +request <title>=<description>
- This command requests <title> and <description> from staff. The request is added to the jobs list and will be tended to as soon as possible.
Find this file on the mux by typing: +help +request
- +roll (Ability)
- Rolls a stat (Brawn, Finesse, Brains, or Spirit).
- +roll (Ability) [(+/- Modifiers)]
- Rolls a stat (Brawn, Finesse, Brains, or Spirit), with optional modifier for a positive or negative quality, perk, or other situational modifier in scene.
- +roll (X)d(Y)
- Rolls X (number) dice of Y (number). This is what you use to roll dice for your Supporting Roles and any Central Casting characters that do not have a coded sheet.
- Example: +roll 4d8
- Adding the /quiet switch to +roll will show the result only to yourself, good for testing or GMing. Command is otherwise formatted as above.
- Adding the /to=<person> switch to +roll will show the result only to yourself and the target person, good for testing or GMing. Command is otherwise formatted as above.
- Adding the /job=<#> switch to +roll will show the result only to yourself, and will add the roll to the specified job number. Command is otherwise formatted as above.
This will roll dice and report to the appropriate person or place.
Find this file on the mux by typing: +help +roll
- The first command resets the Survival Point totals of everyone in the current scene. (Staff or Directors Only)
- +sp/mod (Player)=(#)
- The second command will modify (Player)'s SP total by (#). (Staff or Directors Only)
- The final command will display the Survival Point totals of everyone in the current scene.
Find this file on the mux by typing: +help +sp
- This command allows you to boot 'extra' connections that are sometimes left over as a result of losing your connection to the game.
Find this file on the mux by typing: +help +selfboot
- Displays your character sheet.
- +sheet <name>
- Displays <name>'s character sheet.
This is not limited to staff only. All sheets are open and visible to everyone on Horror MUX.
Find this file on the mux by typing: +sheet
- +spend <#>=<reason>
- This will allow you to directly spend your GP (max 5), and log the reason for the spend both to those in your current location and to staff.
Find this file on the mux by typing: +help +spend
- This command shows a list of all connected, visible staff along with their status and idle time.
- The second form of the command lists all staff, regardless of connection status, with online staffers shown first.
Find this file on the mux by typing: +help +staff
- +temproom <room name>
- Creates a temporary room anywhere on the grid. (Staff can create temporary rooms anywhere.) Exit names are based upon the name of the room name you've created and are by default visible and unlocked, rooms findable (but not jump_ok). Additional instructions are available within the room itself.
- Empty rooms are cleared out every thirty minutes, unless excluded by a staffer.
- Destroys a temproom you are in, if you are the creator or a staffer, and if the room is otherwise empty of connected players. Temprooms set "permanent" by staff may not be destroyed in this manner, either.
Find this file on the mux by typing: +help +temproom
- +travel (num)
- Sets you IC and instantly sends you to the Hangout location associated with (num). See +hangouts for a list of valid locations.
Find this file on the mux by typing: +help +travel
- This command displays basic runtime statistics for the game, such as boot time, current server time, and the game server's uptime.
Find this file on the mux by typing: +help +uptime
- To see a list of all views in your current location, including players, objects, and exits.
- +view <target>
- The second command shows only a list of those views on the target.
- +view <target>/<name>
- The final command allows you to read those views. Note that you can use 'me' to refer to yourself and 'here' to refer to your location.
Views are a way to expand the detail of a thing with data that might not necessarily fit well, or concisely, in its description.
To set a view, simply type &VIEW-<name> <target>=Stuff. The name should have spaces replaced with underscores (ie: &VIEW-EYE_COLOR me=Brown). You can only set views on things you control, such as yourself or objects you create.
Find this file on the mux by typing: +help +view
- Show current topics to be voted on.
- +votes <#>
- Show the options and the running total of choices.
- +vote <#>=<#>
- To actually cast a vote, +vote <X>=<Y> will choose option Y for topic X.
If you vote a second time it will simply change your choice.
Find this file on the mux by typing: +help +votes
- Currently connected friends on your +watch list.
- +watch/add <name>=<note>
- Add a friend to your list (note optional).
- +watch/rem <name>
- Remove a friend from your list.
- Show all friends on your list with notes.
- Toggle hiding from sending +watch notifications.
- Toggle receiving +watch notifications.
- Clean non-player db#s out of your watchlist.
These commands are used to show you when friends connect/disconnect from the game and their idle/and or last connect times. You may also set an optional note for them.
Find this file on the mux by typing: +help +watch
- Similar to +who, this command shows a list of online players sorted by their location. If the location is JUMP_OK and you pass its tportlock, you will be shown its dbref. If a player or the room they are in is unfindable, you will not be able to see them, but they will be listed in the "Unfindable" section at the end of the list. Staff will see all players regardless, but unfindable players will have a * by their name.
Find this file on the mux by typing: +help +where
- This command displays an alternate WHO that lists player sex, alias, idle time, status, and location (if not unfindable). For similar commands, see: +3who, +where, and +hangouts.
Find this file on the mux by typing: +help +who
- whois <partial name>
This command will search approved players and return matches. It will search both Archetype names and one's full name, but it will show partial matches. For example. If you are in a scene and someone emits 'Cameron', but you forget which Archetype that is, 'whois Cameron' or 'whois cam' will show you which Archetype is named Cameron/Cam this cycle.
Find this file on the mux by typing: +help whois