Stendhal:GuideForAdmin: Difference between revisions
Content deleted Content added
imported>Kymara No edit summary |
imported>Hendrik Brummermann No edit summary |
||
| (102 intermediate revisions by 3 users not shown) | |||
Line 1:
{{Navigation for Stendhal Top|GMs}}
{{Navigation for Stendhal GMs}}
Being an admin on a server with many users is not easy, so firstly, thank you. Thank you very much.
This guide is aimed to be helpful to admins on the main game server,
Commonly used commands are summarised, with examples given, at [[Stendhal:Administration]].
== Admin role ==
If you just want to help players, for example those who:
; need information and don't know where to look
:point them to the correct source, this may be the wiki, website, or an NPC
Line 15 ⟶ 19:
; don't know the rules yet (e.g. think PVP is against the rules)
:educate on rules, point to source of information
then this can be achieved by taking the [[Stendhal Helper Role]].
Admins and helpers also help players who:
; have a technical problem
:a client glitch may be temporary: suggest they try relogging
Line 20 ⟶ 29:
:otherwise advise them to lodge a support request, or wait for an answer which may come later
; have lost their password
: See [[Stendhal FAQ#Passwords]], or below.
A big difference between an admin and a helper is that an admin can be expected to do detailed investigations when problems arise, they have access to some admin commands which are rarely needed, and admins are expected to use the /support channel for all communications with players regarding problems as this is logged.
▲In rare cases, direct intervention is needed (todo: link to Support: section)
== Answering /support==
===General guidelines===
It is essential to always use '''/supportanswer''' in response to a /support query.
* /supportanswer is logged to IRC and player history, the /msg is not
Line 32 ⟶ 44:
Do make use of the standard $ supportanswer responses, a list of which can be obtained with ''/gmhelp support''.
If writing your own
It's a good idea to familiarise yourself with the FAQ so that you can answer questions fast with it (and do look up the $faq shortcuts), and be consistent with game policy.
===Communication between admin===
===Bugs reported through support===
Bug reports are very helpful, and are roughly divided into three types. Suggested replies are given below. Politeness is emphasised because we really need players to feel willing to make bug reports.
:* not a bug, just a feature
::''Hi, what you have discovered is a feature of XXX and not a bug. But thank you for your time in reporting it anyway, as if it was a bug we'd need to know!''
:* a known bug which is already reported
:: ''/supportanswer $knownbug'' is ideal for this
:* something which sounds like a bug and probably isn't reported, so we would like a report
:: ''/supportanswer $bugstracker'' is ideal for this
In case a player just says 'help' or 'hello' or 'anyone here' then you can either:▼
:* Say ''Hi, please could you tell us specifically what you need help with? Thanks'' Or▼
:* ignore it▼
===Password resets===
If someone asks for a password reset then it can be done only if they originally signed up with a valid email address to a mailbox that they can access. So,
:1. For example, reply: ''Hi, your password can be reset if you signed up with a valid email address originally. Please wait for an email.''.
Line 51 ⟶ 66:
:<code>Hi, someone requested a password reset for the stendhal account XXX. This is the email address registered for that account.</code>
:<code>Please do the following things:</code>
:<code>1.
:<code>2. Tell support this message :</code>
:<code>/support Hi
:<code>3. Wait. A server admin will be asked by someone from support to
:<code>Thanks</code>
:<code>adminname</code>
:3. When the support message is received, any admin needs to please comment on the tracker item that was created. The server admin who sent the email will confirm that the created account name matched what was in the email (YYY). This acts as the check that the email was read, i.e. the person requesting the pw change is the one who owns the account. They will then change the password and close the request.
===Misc cases ===
▲In case a player just says 'help' or 'hello' or 'anyone here' then you can either:
▲'''Communication is very important between admin'''. Please make sure you join the IRC channel when you are in the game in a support capacity. If you start to answer support questions and have not joined the IRC channel already, please join asap. For example, if you deal with a support question in person because you are there already then please send a quick message to /support so that the other admin know that they don't have to deal with it. Likewise if there is an issue which needs a decision from other admin, you need to tell the other admin about the issue. Preferably tell them before the issue is raised again so there is time for discussion. Finally if something needs extra attention and noone else is around to respond, please create a new [https://sourceforge.net/tracker/?func=add&group_id=1111&atid=201111 Support Request].
▲:* Say ''Hi, please could you tell us specifically what you need help with? Thanks'' Or
▲:* ignore it
== Hacked account ==
Line 76 ⟶ 93:
Situation 1: Player x rented a sign with: "Admins please help, player y stole my items!"
:*"Hi all! In response to a sign from a player asking admins to do something about thieves: Sorry to read about stealing, but this is an issue admins don't intervene in. For trading please use
Situation 2: Player x rented a sign which is including insults in relation to player y like "player y is stupid and dumb!"
Line 93 ⟶ 110:
== Teleport use ==
Most problems are possible to answer using /support and this is logged, so teleport is rarely needed.
Please only teleport to a player if you need to
In some cases, it is better to observe the situation without interacting.
For non player admins who need to go fast to bank, or DM, first teleportto Skye then walk through one of her clever portals.
== Your conduct ==
As an admin it is important to set a good example to other players. This certainly means you should not be breaking any rules yourself. It is strongly preferable that you do not attack and certainly do not kill other players. If you have clone accounts which most people know belong to you, you should apply the same rules of conduct to them as you do yourself - players do not differentiate between the play-only and the admin characters. Of course, you would not have been chosen to have adminlevel if you weren't already a nice person who behaved well, but it is worth noting these things 'officially'. Also remember, that we admins are not there to solve personal problems between two players. If there is the case that two are having a personal revenge and doing something like stealing from each other corpses, admins should not interfere, neither with their admin chars nor with clones as that is against our admin rules. Also don't give items to players who complained about being robbed by someone with your admin chars/clones as it sets a precedent which isn't part of our admin role.
== Raids ==
It can be helpful to keep the [http://stendhalgame.org/creature/ creature page] open.
For players up to level 300, you should only summon creatures up to half the player level on top of a full health player. If summoning a Plague or using a script make this 1/3 or less.
Players above level 300 should cope with any level of creature or know what to do if not.
Please *destroy creatures have been summoned in error and are killing a low level.
You can on occasion summon a small number potions or a soup if you see that a player is defending against something too big for it but trying hard, do not do this too much please.
===Raid scripts===
Find out what is available with /script -list *Raid.class
Find out what players each raid is safe for with /script NameRaid.class any parameter
== See also ==
Line 104 ⟶ 147:
*[[Stendhal:Administration]]
*[[Stendhal:Scripts_For_Admins]]
*[[
<br>
| |||