Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

User:Kelaris/Sandbox3: Difference between revisions

From The Den Wiki
 
(56 intermediate revisions by the same user not shown)
Line 1: Line 1:
{| class="wikitable"
== Adminstration of the Den ==
|+Subdocuments
Our volunteer team of moderators and administrators exist to maintain and contribute to the community direction goals of the server. They do this primarily through the ticket system and the in-game Admin Help (Ahelp) menu, either in response to a user request, complaint, or concern, or as a corrective action in response to behaviors observed to be outside the scope of our community rules and guidelines.
|-
|[[Alert Procedure]]
|-
|[[Command Hierarchy]]
|}


== Command Standard Operating Procedure ==
Team members typically use these systems to discuss with players matters of server expectations, concerns they may have over IC and/or OOC actions, and complaints levied against specific behaviors. Involvement in these systems does not imply that there will be punitive or corrective action; Communication is always the first step, and in the majority of cases, is often solely sufficient.


=== Captain or Acting Commanding Officer ===
In an effort to be as transparent as possible with how the Den is operated, here are some major points of interest regarding the expectations and standard procedure of those those entrusted with overseeing its safety and operation.
The Captain is the legally appointed officer by Nanotrasen in charge of the station, and is the final word in all station affairs, unless Central Command becomes directly involved. Captain is the formal title, while the legal title is ''Commanding Officer'' or '''CO'''.  


The title of Acting Commanding Officer may only be taken on by the Executive Officer, in the event of no Captain being present, or the Captain becoming incapacitated or otherwise unavailable to lead the station. It is not mandatory for members of command to take on the role of Executive Officer/Acting Commanding Officer in the absence of a Captain, but it is encouraged when possible.
== Our Stance on Actioning Players: ==
When a situation is brought to our attention, unless someone was harmed in some way or repeat behavior has occurred, we try to simply have a discussion, inform players of expectations, and ask them to modify behavior that may be disruptive or harmful.


The Captain's primary duty is to ensure the safety and survival of the crew aboard their station. Their secondary duty is to ensure the safety and security of the station itself and its assets. Their tertiary duty is to ensure the smooth operation of the station's various departments. To this end, the Captain should be capable of operating and leading all departments at a passable level of proficiency, to ensure the continued operation of the station in the event of departmental staff shortages.
We try to err on the side of leniency whenever possible, but ultimately the safety and comfort of the entire community has to be considered. For severe, repeating, or unresolvable issues, action tends to scale up rapidly.


===== Captain's Authority: =====
== Our Stance on Admin Intervention in Rounds: ==
Due to the complex and unpredictable nature of events that may unfold on any given shift, the Captain (or ACO) is given the right to modify Space Law, Standard Operating Procedure, and Alert Procedure ''when necessary''. Any modification must be announced to the station, and Central Command should be notified of the deviation as soon as possible. Abuse or misuse of this authority will have severe consequences.
Admins usually try to let the round play out naturally. However sometimes we do interfere to either solve mechanical problems, enable RP interactions and situations, add small events for variety, or intervene in some way to allow the round to continue when it would otherwise end (destroying a tesloose, sending ERT, etc).  


=== Executive Officer ===
We welcome players making the occasional request for assistance and small events for their own RP goals, and as long as it is kept private or is not too disruptive to the station, we can usually accommodate the request.
The Executive Officer (XO) is any member of command selected by the Captain to function as a second-in-command of the station. Under normal circumstances, with the Captain available and on-station, the XO has no additional authority or duties. However the XO may be delegated tasks and situations to handle by the Captain, or take independent action to preserve the safety of the station and crew during life threatening emergencies.


In the absence of a Captain, the XO is chosen by majority vote of all departmental heads, and the result of this vote must be faxed to Central Command. Afterwards the elected XO will immediately become the station's Acting Commanding Officer, until an officially appointed Captain arrives to take command of the station. The title, access, and equipment of the XO are not immediately revoked by the arrival of the Captain, but may be revoked and a new XO selected at any time if the Captain chooses.
== How Are Ahelps and Tickets Handled? ==
When an Ahelp or user ticket received, it is also relayed into chats accessible by all team members. An available team member that is also in a position to assist will either reply and attempt to handle the issue, or inform the issuing party that the message has been received and is undergoing review. In cases more complex than something like a simple item request, team members will discuss with one or more colleagues on how to proceed, with any potential concerns noted and weighed into the response.


The XO should equip the station's spare master encryption key, modify their ID to have all accesses, and include "XO" or Executive Officer in their title. At their discretion, the XO has the right to requisition and carry a sidearm of their choice on any alert level.
When tickets are created, a secondary channel is also generated to allow team members to discuss the ticket at hand, provide supporting evidence, logs, or relevant information to the discussion. Both the contents of the ticket and the investigation threads pertaining to the ticket are logged and preserved after its conclusion, for reference by Head Admins or Owners in the case of appeals or further required action.


Due to potential conflicts of interest and overlapping duties, the Head of Security and Administrative Assistant should only be considered for XO/ACO duties when no other Departmental Heads are willing to take the role.
Staff Complaints are visible exclusively to Head Admins and Owners, though there has been precedent for such a ticket to be delegated to the Senior Admin team for situations that need more opinions and do not require the highest confidentiality.


=== Departmental Heads ===
When handling a complaint regarding another individual, the identifying information of the person making the complaint is kept as obscured as is reasonably possible.
Departmental Heads are expected to have comprehensive knowledge of the function of their department, and must be ready and able to personally fulfill any task within the department as necessary. However their primary duty is organizing their department and ensuring that it operates smoothly.


Under normal non-emergency circumstances, departmental heads should attempt to delegate most of the hands-on work to other members of the department, and focus their own efforts on teaching and coordinating.
== What Information Does the Admin Team Have Access To? ==
As a ghost in the round, admins can see all of the same things normal ghosts see, and can not see subtle, whisper, or subtle ooc, and can interact with the world in a limited fashion (picking up or dragging things, interacting with consoles, using tools, etc).  


=== Administrative Assistant ===
With a search through the logs, which is only done when investigating issues or complaints, admins can see all actions, every chat and every emote from all channels that have occurred on any round. These logs are accessible by all admins, but are time consuming and unwieldy to sift through, and only intended to be used for troubleshooting and investigation. At manual intervals, logs older than approximately 1000 rounds are deleted.
The Administrative Assistant (AA) is a full member of command, and is intended to act as a coordinator and communicator. The AA's primary duty is managing information and relaying that critical information to command, departments, and the crew. Their secondary duty is to assist in any department, or with any task as requested by the Captain, XO, or department heads.


The AA has a level of access second only to the Captain and XO. However this access is never to be used to do the job of any department, unless specifically requested by the relevant departmental head, the Captain, or the XO.
Headmins and Owners have the capability to retrieve replays of any round on the server if needed, and may provide a replay for use in an investigation with a documented request from other members of the team.


The AA is especially forbidden from independently acting as security or an investigator for security, or granting security personnel access to departmental restricted areas without permission or request from the relevant department head, Captain, or XO. During red alert or higher, the AA may use their access to grant free movement through the station to security personnel if necessary.
== Joining the Admin Team: ==
Our applications are always open, and an application may be submitted to indicate a standing interest in joining the team, on the Staff Applications forum of our Discord.  


== Emergency Access ==
== A Final Note Regarding our Team: ==
The emergency spare ID is authorized for use by any member of command during emergency situations. Executive Officers are authorized to use this spare ID to update the accesses on their own ID card to all-access. However, the spare ID should be returned and locked in its container under normal circumstances.
It is important to remember that team members do not void their desire or ability to participate in the game as a result of joining the administration team - They are both players and people, and volunteer their time freely to try and maintain comfort, safety, and ongoing consent for the community. Abuse of team members is not tolerated whatsoever; If you feel that a team member has made a mistake or acted inappropriately, you are encouraged to open a Management ticket or Staff complaint.  


== Combat Involvement ==
The Den is a collaborative space, and without active communication between team members and the community, it is impossible to effectively maintain these core values. If you have any questions or concerns, please let us know!
 
== Restricted Equipment ==

Latest revision as of 18:39, 11 May 2026

Adminstration of the Den

Our volunteer team of moderators and administrators exist to maintain and contribute to the community direction goals of the server. They do this primarily through the ticket system and the in-game Admin Help (Ahelp) menu, either in response to a user request, complaint, or concern, or as a corrective action in response to behaviors observed to be outside the scope of our community rules and guidelines.

Team members typically use these systems to discuss with players matters of server expectations, concerns they may have over IC and/or OOC actions, and complaints levied against specific behaviors. Involvement in these systems does not imply that there will be punitive or corrective action; Communication is always the first step, and in the majority of cases, is often solely sufficient.

In an effort to be as transparent as possible with how the Den is operated, here are some major points of interest regarding the expectations and standard procedure of those those entrusted with overseeing its safety and operation.

Our Stance on Actioning Players:

When a situation is brought to our attention, unless someone was harmed in some way or repeat behavior has occurred, we try to simply have a discussion, inform players of expectations, and ask them to modify behavior that may be disruptive or harmful.

We try to err on the side of leniency whenever possible, but ultimately the safety and comfort of the entire community has to be considered. For severe, repeating, or unresolvable issues, action tends to scale up rapidly.

Our Stance on Admin Intervention in Rounds:

Admins usually try to let the round play out naturally. However sometimes we do interfere to either solve mechanical problems, enable RP interactions and situations, add small events for variety, or intervene in some way to allow the round to continue when it would otherwise end (destroying a tesloose, sending ERT, etc).

We welcome players making the occasional request for assistance and small events for their own RP goals, and as long as it is kept private or is not too disruptive to the station, we can usually accommodate the request.

How Are Ahelps and Tickets Handled?

When an Ahelp or user ticket received, it is also relayed into chats accessible by all team members. An available team member that is also in a position to assist will either reply and attempt to handle the issue, or inform the issuing party that the message has been received and is undergoing review. In cases more complex than something like a simple item request, team members will discuss with one or more colleagues on how to proceed, with any potential concerns noted and weighed into the response.

When tickets are created, a secondary channel is also generated to allow team members to discuss the ticket at hand, provide supporting evidence, logs, or relevant information to the discussion. Both the contents of the ticket and the investigation threads pertaining to the ticket are logged and preserved after its conclusion, for reference by Head Admins or Owners in the case of appeals or further required action.

Staff Complaints are visible exclusively to Head Admins and Owners, though there has been precedent for such a ticket to be delegated to the Senior Admin team for situations that need more opinions and do not require the highest confidentiality.

When handling a complaint regarding another individual, the identifying information of the person making the complaint is kept as obscured as is reasonably possible.

What Information Does the Admin Team Have Access To?

As a ghost in the round, admins can see all of the same things normal ghosts see, and can not see subtle, whisper, or subtle ooc, and can interact with the world in a limited fashion (picking up or dragging things, interacting with consoles, using tools, etc).

With a search through the logs, which is only done when investigating issues or complaints, admins can see all actions, every chat and every emote from all channels that have occurred on any round. These logs are accessible by all admins, but are time consuming and unwieldy to sift through, and only intended to be used for troubleshooting and investigation. At manual intervals, logs older than approximately 1000 rounds are deleted.

Headmins and Owners have the capability to retrieve replays of any round on the server if needed, and may provide a replay for use in an investigation with a documented request from other members of the team.

Joining the Admin Team:

Our applications are always open, and an application may be submitted to indicate a standing interest in joining the team, on the Staff Applications forum of our Discord.

A Final Note Regarding our Team:

It is important to remember that team members do not void their desire or ability to participate in the game as a result of joining the administration team - They are both players and people, and volunteer their time freely to try and maintain comfort, safety, and ongoing consent for the community. Abuse of team members is not tolerated whatsoever; If you feel that a team member has made a mistake or acted inappropriately, you are encouraged to open a Management ticket or Staff complaint.

The Den is a collaborative space, and without active communication between team members and the community, it is impossible to effectively maintain these core values. If you have any questions or concerns, please let us know!