Plus Help
From Crossroads Wiki
Contents |
+admins
Syntax:
+admins +admins/all
This command shows all connected admins who are not set DARK, along with their alias, staff position, duty status, and how long they have been idle. With the /all switch, displays all admin and last connected times.
+age
Syntax:
+age +age/set <years> +age/set <years> in <month> +age/set <years> on <month> <day> +age/privacy on +age/privacy off
The +age command displays your current birtdate and age. With the /set switch, you may specify your age in years (with your birthday today), age and birth month (on the first day of that month), or age and exact birthday.
By default, +age is public. You can set your age to be private by turning privacy on.
+amail
Syntax:
+amail <subject>/<message> (admin only) +ticket <subject>=<message> (everyone)
Admin mailboxes fill up pretty quickly, so we would like players to use the +ticket system. This method will give you a faster, more personal response to your communication to admin, as well as record the action taken.
See also: +help +ticket
+back
Syntax:
+back in <time until return> +back at <time of return> +back on <date of return> +back on <date> at <time of return> +back <player>
This command allows players to set a time at which they expect to return, either from a brief idle period, or a longer vacation.
<Time until return> can be a number of minutes or a string of the form "#d #h #m" with the number of days, hours, and/or minutes, respectively. (Use 0 to indicate you're back now.)
<Time/date of return> is a time of day in either hours or hours and minutes (either 24-hour or with am/pm). Date is MMM DD. Date and time are in the player's time zone (if &TZ is set) or game time (U.S. Eastern time) if no &TZ is set.
The information from +back <player> is also automatically included as a field in +finger.
Examples:
+back in 30 - player will be back in 30 minutes +back in 1h - player will be back in 1 hour +back in 1h 30m - player will be back in an hour and 30 minutes +back in 0 - Player is back now! (Clears the setting.)
+back at 5 pm - player will return at 5pm (local if &TZ set) +back at 5:30 pm - player will return at 5:30pm +back at 17:30 - player will return at 5:30pm
+back on Dec 25 - player will return on December 25 +back on Dec 25 at 8 pm - player will return at 8pm on December 25
+beginner
MUSH is new to some of you and probably a little daunting. To ease your feelings of panic, we offer a very basic list of commands that will get you looking around and using the various features of the game.
"<message> You say <message> Say <message> See above. ooc <message> Makes an OOC statement or pose. page <person>=<message> Pages <person> with <message> look Shows you the room you are standing in. look <object or person> Shows the desc for that object or person pose <message> You pose <message> EX: pose grins.->John Doe grins. :<message> See 'pose" above WHO Shows a list of who is connected to the MUSH +who Shows a modified WHO. +help The global +help system. +admins Shows connected Staff
NOTE: MUSH commands may be case sensitive. You can always page a staffer for help.
"+beginner" recalls this file
+bug
The following commands provide player access to the +ticket system:
+bug <details> ................ Report a bug.
+typo <details> ............... Report a typo. Your location will be automatically included with the report.
+ticket <subject>=<request> ... Creates any other trouble ticket.
+census
Syntax:
+census +census <duchy or 'none'>
This command returns a list of all players who have connected to the game within the past 30 days. If a duchy is specified, the list will be limited to only those players whose home duchy (&DUCHY attribute) matches the specified text.
Warning: this command is /very/ spammy.
+comlock
Syntax:
+comlock <name> - add <name> to page and mail locks +comunlock <name> - remove <name> from page and mail locks
The +comlock command allows players to protect themselves from unwanted pages and @mail by adding the specified <name> to their @lock/page and @lock/mail lists. The +comunlock equivalent will reverse the action of +comlock.
Note that if you've manually manipulated your @lock/page or @lock/mail, the unlock command may not work properly, and you may have to remove the locks manually.
+currents
Syntax:
+currents
This displays the direction that the currents are presently running between the duchies.
+date
Syntax:
+date
Displays current IC date.
See also: +dtw +time +weather +tide +moons
+datebook
Syntax:
+datebook - lists all entries +datebook <date> - lists entries for <date> +datebook/upcoming - lists entries for next # (default 15) days +datebook/upcoming <#> - sets # of days for above command to show
+datebook/add <date>=<text> - Adds an entry +datebook/clear <date> - Removes all entries for <date> +datebook/remove <date>=<text> - Removes a single entry for <date>; <text> can include wildcards
The +datebook code allows you to maintain a calendar of important IC dates (such as birthdays, holidays, and other recurring annual events). You can have multiple entries for each date. The +datebook/upcoming command is automatically executed when you log in.
Example: +datebook/add Jan 1=New Year Celebration
+desc
NOTE: This system stores and retrieves individual parts of a description. To edit your description by categories (types), see +help +desc/types
Syntax:
+desc/list - List the names of all your descriptions. +desc/view <desc-name> - Look at a particular description. +desc/get <desc-list> - Change your @desc to the named one(s). +desc/store <desc-name>=<text> - Create a new description from scratch. +desc/kill <desc-name> - Erase an old description. +desc/save <desc-name> - Copies your @desc for later retrieval. +desc/edit <desc>=<old>/<new> - Edits a saved description.
This set of commands will allow you to use the global multi-description system, a slightly more complex, but infinitely more configurable system than +wear (see +help wear). These commands let you store any number of descriptions and to retrieve them as needed in any order.
Some helpful tips: '+desc/store' is used to author a new description. It does not save or modify your current @desc but creates a brand new saved description. Use '+desc/save' to save your current @desc so that you can retrieve it later. This is also handy for porting descriptions from other multi-descers as you can load them into your @desc and then use '+desc/save'.
You can chain together sets of descriptions, making a complex multi-descer. For instance, describe your character's facial features (but no clothes yet), calling it BASIC. Then, create a second description containing only your character's clothes, calling it something like CLOTHES. Then, you can use '+desc/get BASIC CLOTHES', and it will install both descriptions, with BASIC coming first and CLOTHES coming next.
These commands provide a front-end to the +desc system by storing descriptions in categories you create, called types. You may designate which types (in which order) to display (+desc/types), and then just switch one item without having to remember all the others (+desc/set).
To create, delete, and display descriptions of the given type:
+desc/create <type>/<descname>=<desc> +desc/delete <type>/<descname> +desc/show <type>/<descname>
To list the types you have defined, or descriptions of the given type:
+desc/list desctypes +desc/list <type>
To designate which type(s) to show, and in which order:
+desc/types <list of types>
To designate which one of each of the types to set or clear:
+desc/set <type>/<descname> +desc/clear <type>
+dtw
Syntax:
+dtw
Displays current IC and RL time, as well as information about the moons, tide, and weather.
Note: RL time uses the &TZ attribute (-24 to +24) and defaults to EST/EDT (-5/-4) as appropriate if no &TZ is set.
See also: +date +time +weather +tide +moons
+events
Syntax:
+events[/tz] - List all future events. +events/upcoming[/tz] - List events in the next week. +events/past - Lists expired events. +event <#> - Views details for a particular event.
+event/add[/tz] <title>@<location>@mm/dd/yy@hh:mm=<description>
+event/edit[/tz] <#>=<title>@<location>@mm/dd/yy@hh:mm=<description>
-Adds (or edits) an event with the given title, location, date, and time (either 24-hour "hh:mm" or "hh:mm pm")
+event/duration <#>=<duration> - Sets duration (default 1 hour)
-Duration example: 2h 30m
+event/announce <#> - sets heralds to announce a particular event. +event/unannounce <#> - removes herald announcements for the event. +event/delete <#> - deletes an event.
+events/auto - Toggles automatic +events/upcoming/tz on login.
The +events code lets players manage a calendar of events. Times given are in RL Eastern Time (ET). If you have a &TZ attribute set, you can add, edit, or display upcoming events in your local time zone with the /tz switch. Anyone may add an event, but only Admin may set an event to be announced by heralds. (Other players should submit a +ticket to request this.) Admin and the submitting player may remove announcements, edit, or delete events.
+facticket
Factions have their own database in the +ticket system. For all of the commands, <f> represents the faction abbreviation: for example, +gfticket will access the Green Fields ticket system.
Any player can submit a ticket with:
+<f>ticket <subject>=<request>.
Faction heads have access to the below additional commands by default. Other players can be set up to view by request.
+<f>tickets ............................... See all unfinished tickets. +<f>tickets/new ........................... Shows new unclaimed tickets. +<f>tickets/done .......................... Shows completed tickets. +<f>tickets/review ........................ Review just your own tickets. +<f>tickets/review <name> ................. Review's <name>'s tickets.
+<f>ticket/claim <ticket-id> .............. Claim a particular ticket. Sends a @mail to submitter and closer. +<f>ticket/unclaim <ticket-id> ............ Release a particular ticket. +<f>ticket/close <ticket-id>=<message>..... Set a ticket as Done. Sends a @mail to submitter and closer. May include an optional <message>, which is included in both the @mail and the ticket notes. +<f>ticket/open <ticket-id> ............... Set a ticket as New. +<f>ticket/delete <ticket-id> ............. PERMANENTLY DELETE a ticket.
+<f>ticket <ticket-id> .................... Shows details for a ticket. +<f>ticket/comment <ticket-id>=<text> ..... Puts a comment into the detail.
