.DT
playerinfo
$MUDNAME$ creator help
playerinfo
.SH Name
.SI 5
playerinfo - Access the player information database.
.EI
.SH Syntax
.SI 5
playerinfo list
playerinfo <player-name> [<event-type>]
playerinfo list alerts [online]
playerinfo <player-name> acknowledge [as <event-type>] <event> <update>
.EI
.SH Description
.SP 5 5
Playerinfo is used to print out the player's dossier. This information is
mostly useful for liaisons who want to check the player's behavior history,
punitive measures, item replacements and so on. For each entry in the dossier
the following information is provided: type of the event, time when the event
was recorded, name of the creator who added the entry, and an arbitrary text
describing what happened. Most recent entries are displayed first.
In the special case of "alert" type events, The player will show up (to
creators only) on the login inform:
> [%^GREEN%^Gumboot enters Divided Sky %^BOLD%^%^RED%^1 alert%^RESET%^]
This alert may then be "acknowledged". If the type is not specified, it
will go onto their dossier as a "misc" event. You can specify the type
by using this syntax:
playerinfo <player-name> acknowledge as <type> <event-number> <update>
When you acknowledge an alert, the original information about who added
it and when, and what they said will remain, so all you need to do is
explain what you did to resolve the alert (rather than having to
paraphrase the original as well).
You can also list the players who have alerts with "playerinfo list alerts",
or list only those who have alerts and are currently online, with
"playerinfo list alerts online".
The player whose dossier is being printed doesn't have to be online. If the
optional event argument is provided, only entries of this type are printed.
The following events are generated automatically:
.EP
.SO 8 20 -25
replace Item replacement; generated by Presto's wand
gag Gagging and ungagging; generated by the gagger
suspend Player suspension; generated by the "suspend" command
meteor Nuking; generated by the "meteor" command
multiplay Cases of multiplaying; generated by the multiplayer handler
refresh Partial or complete refreshes; generated by the refresh handler
.EO
.SP 5 5
The following events can be added manually using the "addevent" command:
.EP
.SO 8 15 -25
replace Replacement of items that are not on the wand
harassment Cases of harassment
misc General information that doesn't fit in any of the above categories
discipline General comments done with regards to discipline
alert As explained above
.EO
.SP 5 5
To print all events supported by the database, use "playerinfo list".
.EP
.SH Notes
.SP 5 5
1. The "replace" events expire after 30 days.
.EP
.SP 5 5
2. The player information database doesn't contain events that happened
before it was implemented.
.EP
.SP 5 5
3. If a player deletes, their playerinfo dossier will not be updated.
Someone with the correct write access should delete their playerinfo file
and clear their alerts.
.EP
.SH Examples:
.SI 5
> playerinfo pinkfish
Report for: Pinkfish
16. Sun Nov 1 09:56:18 1998 harassment (added by Fiona)
Made me code this playerinfo database.
.SI 5
> playerinfo macchirton gag
1. Mon Nov 2 07:40:52 1998 gag (added by Presto)
For being unable to fix his spacebar.
.EI
.SI 5
> playerinfo lagger
Report for: Lagger
1. Wed Nov 10 12:17:05 1999 alert (added by Shrike)
Please remove this player's nipples when he logs on next.
He stole them from Pinkfish's pantry.
> playerinfo lagger acknowledge as discipline 2 Ok. Surgically removed his
nipples, and also took his pants for good measure.
Event acknowledged.
> playerinfo lagger
Report for: Lagger
1. Wed Nov 10 12:19:37 1999 discipline (added by Pinkfish)
Originally added by Shrike at Wed Nov 10 09:56:22 1999:
Please remove this player's nipples when he logs on next.
He stole them from Pinkfish's pantry.
---
Ok. Surgically removed his nipples, and also took his
pants for good measure.
.EI
.SH See also
.SP 5 5
addevent, delevent, addalt, delalt
.EP
