Common Staff Commands

Adding new residents

Use addpl <name> to add someone to the Igen Weyr parent. This will do the following:

  • add the Igen Weyr FO to their character
  • send them a welcome @mail
  • add [Desert Discourse] and [Desert Raiders] to their @channels list
  • @subscribe them to *Igen Weyr and *Igen Intros
  • @sethome and @resident them in the Resident Terraces, unless they already have a .home property set (i.e. a specific room or another area's resident default)
  • @ltitle them to "Igen Weyr Weyrfolk", unless they already have a customized title
  • Please note: you will need to manually use @ltitle to conform their title to the IGW title pattern. See below for more information on how to do that.
  • To add to the wiki roster, the instructions to do so can be found here

Use delpl <name> to remove anyone if need be.

Living Arrangements

If a character needs to be @residented anywhere else in the Weyr, you'll need access to the IgenBldr. (Unless the desired room is owned by someone other than the builder, in which case, that person will need to @resident the character.)

Rank and Title

If a character is to have a position other than the default resident, make sure you promote <name> to <newrank> to make sure we're keeping things nice and tidy. For a list of available ranks, type rlist.

@ltitle <name> to <title> will change person's title. Please try to follow the title conventions, which are generally "IGW" followed by the specific title. For a list of all current titles, use clist all or cinfo all. @ltitle does not send an auto-mail.

  • When a resident is first added to Igen, even if they are going to be titled as Weyrfolk, you will need to use @ltitle <name> to "IGW Weyrfolk" in order to make their title match those of fellow Weyrfolk.
Reskin

When players want to reskin or change the names of their characters, they must be removed from the area before the request can be completed. Inform the player of the process, remove them from the area using delpl <name> and then submit the @rubyq reskin request.

Staff Bits

@addstaff <name> will add someone to the parent as a staff member. This will put them on the staff channel and add them to *igenstaff.

@delstaff <name> to remove from staff.

Mailers

addre <name> to *mailer (or #dbref of mailer). If you don't have authorization to do so, you may need builder access or have your name added as a .writer of said *mailer.
delre <name> from *mailer will remove them as a reader.
delwr <name> from *mailer will remove them as a writer.

Important Note: whenever editing properties manually (using ; or @set), make sure you are logging what you're doing.

For new general Igen *mailers, be sure to @set mailer#.writers to 0. If a new *mailer is to be moderated, be sure to set the .reader and .writer properties. You can use the addre and delre commands above, or manually edit the properties with @set.

  • @readers *mailer will show the names of the subscribed, readers, and writers.
  • @show *mailer.readers and/or @show *mailer.writers will show the list of characters' dbref#s. (You can also use the mailer's dbref#.
  • The list in both methods above should align in the same order, which makes it easier to see which numbers should not be in the properties.
  • In order to manually edit this list, use:
    • @set mailer#.readers to {list} or @set mailer#.writers to {list} (or)
    • ;mailer#.readers = {list} or ;mailer#.writers = {list} (if using the builder)
    • It is crucial that you include the squiggly brackets when you input and/or copy & paste the new list, otherwise things will break. If you forget, no harm done. Just @set it again, properly.
Area Message of the Day

To edit the Igen MOTD (Message Of The Day), you must use the builder, then @notedit #25222.motd to enter the editor. Type cmotd to view the current or updated message. (Don't forget to type save.)

Help Files

Weyr help is on #14597. To make a help file, first log on as the builder. @prop #14597.<helpfile> {} will give you an empty file to work with. @notedit #14597.<helpfile> to edit that file. To edit the help file that comes up when people type help igen, use the builder to @notedit #113.igen.

Public Rooms

@set here.outside_room to 1 to make a room outside, @set here.outside_room to 0 for indoor rooms.

@set here.want_vis_moon to 1 to show moon cycles in the room desc.

@setarea to 28

For the wiki helpfile, @notedit here.help_msg and then paste in the following:

del 1-69

and then:

"The wiki code for this room is:
"
"[[f>image /igen-room-images/FILENAMEFORROOMHERE.jpg]]
"
"For more of Igen Weyr's help files, type:  'help igen' for a list of topics!
New Weyrs and Private Rooms
Rider Weyrs & Ledges

To create a new weyr and ledge for a new rider or senior weyrling, you will need access to the builder. Move to the rider's preferred weyr location and type @make-ledge for <rider name>. This will create both a ledge and weyr for said rider, then automatically @chown the rooms to that rider.

  • They will need to @rename the weyr, as it defaults to "dbref#'s weyr".
  • You will also need to use @setarea for both the new weyr and the new ledge. (See below.)
Weyrling Couches

Standing in the weyrling barracks, makecouch for <weyrling> i.e. makecouch for Th'bek. Using the command @exits will show the hidden exits. The command automatically @chowns the couch to the weyrling, you just need to remember to @setarea inside the couch, as it defaults to Southern Weyr.

Goldrider Weyrs and Ledges

To create a new goldrider's weyr and ledge, move the builder to the Leadership Ledges (#12841). Use @make-ledge as above, using the goldrider's name. Have the goldrider @rename their "Fly" exit to "Ledges" if they'd like, otherwise the default is fine.

  • If they would also like an exit to Sky Above North Bowl, have them rename their existing Fly exit to "Ledges", then coordinate with them to temporarily @chown their new ledge.
  • @dig Fly to #23590
  • @set the ledge #.c to 1 and ask the rider to @chown it back to themselves.
  • The exit messages may need to be modified. They can be seen by typing @messages #, where the # is for the exit object. ("<dra> Dragonth's Ledge", "Fly", "Ledges", etc.) To edit, they can use @oarrive # is "new text".
  • They will need to @rename the weyr, as it defaults to "dbref#'s weyr".
  • You will also need to use @setarea for both the new weyr and the new ledge. (See below.)
Ghostweyr Residences, Riders and Non-Riders

To create a new Ghostweyr residence for a Rider, move the builder to the Lake Shore (#9331). Use @make-ledge as above, using the rider's name. Have the rider @rename their "Fly" exit to "Weyrs" if they'd like, otherwise the default is fine. For a non-rider, use @addnewroom <characterName> to here.

  • If they would also like an exit to Sky Above Lake, have them rename their existing Fly exit to "Weyrs", then coordinate with them to temporarily @chown their new ledge.
  • @dig Fly to #17148
  • @set the ledge #.c to 1 and ask the rider to @chown it back to themselves.
  • The exit messages may need to be modified. They can be seen by typing @messages #, where the # is for the exit object. ("<dra> Dragonth's Ledge", "Fly", "Weyrs", etc.) To edit, they can use @oarrive # is "new text".
  • They will need to @rename the weyr, as it defaults to "dbref#'s weyr".
  • You will also need to use @setarea for both the new weyr and the new ledge. (See below.)
Crafter Rooms

For apprentices, ask them if they would like to live in the general resident dorms or the Apprentice Dorms (#4237). If they do want to live in the apprentice area, use the builder and type @resident [name] while in the dorms, then ask them to move there and @sethome. If they wish to remain in the general dorms, nothing additional should be necessary.

(To remove someone from the .residents list for a room, you can do it manually, or go to that room and type @resident ![name]

To create a private room linked to the Crafter Quarters (#1298), log into the builder and use @addnewroom <characterName> to here. The room and its exits will automatically be @chowned to the character. You will still need to use @setarea. (See below.)

Whenever creating a new room, make sure to @setarea #dbref to 28 for Igen Weyr, or whichever choice is more appropriate for that room.

Dragon Details

The @wings/dwho/pair details are set by using @wingset <dragonname> <wing> <position> This does not send an auto-mail.

  • Normal wingrider example: @wingset Alphath Arroyo Wingrider
  • Special position example: @wingset Betath Arroyo "Ret. Wingrider" (quotes needed if position is more than one word)
  • Please note, the @wings command is set to arrange the order of riders according to their listed position. Using "leader" in the position (ex: Wingleader, Weyrleader) will put that rider at or near the top of the list, while "second" places the name in the next bracket down. "WLM" and "AWLM" will also auto-arrange.

Other Staff Guidelines

Staff Correspondence

Whenever you @send mail to an individual or a non-Igen *mailer on official staff business, always be sure to include *igenstaff so all staff members will know it's been taken care of, and what exactly was @sent.

  • For instance, if Foobie wants to know whether it's okay to keep her runner, Doobie, in the stables, @send both Foobie and *igenstaff about it. That way, an hour later another staffer won't spam poor Foo with it when she really just wanted Doo to have a roof over his poor old head.
  • When corresponding with Southern Staff or Game Staff, please make sure *igenstaff is included in the 'to' list.
Adding New Residents

The first step in adding a new resident is to nfo/+finger them. If they are a Traveler, go right ahead. Otherwise, make sure they've completed any other tasks that might apply according to Joining Igen, and that Staff Procedures have been met according to the Igen Staff Policies.

  • Encourage the new Igenite to @send *igenintros with an introduction to their character.
  • Remember to use the promote, @ltitle, and @wingset commands as necessary. In the case of a normal Weyrfolk character, '@ltitle <name> to IGW Weyrfolk'.
  • In some cases (transfer) an additional command may be necessary to assign a dragon to the Weyr: @weyrset <dragonname> Igen
Staff and Area Mailers

If you decide to clean out the staff or area *mailers (*igenstaff, *igen, or *igenintros), remember to log the original messages or @netforward them to yourself before you begin to @rmm any. That way in the event that something turns up missing that shouldn't be, there will still be a copy of it somewhere.

Area Help files

Each time you update or create one of the Igen help files, please remember to note at the bottom who updated the file and when. This way we'll have a better idea of what needs to be added/changed/removed since that date, and the person to contact in case there are any questions.

  • Example: (Last updated by Trek - 6 October 2014)
Code or Property Editing

It's a good rule of thumb to log whenever working on staff or area-related items, but if you are editing things manual using either @set or the ; shortcut (if on the builder), always log. If you make a mistake or miss something while using most of the other commands, there are super easy ways to fix it, or you can just use the command again. If you miss something and close the builder window, only to discover later that something is broken, this way you will have a record of what you did.

If you forgot to log, don't panic. There are still ways to fix things, but they require a lot more effort when done after the fact. Better to remember to log.


@Staff-Issues Verb

(With many, many thanks to T'ab for the original code, and to Ruby for resurrecting it from HT 1.0.)

Copied from help @staff-issues:

Usage: @staff-issue | @staffi

  • without any parameters will show the list of issues for the area staff.
  • with optional argument of 'on' or 'off', it turns on|off the notification on connect.
  • with optional argument of a #, it will record your comments.

Usage: @add|remove-issue | @addi/@remi

  • @add-issue/@addi: will prompt for the area you want to add a staff issue for, then will prompt for the issue's details.
  • @remove-issue/@remi: will prompt for the area you want to remove a staff issue for, then will prompt for the issue's number you want to remove.

Usage: @view-issue #

  • will prompt for the area of the issue you're trying to view, then will display the issue's details.

Before you remove an issue, be sure to first use @view-issue to gather all the information, including the original question, and each staff member response. Then @send or +mail the information to *igenstaff, otherwise the staff input will be lost.