Difference between revisions of "Exodus"

From Immwiki
Jump to: navigation, search
m
(Misc Command Info)
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
This page is for adding miscellaneous notes on imm commands, because Dov's memory sucks.
 
This page is for adding miscellaneous notes on imm commands, because Dov's memory sucks.
  
== Misc Command Notes & Info ==
+
== Connection Stats ==
 +
 
 +
http://www.avendar.net/bible/loginstats.php
 +
 
 +
== Misc Command Info ==
 +
* see: help immcommands
 
* [[Bans]]
 
* [[Bans]]
 
* [[trait info]]
 
* [[trait info]]
 
* [[new imm stuff]]
 
* [[new imm stuff]]
 
* %R - prompt variable for current room vnum
 
* %R - prompt variable for current room vnum
* notify stuff - see "help immnotify" (mostly nonfunctional now--2012)
+
* notify stuff - see "help immnotify" (mostly nonfunctional since at least 2012)
 
* to set skills, use "set skill <name> <group> <value>"
 
* to set skills, use "set skill <name> <group> <value>"
 +
* Rand_progs fire once every 4 seconds.
 +
 +
== Note tricks ==
 +
Syntax: note faketo <line>
 +
 +
Syntax: note sigil####
 +
 +
Syntax: note level##
 +
 +
 +
Imms have the ability to have a fake "to" line that mortals will see instead of the regular to-list.  Notes with faketo lines cannot be responded to with replyall (unless you're an imm).
 +
 +
You can put sigil#### in the to-list of any note to send the note to any people with that sigil.  You should always use a faketo line if you're using this feature.
 +
 +
You can put level## in the to-list of any note to send the note to all people at that trust level or above.  You should always use a faketo line if you're using this feature.
 +
 +
So, for example, Aeolis could do something like:
 +
 +
note to sigil1290
 +
note faketo Followers of the Rose
 +
 +
And mortals would just see:
 +
 +
To: Followers of the Rose
  
  
Line 21: Line 50:
  
 
=== Desc & BG Review ===
 
=== Desc & BG Review ===
 +
<i>badscan's natural / badscan's good / not everybody does it / but everybody should</i>
 +
 +
Actually this is not required now that the pbase is so small and all imms can review all PCs. Dov, being old fashioned, still uses these. :)
 +
 
* badscan [app] - list of chars w/out approved desc or bg
 
* badscan [app] - list of chars w/out approved desc or bg
 
* bg view [name] - shows character's background
 
* bg view [name] - shows character's background
Line 28: Line 61:
  
 
=== Misc Prod Monitoring ===
 
=== Misc Prod Monitoring ===
 +
* rumors - shows all rumors in the rumor pool
 +
* oath list all - shows all active oaths
 
* brand [name] [vnum] - brand with a sigil. To remove, unbrand [name].   
 
* brand [name] [vnum] - brand with a sigil. To remove, unbrand [name].   
 
* brand [name] [vnum] prog - set a prog item on a char.  To remove, unbrand [name] prog.
 
* brand [name] [vnum] prog - set a prog item on a char.  To remove, unbrand [name] prog.
 +
* set skill [charname] [group] [amount] (eg set skill 'minor water' 100) - sets all skills in that group to that amount
 
* note list [name] - read their mail
 
* note list [name] - read their mail
 
* note read [name] x - more mail fraud
 
* note read [name] x - more mail fraud
 
* stat [charname] symbols - shows all void symbols that character has
 
* stat [charname] symbols - shows all void symbols that character has
* stat [offline] [charname]  - ''use with caution if at all, known to crash the MUD''
+
* stat [offline] [charname]  - ''don't use, crashes the MUD''
 
* prac char [pcname] - in same room as pc, shows pc practice list
 
* prac char [pcname] - in same room as pc, shows pc practice list
  
== Imm Rules ==
+
 
/---------------------------------------------------------------------------\
+
|          Immortal Rules                                                  |
+
\---------------------------------------------------------------------------/
+
+
Guidelines for IMMs
+
+
The following rules should be blindingly obvious.  If they are not obvious
+
to you, you might want to contact us to have yourself denied.  If you have
+
any questions about any rule listed here, or other guidelines upon which you
+
are uncertain, talk to other staff members or implementors.  We are here to
+
help one another when we can! 
+
+
1.  Be cautious with your immortal abilities. 
+
+
Giving out equipment, taking it away, usage of slay, healing, transferrance,
+
buffs, and so on should be used responsibly.  If you are unsure what to do
+
or if your action is appropriate, consult other prod immortals for help.
+
Even experienced immortals sometimes misjudge these things, so you should
+
assume you don't know enough to make the call alone.  If you can solicit
+
mulitple opinions, do so.  Remember that what actions you take, both ICly
+
and during OOC enforcement, reflect on all members of Avendar's staff and
+
act accordingly. 
+
+
2.  Favoritism is not permitted. 
+
+
There will be no favoritism of any kind.  You should not choose to roleplay
+
or reward the characters of your OOC friends.  In most cases, another prod
+
immortal will be available to handle cases in which you personally cannot be
+
impartial.  This works two ways: for when you deal with someone who you
+
disproportionately favor, and when you deal with someone you have an OOC
+
grudge with.  Ensure that if you must interact with such people, that you do
+
so as sparingly as possible, and be ready to justify any rewards,
+
compliments, or assistance you may have given them to your fellow staffers.
+
Anything you do with a mortal should be logged with that character's player
+
data. 
+
+
3.  Do not aid your own characters in any way. 
+
+
This is a very important rule and one that must be adhered to at all times.
+
This has a broad scope.  If you are building a new area, do not be the first
+
one to "explore" with a mortal and "find" the awesome items you may have
+
made.  Secondarily, do not utilize your imm powers, such as looking for
+
items, looking at opposing or allied PCs, looking for hiding places of your
+
foes, or other such things.  It is extremely obvious when you suddenly gain
+
a sixth sense for everything your opponents will have, say, and do, and it
+
will result in your removal.  You have been warned. 
+
 
+
4.  Do not abuse bugs at any time for any reason. 
+
+
As a member of staff, you often have access to priviledged information.
+
This may be bug reports, code access, area access, or just plain snooping
+
around on dev in your off time.  It is very likely that in the process of
+
these things, you will uncover "features" that aid you, such as money
+
exploits, prog errors, or code bugs.  If you exploit any of these, for any
+
reason, at any time, consider yourself finished.  You are trusted, and
+
abusing that trust is a fast track to being permanently removed. 
+
+
5.  Assist new players via the newbie channel. 
+
+
Getting and retaining new players is difficult, and we want to help people
+
enjoy their time playing Avendar.  If you have access to prod and you see a
+
question asked, you can and should respond to it.  Sometimes people will ask
+
questions which you obviously cannot answer, such as a quest puzzle
+
solution; this, you do not have to answer and you should say as much.
+
However, if someone asks a straight-forward question about mechanics (such
+
as, "what does constitution do?"  ), your first response cannot and should
+
not ever be PAFO.  Basic mechanics are outlined in help files, so if you are
+
unsure as to an answer, you can direct them to the relevant part of the
+
system.  If said helps are incorrect or there are questions, consult other
+
staff members to ensure correct information is given. 
+
+
6.  Be professional in your public interactions. 
+
+
When posting on the forum, using the newbie channel, or on IRC, remember
+
that you represent Avendar's staff.  This means you should not be publicly
+
belittling players, other staffers, or other MUDs.  Whenever possible, you
+
should do your best to be positive.  If you find yourself posting something
+
negative, insulting, or unnecessary, you should expect to hear from your
+
fellow staffers not to do this.  If you post telling players to PAFO or
+
otherwise being dismissive, you will be reprimanded.  If possible, staff
+
members need to cooperate to achieve the best possible results.  If you are
+
having problems with another member of staff, talk to an implementor. 
+
+
7.  Interact with mortals when possible. 
+
+
If you have access to prod, you have proven that you are a capable
+
roleplayer and have a wide breadth of knowledge regarding the game world.
+
This means that if you are looking for something to do, you can interject
+
yourself into player situations.  Those people standing in Center Square
+
might like the opportunity to chat with an interesting mob.  That said, if
+
you can avoid it, do not interject yourself into PC combat scenarios.  If
+
characters are ranking, unless they are truly over the top about it, do not
+
interrupt them to give them a "challenge".  Remember that ultimately, your
+
role is to assist players in developing their personal stories, as well as
+
broader story arcs. 
+
+
8.  Watch for cheating. 
+
+
Use wiznet to watch reconnection times, look for item passing when you see
+
suspiciously powerful or well-armed low level characters, as well as for
+
login-coordination.  Remember that often these things require a pattern to
+
truly stick, and people will always deny what they have done when
+
confronted.  If you are unsure of if something counts as cheating, or if you
+
feel a behavior is lame or questionable, first check the rules for yourself.
+
If you are not satisfied, consult other staff members or implementors to
+
determine the best course of action. 
+
+
9.  Watch for roleplay. 
+
+
This can consist of both good RP and bad RP.  If you see the goodie water
+
scholar slaughtering babies wholesale, you need to note this.  Conversely,
+
if you see someone putting a lot of effort into their role, you should note
+
it and see the standing of their account.  By the time you see someone with
+
3-5 account points, they have already proven that they are consistently able
+
to roleplay.  Giving out points should not happen for such reasons as "this
+
person said a funny line", or "this person made a race/class combo I like",
+
or "this person is an immortal".  If you are an immortal, your characters
+
should handily prove themselves without such assistance.  If someone is
+
definitely violating some part of their role, consult other staffers or
+
implementors for how best to handle them IC. 
+
+
10.  Develop player or staff resources. 
+
+
The easiest way to do this is build, but not everyone is a good builder.
+
This can take the form of helping with the website, making original art,
+
polishing or formatting the staff wiki, or writing documents that will help
+
players develop their roles.  ICly, this can be in the form of books or
+
in-game texts.  OOCly, this would include the development of help files,
+
race documents, area overviews, OOC histories, or god-related write-ups.
+
There is a huge variety of things that are needed, so if you are unsure of
+
what to do, or you feel there is a niche yet to be filled, speak up and see
+
what sort of help you can give. 
+
+
 
[[category:Exodus]]
 
[[category:Exodus]]

Latest revision as of 20:49, 5 March 2016

This page is for adding miscellaneous notes on imm commands, because Dov's memory sucks.

Connection Stats

http://www.avendar.net/bible/loginstats.php

Misc Command Info

  • see: help immcommands
  • Bans
  • trait info
  • new imm stuff
  •  %R - prompt variable for current room vnum
  • notify stuff - see "help immnotify" (mostly nonfunctional since at least 2012)
  • to set skills, use "set skill <name> <group> <value>"
  • Rand_progs fire once every 4 seconds.

Note tricks

Syntax: note faketo <line>

Syntax: note sigil####

Syntax: note level##


Imms have the ability to have a fake "to" line that mortals will see instead of the regular to-list. Notes with faketo lines cannot be responded to with replyall (unless you're an imm).

You can put sigil#### in the to-list of any note to send the note to any people with that sigil. You should always use a faketo line if you're using this feature.

You can put level## in the to-list of any note to send the note to all people at that trust level or above. You should always use a faketo line if you're using this feature.

So, for example, Aeolis could do something like:

note to sigil1290
note faketo Followers of the Rose

And mortals would just see:

To: Followers of the Rose


Prod Monitoring

Accounts & Dataing

  • acl - list of account points for current chars
  • award [name] [points] [reason] - gives account points (can use negative values)
  • showdata [name[ - character and account info
  • data [name] [info] - add a note about the character
  • acctdata [name] [info] - add a note about the account/player


Desc & BG Review

badscan's natural / badscan's good / not everybody does it / but everybody should

Actually this is not required now that the pbase is so small and all imms can review all PCs. Dov, being old fashioned, still uses these. :)

  • badscan [app] - list of chars w/out approved desc or bg
  • bg view [name] - shows character's background
  • desc view [name] - as above, for descs
  • approve [bg/desc] [name] - toggles approval status


Misc Prod Monitoring

  • rumors - shows all rumors in the rumor pool
  • oath list all - shows all active oaths
  • brand [name] [vnum] - brand with a sigil. To remove, unbrand [name].
  • brand [name] [vnum] prog - set a prog item on a char. To remove, unbrand [name] prog.
  • set skill [charname] [group] [amount] (eg set skill 'minor water' 100) - sets all skills in that group to that amount
  • note list [name] - read their mail
  • note read [name] x - more mail fraud
  • stat [charname] symbols - shows all void symbols that character has
  • stat [offline] [charname] - don't use, crashes the MUD
  • prac char [pcname] - in same room as pc, shows pc practice list