Sojourn - User contributions [en]

Server Policy

2025-05-09T22:20:00Z

K5: /* Staff Roles */ Rewrote the roles to more appropriately match their current incarnations.

{{Stub}}
This page's contents are being migrated to their respective pages. Contents may be outdated.
[[Category:Staff]]

{{SidebarStaff}}

== Staff Roles ==
''This section is out of date. Review the specific page for the role.''

=== Administrative Staff ===
Administrative staff handle all things to do with player activities on server. It is the role of the administration to determine where player actions contravene the server and to act to correct such instances.

==== Head Administrator ====
Head Administrators oversee the server as a whole, and act to maintain the administration rather than directly administering. If credible concerns of administrative bias are made, for example, a Head Administrator may assign a different admin to an unban appeal, or in rare cases handle it themselves. Head administrators also instruct Staff Heads on the direction the server should take.

While strongly discouraged when other staff are available, Head Administrators have the authority to step into '''any''' other role when the situation calls for it.

==== Administrator ====
Administrators rule on player situations that need more complicated solutions than fall within a moderator's prerogative. Excessive rule-skirting, undesired behaviour and other complex issues fall under the Administrators' purview. Administrators also act as agents in enforcing IC rulings where the High Council is involved, and respond to faxes with the full authority of the council.

Administrators are additionally responsible for the continued integrity of the in-game persistency, both by retroactively declaring incidents non-canon, or by accepting requests from players for permission to break major rules.

==== Moderator ====
Moderators act on straightforward issues involving player actions. Generally, this simply means enforcing rules as written in a cut and dry fashion, and helping collect information on situations that an Administrator would otherwise rule on. Moderators are the first line in ensuring that the server stays on track and appropriately in tone, but also first to grant exceptions to players for performing actions that would otherwise be minor rule violations.

Moderators do not act on behalf of the High Council when exercising their moderation powers, but may make informational responses to faxes as supporting staff to a specific councillor.

As moderators do not have some server permissions granted directly to them, many of their rulings may need to have an administrator rubber stamp them and apply them. If an administrator is unavailable, members of Oversight may enact their judgements as well.

=== Development Staff ===
Supporting staff handle all things to do with the server's state and development.

==== Staff Head ====
Staff Heads oversee the development of the server. Each one is given a specific family of tasks to oversee or maintain. Each staff head is either particular to Lore or Code tasks, and when there are four staff heads within either group, one of that group is granted the additional task of foreperson.

An additional, unique Staff Head role exists for maintaining the Rules. This role is also granted the powers and authority of an administrator, but is generally expected to focus on finding flaws in the rules and easing them out, over enforcing them, and to handle rule changes as dictated by headmins.

Staff Heads may respond to faxes regarding clear cut IC issues, in the same fashion as a moderator.

==== Staff Writer ====
A member of development staff, empowered with access to more sensitive pages on the Wiki, and tasked with organizing contributions within a certain subsection of Lore. Coordinates their particular interests with Lore Staff Heads.

==== Staff Coder ====
A member of development staff, empowered with access to debug utilities on the Server, and tasked with organizing code contributions. Coordinates their particular development focus with Code Staff Heads.

=== Showrunning Staff ===

==== Game Master ====
Game Masters are responsible for the bureaucratic elements of running events, as well as their scheduling. The GM is responsible for receiving event proposals, reviewing them with other GMs and relevant members of Oversight to ensure they cause no issues with existing lore or code, and approving them - either for singular use, or as a recurring event. The GM is also responsible for scheduling and overseeing events, and for granting permissions to Operators to participate in the event process.

GMs may allow Operators to independently run a minor event without directly being present to oversee them, however the Operator assumes some of the GM's responsibilities in doing so.

==== Event Operator ====
Event Operators are members of staff who are capable with the various buttons, panels and features of the Server, supporting the GM in running an event by actually enacting the various steps of the event.

=== Special Staff ===

==== Host ====
Not an official role, but nevertheless the foundation of the server, from which all roles are delegated. Has final authority over the server, but reserves such power only for emergencies and for the highest levels of bureaucracy.

==== Liaison ====
A player dedicated not to the server itself, but to the playerbase. Represents the playerbase within higher channels than regular staff, including a direct line of communication to the headmins and staff heads.

==== Regular Staff ====
A normal player elevated to the rank of staff, who participates in staff discussions, including those involving development staff, providing a layperson's perspective on changes and staff activities.

=== Oversight ===
While not a formal branch of the staff, Oversight consists of Head Administrators, Staff Heads and Game Masters. These roles receive roughly equal permissions, and a separate set of channels to coordinate among each other.

== Player Guidelines ==
This section details how players should interact with the administration in certain situations.

=== Appeals ===
Both moderator and administrator rulings may be appealed. Once the appeal is submitted, a Head Administrator will appoint an Administrator to review the case, or in some circumstances, decide to review the case personally. The appointed administrator may not be the administrator who ruled, and should avoid being the administrator who applied a moderator's ruling.

=== Feature Issues, Development Complaints & Bug Reports ===
* Complaints should only be directed at Head Administrators.
* Issues with features that are neither complaints nor bugs should be posted on the issue tracker, though the appropriate Staff Head is also a valid recipient.
* Finally, bug reports may be discussed directly with the developer of a feature if they are particularly pressing or part of a testmerged PR.

The definitions of the three are left intentionally vague, but bad faith reports will be dealt with.

== Administration Policies ==

=== Admin Exclusion Policy ===

The roles in Oversight, and Game Administrator, cannot be held by anyone holding a position roughly at or above Administrator on any other server.

=== Development and Staff Head Policies ===

==== Staff Head Overruling ====
Staff Heads have mostly unilateral powers when their task. However, tasks overlap, and the whole server is, in the end, a collective development effort. As such there are a handful of ways for them to overrule each other.

* If both forepersons and the Rules staff head agree, a decision can be overruled immediately.
* If there is a foreperson, they can start a motion to overrule a decision made by one of the heads in their group. This vote must be unanimous, with the exception of the head that made the decision. In the case of a foreperson's overruling, a headmin can instead start that vote.
* With the approval of a headmin, all staff heads may undertake a standard vote (with abstention permitted). Headmins may vote in this as well.
* Finally, a 66% supermajority of headmins may make a final decision on a matter.

=== On-Server Powers ===

==== Sounds ====
* Sounds should not be used gratuitously. Save admin sounds for events and other worthwhile situations.

Event Checklist

2025-04-04T01:18:57Z

K5:

{{SidebarStaff}}

= Overview =
For an event to be properly created and run, without risk of the event being declared noncanon, a handful of steps need to be taken. These steps range from simply verifying the lore basis of a minor event's premise, all the way to fully validating all the possible outcomes, sanctions and other long-term consequences of an event.

= Procedure =
While only the final event needs to actually be approved before it's run, there are a few stages in the process of putting the event together which will greatly benefit from input from appropriate staff while it happens.

== Preplanning ==
Before any details are hammered down, the basics of the event need to be established. Who are the main actors? What are their goals? What lore will be leveraged during the event? Which [[Event Archetypes|archetype]] will the event fall under, if any?

Consulting with development staff on these details is recommended here, as a bad outline can lead to the event being completely trashed simply due to it failing to fit the setting and server.

== Event Writing ==
With the outline complete, it's time to nail down the plot and playout. If the event is meant to have RP, then the various information that should be exposed, the goals that arise and how they're completed, and how NPCs will interact with the colony should all be nailed down. For more mechanical events, the rewards and challenges enroute are more important, as well as any possibility that the event might enter an RP phase, or what happens when it goes wrong. In both cases, details on how the difficulty should be adapted to more or fewer players should be considered.

== Consequences ==
Review the consequences of the event. Will it just be another day, to be whisked away into the past as soon as the round ends, or will things change within colony bounds as a result? No need to go overboard at this phase, but getting a general sense of how things will lead to various outcomes - or no permanent changes whatsoever, in some cases - is important for any events with consequences.

== Resources ==
While creating new icons and other objects is possible, for use during the event, the main element that is created - where needed - is the event's map.

* Don't leave too much empty space. Unless it serves some purpose, areas in the map should all be dedicated to whatever story the event is to tell.
* Establish portals in believable places. If an area is meant to be 'far' from the colony, set up its entrances to be further away - leveraging the shuttles to close the distance through the jungle instead of walking.
* Event maps should be connected to relevant areas, and might even feature a direct shuttle waypoint - especially if the map is being reused multiple times.
* Make multiple paths to the goal for larger events. Preferably from different locations and directions. The best maps will have high-difficulty routes through areas of highest challenge, but still allow accessing and completing objectives from different entrances without entering those tougher regions.
* If using the colony itself as a map, don't alter too many critical things, simply due to the difficulty of fixing some things, and the impossibility of fixing others without admin intervention.

== Approval ==
This phase of event handling is the responsibility of Game Masters to oversee, as they are responsible for verifying the event's prerequisites. Once the GM has approved the event, it is up to their discretion when the event will be run. Some events will be also be added to the [[Preapproved Events|list of preapproved events]] and can be run as needed in the future.

=== Lore Review ===
All lore-related details of the event must be validated with the lore team. As many possible outcomes as reasonable should be workshopped and regarded, especially if they lead to long-term consequences for the server outside the event. Finally, characters should be reviewed both in motivation, background, and accuracy - though events involving combat can be a bit more lax here.

Keep in mind that while using lore only needs a staff writer's approval, changes to lore that may occur require a lore staff head's approval.

=== Code Validation ===
As a general rule, any code that has been fully merged is assumed to be ready for use in an event. Test-merged code should receive approval and guidance from a coder. Custom maps should be reviewed by a coder - preferably with a writer and a member of the administration in the room, making sure that nothing out of the ordinary is included - such as unique items. Note that being merged does not necessarily mean being available for use: some entities may be merged but incomplete, or reserved for future use.

The GM has particularly strong discretion here: common features and entities can skip this check entirely. Keep in mind that while using code only needs staff coder approval, changes to code that may occur, like event rewards, require a code staff head's approval.

Additionally, keep in mind that the code is not always self-evident. Certain objects will behave in ways that may lead to problems once the event begins. Consult with coders in advance to ensure that anything whose function you're unsure of will work the way you need it to once the event comes around.

=== Rules Check ===
An event is a special circumstance, but that also means that it may be encouraged for players to break certain rules without the expectation of administrative consequence that you'd have on a normal round.

Unless declared uncanon, Sojourn's rounds have persistence: an event that causes a department war, for example if both the Church and Soteria lay claim upon a crash-landed artifact, will likely be followed up with days or weeks of animosity between players, regardless of whether it has any lasting lore consequence.

Unlike the other steps, these adjustments may be minor enough to need a sign-off from a single moderator, or major enough to need the entire administration to consider it. The GM will determine how much 'weight' of approval is needed before the event will be safe to run.

== Volunteers ==
Events should have as many roles as feasible filled by player volunteers. As a general rule, event staff should reserve only important roles or more difficult (read: needs server buttons often) characters for their own number. If possible, draft a few standby volunteers in case someone is unable to show up once the event arrives.

Volunteers should be designated prior to the event, and coached in advance on their characters and roles within the event. When selecting volunteers, pay attention to which players are more robust, versus which players are better at roleplay, so that they best fit their positions. Remember to establish limitations and rules for them in advance, so the event doesn't devolve into a gunfight or hour long boring meeting.

==== Round Authorization ====
Sojourn is, in principle, an HRP server. This means player-driven interaction takes the front stage. Before scheduling an event, the GM will contact the administration, who may determine that the current round has interactions that would be disrupted by the event, or that the event requires some amount of announcement (or secrecy).

As a general rule, contact the most aware member of the administration first. In this scenario, a moderator actively observing the round outranks an admin who's not even logged into the game. GMs have a unique power to bypass this step under certain conditions.

== Running the Event ==
If the event is set up in advance, select a date and inform the playerbase that an event will be occurring. The more advance warning, the better, but too much and it'll lose hype. Try and choose a time where many players will be participating for the most important events.

=== Final Preparations ===
Ensure that all the volunteers are ready for the event before or as the round begins, so that the event doesn't fall apart right as it's about to begin. Keep one or two standby volunteers in the loop, just in case someone leaves midway.

Unlike regular OOC, AOOC is immune to regular ick/ock rules so long as the event team is moderating it and the event through it. Use this to your advantage for keeping the event running smoothly. Similarly, a private voice chat (or two) can be used to coordinate volunteers and staff live, should the event demand that precision in control, or just for the convenience of participants.

=== Event ===
When setting up the event, use assistance from as many willing staff as needed to speed up the setup. The timing of an event within a single round can heavily impact its difficulty - especially with Research players present - so adapt for that as the event comes close to hitting.

And once you're ready, run the event!

=== Postmortem ===
With an event complete, there's paperwork to do to make sure that it's properly kept in the server's persistency.

* Record and log any relevant details that the event generated or interacted with, lore- or narrative-wise.
* Publish detailed news entries to ensure that any players who were not involved can be caught up to speed - especially for Arc events where players who didn't play a previous event might need to know what's going on for the next.
* Ensure that as many lore points as possible are logged for further use, lest they end up becoming dark lore that only some people are aware of.

Game Master

2025-03-03T07:46:25Z

K5: /* Event Oversight */

{{SidebarStaff}}

Game Masters are responsible for the validation and subsequent approval of events. They work closely in the event creation process to ensure that the event follows the [[Event Checklist]]. An event requires approval from a Game Master to proceed.

== Mandates ==
Game Masters have a range of powers depending on how capable they are. In general, they fall into one of a few categories.

; Broad : These GMs can support and approve the whole gamut of events from the simplest to the most intricate of arcs and their constituent events.
; Arc : These GMs are specifically dedicated to reviewing and overseeing Arcs and its events. They don't concern themselves with smaller or single shot events.
; Persistent : These GMs focus on the more complicated single-shot events that need more specific approvals without the benefit of an overarching Arc approval.
; Mini : These GMs focus on approving small events with few lore or code consequences that can be used to spice up a round on short notice.

== Event Validation ==
Game Masters are responsible for ensuring an event will neither breach lore, have code mishaps, nor cause administrative troubles. See [[Event Checklist]] for details. The GM may seek to approve an event for a single run, multiple, or to have it permanently added to the [[List of Approved Events]] for frequent use as a midround event.

While full approvals are generally required to run an event, GMs have some discretionary power to bypass approvals.
* Most commonly, fully merged code features that the GM or an involved Operator are familiar with need no approval from Code.
* Less frequently, if an event draws on well-known lore and will make no changes to it, such as a known colony enemy launching an attack on an already established site with no chance of any change in relations, Lore need not be involved.
* In extraordinary cases, events that need temporary rule amendments may skip getting approval from the administration. The premise of the event isn't enough to justify this exception: the amendment should either be strongly unforeseen or have such a small risk as to justify surprise when it happens.

Once an event is approved, it is available to use as soon as round interference approval is granted.

== Round Interference ==
Before running an event, the GM is expected to contact the administration to ensure the round is available for interference. If a significant player-driven event is occurring, or other circumstances (such as midround events) are taking too much of the playerbase's attention, the administration may refuse to open the round to the event.

Administrators may add the following conditions before the event may take place:
* The event must be postponed until later, or to the next round, due to current events.
** This may not be done two rounds in a row for the same event, or if the event has already been announced, voted on or telegraphed after all other set conditions are met.
* The event must be announced in advance by some amount of time, up to 7 days.
* The event must pass a vote of some threshold, no greater than 75%.
* The event must be telegraphed in some way before it begins.
* The event must be openly announced at the beginning of the round in which it will be run.
* The event must be openly announced when it begins.
* The event must be kept secret from the playerbase before it is launched.
If conditions conflict with each other, the GM has the authority to determine which conditions to ignore, to remove conflict.

In the event of radio silence from the administration, or in the face of unreasonable demands, a GM is authorized to bypass the round interference portion of approval, so long as an announcement of the event is made no less than 48 hours (2 days) in advance of the event. This power does not excuse the GM from attempting to contact the administration about possible rule implications, but may be used in response to radio silence on that matter as well.

== Event Oversight ==
Game Masters take custody of an event once the event begins. Unlike [[Event Operator|Event Operators]], they do not directly run the event through the game's tools. Instead, it is their responsibility to ensure that the players have a fun time experiencing the event, coordinating with the creator of the event to keep it on track while directing Operators to make changes as they see fit.

GMs are expected to oversee the event from start to finish, but have the discretion to allow an Operator to handle an event in their place if it's minor enough to not need oversight. Simply trusting the operator, however, does not suffice to justify this exception for a larger event.

While the GM should not directly be running most events, if an event is sufficiently simple and there are no Operators available, or if an extra pair of hands are needed beyond the staff already involved, the GM may also run the event.

A single Game Master should suffice for most events, but if additional oversight is needed, another Master can ease some of the burden. The event remains the responsibility of the GM who approved it. If none are available, an Administrator can also help.

== Deputizing ==
Event Operators should be used and prioritized when help is needed for the event. However, if more hands are needed than are available, the Game Master can deputize certain willing staff, in this order of priority:

# Other Game Masters
# Administrators
# Moderators
# Code Staff
# General Staff

Game Master

2025-03-03T07:40:51Z

K5: /* Event Validation */

{{SidebarStaff}}

Game Masters are responsible for the validation and subsequent approval of events. They work closely in the event creation process to ensure that the event follows the [[Event Checklist]]. An event requires approval from a Game Master to proceed.

== Mandates ==
Game Masters have a range of powers depending on how capable they are. In general, they fall into one of a few categories.

; Broad : These GMs can support and approve the whole gamut of events from the simplest to the most intricate of arcs and their constituent events.
; Arc : These GMs are specifically dedicated to reviewing and overseeing Arcs and its events. They don't concern themselves with smaller or single shot events.
; Persistent : These GMs focus on the more complicated single-shot events that need more specific approvals without the benefit of an overarching Arc approval.
; Mini : These GMs focus on approving small events with few lore or code consequences that can be used to spice up a round on short notice.

== Event Validation ==
Game Masters are responsible for ensuring an event will neither breach lore, have code mishaps, nor cause administrative troubles. See [[Event Checklist]] for details. The GM may seek to approve an event for a single run, multiple, or to have it permanently added to the [[List of Approved Events]] for frequent use as a midround event.

While full approvals are generally required to run an event, GMs have some discretionary power to bypass approvals.
* Most commonly, fully merged code features that the GM or an involved Operator are familiar with need no approval from Code.
* Less frequently, if an event draws on well-known lore and will make no changes to it, such as a known colony enemy launching an attack on an already established site with no chance of any change in relations, Lore need not be involved.
* In extraordinary cases, events that need temporary rule amendments may skip getting approval from the administration. The premise of the event isn't enough to justify this exception: the amendment should either be strongly unforeseen or have such a small risk as to justify surprise when it happens.

Once an event is approved, it is available to use as soon as round interference approval is granted.

== Round Interference ==
Before running an event, the GM is expected to contact the administration to ensure the round is available for interference. If a significant player-driven event is occurring, or other circumstances (such as midround events) are taking too much of the playerbase's attention, the administration may refuse to open the round to the event.

Administrators may add the following conditions before the event may take place:
* The event must be postponed until later, or to the next round, due to current events.
** This may not be done two rounds in a row for the same event, or if the event has already been announced, voted on or telegraphed after all other set conditions are met.
* The event must be announced in advance by some amount of time, up to 7 days.
* The event must pass a vote of some threshold, no greater than 75%.
* The event must be telegraphed in some way before it begins.
* The event must be openly announced at the beginning of the round in which it will be run.
* The event must be openly announced when it begins.
* The event must be kept secret from the playerbase before it is launched.
If conditions conflict with each other, the GM has the authority to determine which conditions to ignore, to remove conflict.

In the event of radio silence from the administration, or in the face of unreasonable demands, a GM is authorized to bypass the round interference portion of approval, so long as an announcement of the event is made no less than 48 hours (2 days) in advance of the event. This power does not excuse the GM from attempting to contact the administration about possible rule implications, but may be used in response to radio silence on that matter as well.

== Event Oversight ==
Game Masters take custody of an event once the event begins. Unlike [[Event Operator|Event Operators]], they do not directly run the event through the game's tools. Instead, it is their responsibility to ensure that the playerbase has a fun time experiencing the event, coordinating with the creator of the event to keep it on track while directing Operators to make changes as they see fit.

GMs are expected to oversee the event from start to finish, but have the discretion to allow an Operator to handle an event in their place if it's minor enough to not need oversight. Simply trusting the operator, however, does not suffice to justify this exception for a larger event.

A single Game Master should suffice for most events, but if additional oversight is needed, another Master can ease some of the burden. The event remains the responsibility of the GM who approved it. If none are available, an Administrator can also help.

== Deputizing ==
Event Operators should be used and prioritized when help is needed for the event. However, if more hands are needed than are available, the Game Master can deputize certain willing staff, in this order of priority:

# Other Game Masters
# Administrators
# Moderators
# Code Staff
# General Staff

Template:SidebarStaff

2025-03-03T06:35:55Z

K5:

{{Sidebar
| name=SidebarStaff

| title=Administration
| above=[[Server Policy]]

| heading1=Staff Ranks
| content1={{Sidebar | child=yes
| contentclass=hlist

| heading1=[[Server Oversight|Oversight]]
| content1=
* [[Head Administrator]]
* [[Staff Head]]
* [[Game Master]]
* [[Liaison]]

| heading2=Administration
| content2=
* [[Head Administrator]]
* [[Administrator]]
* [[Moderator]]
| heading3=Showrunning
| content3=
* [[Game Master]]
* [[Event Operator]]

| heading4=Staff
| content4=
* [[Staff Head]]
* [[Code Staff]]
* [[Lore Staff]]
* [[Staff Member|Staff (General)]]

}}

| heading2=Policies
| content2={{Sidebar | child=yes
| contentclass=hlist

| heading1=Oversight Policy
| content1=
* [[Headmin Domain]]
* [[Staff Head Purview]]
| heading2=Administrative Policy
| content2=
* [[Tickets]]
* [[Banning]]
* [[Appeals]]
* [[Rules]]
| heading3=Showrunning Policy
| content3=
* [[Event Checklist]]
* [[Event Archetypes|Archetypes]]
* [[Preapproved Events]]
| heading4=Development Policy
| content4=
* [[Contributor Guide]]
* [[Coding Standards]] [[Features|(Features)]]
* [[Lore Writing]]
| heading5=Staff Policy
| content5=
* [[Code of Conduct]]
* [[Disclosure]]
| heading6=Player Policy
| content6=
* [[Persistency]]
* [[Roleplay]]

}}
}}<includeonly>[[Category:Staff]]</includeonly>

Template:SidebarStaff

2025-03-03T06:30:48Z

K5:

{{Sidebar
| name=SidebarStaff

| title=Administration
| above=[[Server Policy]]

| heading1=Staff Ranks
| content1={{Sidebar | child=yes
| contentclass=hlist

| heading1=[[Server Oversight|Oversight]]
| content1=
* [[Head Administrator]]
* [[Staff Head]]
* [[Game Master]]
* [[Liaison]]

| heading2=Administration
| content2=
* [[Head Administrator]]
* [[Administrator]]
* [[Moderator]]
| heading3=Showrunning
| content3=
* [[Game Master]]
* [[Event Operator]]

| heading4=Staff
| content4=
* [[Staff Head]]
* [[Code Staff]]
* [[Lore Staff]]
* [[Staff Member|Staff (General)]]

}}

| heading2=Policies
| content2={{Sidebar | child=yes
| contentclass=hlist

| heading1=Oversight Policy
| content1=
* [[Headmin Domain]]
* [[Staff Head Purview]]
| heading2=Administrative Policy
| content2=
* [[Tickets]]
* [[Banning]]
* [[Appeals]]
* [[Rules]]
| heading3=Showrunning Policy
| content3=
* [[Event Checklist]]
* [[Event Archetypes|Archetypes]]
* [[Preapproved Events|List of Preapproved Events]]
| heading4=Development Policy
| content4=
* [[Contributor Guide]]
* [[Coding Standards]] [[Features|(Features)]]
* [[Lore Writing]]
| heading5=Staff Policy
| content5=
* [[Code of Conduct]]
* [[Disclosure]]
| heading6=Player Policy
| content6=
* [[Persistency]]
* [[Roleplay]]

}}
}}<includeonly>[[Category:Staff]]</includeonly>

Server Policy

2025-02-28T03:19:52Z

K5: /* Staff Roles */

{{Stub}}
This page's contents are being migrated to their respective pages. Contents may be outdated.
[[Category:Staff]]

{{SidebarStaff}}

== Staff Roles ==
''This section is out of date. Review the specific page for the role.''

=== Administrative Staff ===
Administrative staff handle all things to do with player activities on server. It is the role of the administration to determine where player actions contravene the server and to act to correct such instances.

==== Head Administrator ====
Head Administrators oversee the server as a whole, and act to maintain the administration rather than directly administering. Individually, they can override rulings made by administrators and moderators. Together, they can override decisions on server direction as made by the staff heads, as well as rulings made by individual headmins.

In the event that an administrator is unavailable, a head administrator may step in to act. However, this is discouraged, as receiving a ruling directly from a head administrator may leave a player feeling unable to seek appeal or recourse at a higher level.

==== Administrator ====
Administrators rule on player situations that need more complicated solutions than fall within a moderator's prerogative. Excessive rule-skirting, undesired behaviour and other complex issues fall under the Administrators' purview. Administrators also act as agents in enforcing IC rulings where the High Council is involved, and respond to faxes with the full authority of the council.

==== Moderator ====
Moderators act on straightforward issues involving player actions. Generally, this simply means enforcing rules as written in a cut and dry fashion, and helping collect information on situations that an Administrator would otherwise rule on. Moderators are the first line in ensuring that the server stays on track and appropriately in tone.

Moderators do not act on behalf of the High Council when exercising their moderation powers, but may make informational responses to faxes as supporting staff to a specific councillor.

As moderators do not have some server permissions granted directly to them, many of their rulings may need to have an administrator rubber stamp them and apply them.

=== Supporting Staff ===
Supporting staff handle all things to do with the server's state and development.

==== Staff Head ====
Staff Heads oversee the development of the server. Each one is given a specific family of tasks to oversee or maintain. Each staff head is either particular to Lore or Code tasks, and when there are four staff heads within either group, one of that group is granted the additional task of foreperson.

An additional, unique Staff Head role exists for maintaining the Rules. This role is also granted the powers and authority of an administrator, but is generally expected to focus on finding flaws in the rules and easing them out, over enforcing them, and to handle rule changes as dictated by headmins.

Staff Heads may respond to faxes regarding clear cut IC issues, in the same fashion as a moderator.

==== Game Master ====
A Game Master creates and runs larger events that may affect the lore or have permanent effects. They may also run normal events at will and create their own stories. Game Masters may also approve events by event operators.

Within the context of an event they are operating, Game Masters also receive authority just above that of a moderator.

==== Event Operator ====
Event Operators run normal events with the approval of a Game Master or Administrator. They also assist in events being run by Game Masters.

==== Developer ====
A member of development staff empowered to inspect and debug the server live, as well as provide technical support on the server where pertinent.

==== Development Staff ====
A contributor elevated to the rank of staff. Has a louder voice when making proposals to how the server should be improved. Is expected to be accurately authoritative when it comes to statements about the server. Works with the staff heads to make sure features are consistent with the playerbase's expectations.

=== Special Staff ===

==== Host ====
The font of all power, from which it is all delegated. Has final, unshakable authority over the server, when used.

==== Liaison ====
A player dedicated not to the server itself, but to the playerbase. Represents the playerbase within higher channels than regular staff, including a direct line of communication to the headmins and staff heads.

==== Regular Staff ====
A normal player elevated to the rank of staff, who participates in staff discussions, including those involving development staff, providing a layperson's perspective on changes and staff activities.

== Player Guidelines ==
This section details how players should interact with the administration in certain situations.

=== Appeals ===
Both moderator and administrator rulings may be appealed. Once the appeal is submitted, a Head Administrator will appoint an Administrator to review the case, or in some circumstances, decide to review the case personally. The appointed administrator may not be the administrator who ruled, and should avoid being the administrator who applied a moderator's ruling.

=== Feature Issues, Development Complaints & Bug Reports ===
* Complaints should only be directed at Head Administrators.
* Issues with features that are neither complaints nor bugs should be posted on the issue tracker, though the appropriate Staff Head is also a valid recipient.
* Finally, bug reports may be discussed directly with the developer of a feature if they are particularly pressing or part of a testmerged PR.

The definitions of the three are left intentionally vague, but bad faith reports will be dealt with.

== Administration Policies ==

=== Admin Exclusion Policy ===

The roles in Oversight, and Game Administrator, cannot be held by anyone holding a position roughly at or above Administrator on any other server.

=== Development and Staff Head Policies ===

==== Staff Head Overruling ====
Staff Heads have mostly unilateral powers when their task. However, tasks overlap, and the whole server is, in the end, a collective development effort. As such there are a handful of ways for them to overrule each other.

* If both forepersons and the Rules staff head agree, a decision can be overruled immediately.
* If there is a foreperson, they can start a motion to overrule a decision made by one of the heads in their group. This vote must be unanimous, with the exception of the head that made the decision. In the case of a foreperson's overruling, a headmin can instead start that vote.
* With the approval of a headmin, all staff heads may undertake a standard vote (with abstention permitted). Headmins may vote in this as well.
* Finally, a 66% supermajority of headmins may make a final decision on a matter.

=== On-Server Powers ===

==== Sounds ====
* Sounds should not be used gratuitously. Save admin sounds for events and other worthwhile situations.

Appeals

2025-02-27T12:59:43Z

K5: Created page with "This page is under construction. Have a sample appeal in the meantime. <blockquote> Facts: Time of Ban: January 1st, 2022 Banning Admin: k5 Ban Reason: Overescalation bordering on RDM Ban Expiry: Indefinite Appeal Window: January 1st, 2023 Cause: I was playing Joe Jimbo in the bar, and he was getting drunk. When Kimberly made a passing insult at him, Joe got mad and shot Kimberly in the face. Postmortem: I believe I was banned because I didn't..."

This page is under construction. Have a sample appeal in the meantime.

<blockquote>
Facts: 
Time of Ban: January 1st, 2022 
Banning Admin: k5 
Ban Reason: Overescalation bordering on RDM 
Ban Expiry: Indefinite 
Appeal Window: January 1st, 2023 

Cause: I was playing Joe Jimbo in the bar, and he was getting
drunk. When Kimberly made a passing insult at him, Joe got mad
and shot Kimberly in the face.

Postmortem: I believe I was banned because I didn't properly
escalate before pulling out the gun. The insults wouldn't have
aggravated any other characters, drunk or not, into doing what
mine did, and it was excessive escalation.

Pleading: I won't play my characters in a way that they snap from
drunken banter to point blank murder in the future.
</blockquote>

Server Policy

2025-02-26T01:42:58Z

K5:

{{Stub}}
This page's contents are being migrated to their respective pages. Contents may be outdated.
[[Category:Staff]]

{{SidebarStaff}}

== Staff Roles ==
''This section is incomplete but accurate.''

=== Administrative Staff ===
Administrative staff handle all things to do with player activities on server. It is the role of the administration to determine where player actions contravene the server and to act to correct such instances.

==== Head Administrator ====
Head Administrators oversee the server as a whole, and act to maintain the administration rather than directly administering. Individually, they can override rulings made by administrators and moderators. Together, they can override decisions on server direction as made by the staff heads, as well as rulings made by individual headmins.

In the event that an administrator is unavailable, a head administrator may step in to act. However, this is discouraged, as receiving a ruling directly from a head administrator may leave a player feeling unable to seek appeal or recourse at a higher level.

==== Administrator ====
Administrators rule on player situations that need more complicated solutions than fall within a moderator's prerogative. Excessive rule-skirting, undesired behaviour and other complex issues fall under the Administrators' purview. Administrators also act as agents in enforcing IC rulings where the High Council is involved, and respond to faxes with the full authority of the council.

==== Moderator ====
Moderators act on straightforward issues involving player actions. Generally, this simply means enforcing rules as written in a cut and dry fashion, and helping collect information on situations that an Administrator would otherwise rule on. Moderators are the first line in ensuring that the server stays on track and appropriately in tone.

Moderators do not act on behalf of the High Council when exercising their moderation powers, but may make informational responses to faxes as supporting staff to a specific councillor.

As moderators do not have some server permissions granted directly to them, many of their rulings may need to have an administrator rubber stamp them and apply them.

=== Supporting Staff ===
Supporting staff handle all things to do with the server's state and development.

==== Staff Head ====
Staff Heads oversee the development of the server. Each one is given a specific family of tasks to oversee or maintain. Each staff head is either particular to Lore or Code tasks, and when there are four staff heads within either group, one of that group is granted the additional task of foreperson.

An additional, unique Staff Head role exists for maintaining the Rules. This role is also granted the powers and authority of an administrator, but is generally expected to focus on finding flaws in the rules and easing them out, over enforcing them, and to handle rule changes as dictated by headmins.

Staff Heads may respond to faxes regarding clear cut IC issues, in the same fashion as a moderator.

==== Game Master ====
A Game Master creates and runs larger events that may affect the lore or have permanent effects. They may also run normal events at will and create their own stories. Game Masters may also approve events by event operators.

Within the context of an event they are operating, Game Masters also receive authority just above that of a moderator.

==== Event Operator ====
Event Operators run normal events with the approval of a Game Master or Administrator. They also assist in events being run by Game Masters.

==== Developer ====
A member of development staff empowered to inspect and debug the server live, as well as provide technical support on the server where pertinent.

==== Development Staff ====
A contributor elevated to the rank of staff. Has a louder voice when making proposals to how the server should be improved. Is expected to be accurately authoritative when it comes to statements about the server. Works with the staff heads to make sure features are consistent with the playerbase's expectations.

=== Special Staff ===

==== Host ====
The font of all power, from which it is all delegated. Has final, unshakable authority over the server, when used.

==== Liaison ====
A player dedicated not to the server itself, but to the playerbase. Represents the playerbase within higher channels than regular staff, including a direct line of communication to the headmins and staff heads.

==== Regular Staff ====
A normal player elevated to the rank of staff, who participates in staff discussions, including those involving development staff, providing a layperson's perspective on changes and staff activities.

== Player Guidelines ==
This section details how players should interact with the administration in certain situations.

=== Appeals ===
Both moderator and administrator rulings may be appealed. Once the appeal is submitted, a Head Administrator will appoint an Administrator to review the case, or in some circumstances, decide to review the case personally. The appointed administrator may not be the administrator who ruled, and should avoid being the administrator who applied a moderator's ruling.

=== Feature Issues, Development Complaints & Bug Reports ===
* Complaints should only be directed at Head Administrators.
* Issues with features that are neither complaints nor bugs should be posted on the issue tracker, though the appropriate Staff Head is also a valid recipient.
* Finally, bug reports may be discussed directly with the developer of a feature if they are particularly pressing or part of a testmerged PR.

The definitions of the three are left intentionally vague, but bad faith reports will be dealt with.

== Administration Policies ==

=== Admin Exclusion Policy ===

The roles in Oversight, and Game Administrator, cannot be held by anyone holding a position roughly at or above Administrator on any other server.

=== Development and Staff Head Policies ===

==== Staff Head Overruling ====
Staff Heads have mostly unilateral powers when their task. However, tasks overlap, and the whole server is, in the end, a collective development effort. As such there are a handful of ways for them to overrule each other.

* If both forepersons and the Rules staff head agree, a decision can be overruled immediately.
* If there is a foreperson, they can start a motion to overrule a decision made by one of the heads in their group. This vote must be unanimous, with the exception of the head that made the decision. In the case of a foreperson's overruling, a headmin can instead start that vote.
* With the approval of a headmin, all staff heads may undertake a standard vote (with abstention permitted). Headmins may vote in this as well.
* Finally, a 66% supermajority of headmins may make a final decision on a matter.

=== On-Server Powers ===

==== Sounds ====
* Sounds should not be used gratuitously. Save admin sounds for events and other worthwhile situations.

Game Master

2025-02-18T07:38:33Z

K5: /* Event Validation */

Game Master

2025-02-18T07:38:14Z

K5: /* Event Validation */ The GM's discretion has been codified.

Game Master

2025-02-18T07:02:21Z

K5:

Event Operator

2024-12-19T07:11:31Z

K5: /* Event Composition */

{{SidebarStaff}}

Event Operators are staff trained to handle the game's tools. They're capable of running approved events single-handedly, as well as helping other event operators with their events when more than one pair of hands is needed. Event Operators answer to [[Game Master|Game Masters]] and receive in-game permissions from them alongside event approval.

== Event Running ==
Formally, events are run by the Game Master that approves the event, with the assistance of the creator of the event. This leaves the role of the Operator primarily in the mechanical running of the event as described in the event plan, and following any other instructions.

In practice, the event team communicates to run the event smoothly and make any necessary adjustments as needed. More often than not, an event will be run by the Operator who created it, and will have extra flexibility in adjusting the event to suit their intentions.

== Event Composition ==
Beyond simply running an event, Operators also are the primary contact point of any denizens who want to create an event. They're responsible for guiding the denizen through the [[Event Checklist]] and making sure all the steps are followed to produce a great event. Once the event is ready, the Operator is also responsible for submitting it for review, along with an assurance that the denizen's event was built correctly.

Given their intimate relationship with the event process, Operators themselves receive extra privileges:

* They are not restricted to following the [[Event Checklist]] step by step, and may submit an event plan for approval without any prior communication.
* They may fast-track their event's approval process by having relevant development staff pre-approve lore and code elements or changes, allowing the Game Master to simply verify the approval once submitted.
* For their own events, they both advise the active GM and can also directly operate the event as it happens. This provides no benefit beyond fitting a single person to two roles during the event.

Staff head

2024-12-19T04:10:14Z

K5: Redirected page to Staff Head

#REDIRECT [[Staff Head]]

Administrator

2024-12-15T18:28:25Z

K5:

{{SidebarStaff}}
Administrators have the broad power of sustaining the administration on the server. They wield the ban hammer, have executive authority to issue orders to denizens, and some are tasked with the Staff Head-like role of writing and maintaining the rules. They are directly beholden to headmins, who may intervene if they believe an admin is acting beyond or in contravention to the server's direction.

== Spirit of the Law ==
Administrators are granted the power to interpret the rules in more broad and creative ways than moderators. In circumstances where a denizen frequently comes close to breaking a rule without actually breaking it, it is the administrator who determines how much, or how close, is too close. For situations where the punishment would normally be minor, it is the administrator who may find an instance to be particularly egregious and escalate the punishment to match.

== Approvals ==
While the old adage "it's better to ask for forgiveness than permission" may spare a player from punishment, whether it be a breach of the rules, a disregard for lore, or misuse of a bug, it's expected to stop - preferably before administration needs to get involved.

It is the administrator's prerogative to judge when an exception to the rules will contribute more to the server than their enforcement. Unlike moderators, their approval may span over multiple rounds, and ignore lore or bugs. These approvals should be issued conditionally and temporarily, to ensure that they're not taken too far.

== Banning ==
Administrators are empowered to enforce all sanctions that are necessary in a situation. Whether this be as simple as banning an unrepentant troublemaker, or as complex as issuing individualized bans, mutes, job-bans and de-whitelistings to a group that's causing issues, the administrators are involved in the process.

== Appeals ==
The administrator that takes custody of an issue is responsible for it even after the situation has been resolved. In the event of an extended ban, it's that same administrator's role to handle the appeal. In the event that a head administrator has assigned another admin to the case, the administrator with custody is still expected to provide information, evidence or other assistance in the appeal process.

Moderator

2024-12-15T18:20:00Z

K5:

{{SidebarStaff}}

Moderators are the lower rank of the administrative branch. Their responsibilities lie in the straight-forward elements of server administration, and their role is primarily to collect information and correct player misbehaviour, rather than explicitly punishing the players.

== Letter of the Law ==
Moderators enforce the rules as written, however they are only empowered to take minor actions against denizens. As such, in the pursuit of enforcement, their role is more informative: they investigate and produce a complete summary of the situation, then present it to Administrators alongside a recommendation of what action should be taken.

== Player Guidance ==
When players aren't acting with impunity, the moderator is also responsible for guiding and correcting their mistakes. In the simplest situations, that means messaging them to inform them of the error. Usually, however, the moderator should undertake questioning before attempting to judge whether an activity is against the rules. Patience is a virtue here: unless the situation is truly urgent, moderators should allow the player to play through whatever situation they're currently in before initiating the conversation.

== Whitelist Applications ==
It is also the responsibility of the moderator to approve whitelists. The most important element of the whitelist to verify is age: absolutely no players under the age of 18 should be permitted to play on Sojourn. Beyond that, other points to consider are applicants' skill in writing English within a fast-paced roleplay environment, their understanding of what high roleplay means, and their understanding of consequences. While a ban history outside Sojourn is not usually a sufficient reason to deny an application, moderators have discretion in how to interpret such records. For example, someone with a long sequence of recent bans may be on the hunt for another server to misbehave on, whereas someone with many older bans may be given the benefit of the doubt and allowed the opportunity to demonstrate their reform.

== Granting Permission ==
Occasionally, a player will have an idea that, while nominally against the rules, will provide an interesting round or situation. Moderators may, if they trust the player to execute the plan in an engaging and worthwhile manner, permit one-time breaches of the rules. These permissions are expressly singular, and only usable within the round in which said permission was granted. The permission comes with no further benefits: the player must still be able to execute their idea within the other rules, and/or self-antag guidelines.

== Logging ==
While the burden of ensuring all faxes (and any relevant tickets or ahelps) are appropriately logged falls to all staff with access to view them, moderators are explicitly tasked with recording them.

Rules

2024-12-15T18:19:28Z

K5: /* Rules of ‘Self-Antag’ */

{{GetStartedHeader}}
{{SidebarStaff}}

These are the rules for the server and ''are subject to change without notice''. For further clarification, use common sense. If you did get banned, there's probably a good reason for it, but if you disagree, you can always make an appeal on the discord. Although these are rules, but they are not infallible, complete, or concrete, and probably never will be despite our best efforts. If ''ever'' something feels wrong, either don't do it, or admin-help it first. Above all, use your common sense, listen to the game staff, and try to keep the game fun for everyone; not just yourself.

If you disagree with the rules as they currently stand, talk about it on the discord or with admins and maybe we can improve them through some healthy criticism and debate.

'''These rules are designed to be written in such a way that you can ''usually'' understand them just by reading the headers''', because reading ''all of this'' would be insanity for most people. If you cannot understand a rule just by looking at it, or wish to know about possible exceptions or examples, click the rule to learn more.

If you find yourself spending too much time reading this page, or are confused about any rules, please contact an admin on Discord to make suggestions on how these rules could be better worded.

== You must be 18 or older to play on this server ==
'''There are no exceptions.''' If the staff suspects that you are underage for any reason, you will be banned from playing on the server until you are able to prove to the satisfaction of the staff that you are at least 18 years old.

*Use of real world slurs, ‘lolspeak’, and other indications of immaturity may be taken as signs that you are underage.

*Knowing another user is underaged but not reporting it is considered grounds for an immediate, permanent ban.

*The age of consent in your country is irrelevant. Your opinion about this rule is irrelevant.

*You may also not play a character who is under 18 years of age.

== Obey the community's global rules ==
These rules apply ''everywhere'', including Discord, the server, and even private discussions with non-admins. However, not all of the global rules are even possible to break in the server, so this wiki page only covers what's relevant to the game server. The overlap from the global rules are:

* No spam.
* No OOCly illegal discussions or content (such as child porn, drugs, piracy, real world threats, etc).
* Respect other users, don't use real-world slurs, and don't intentionally drag private conflicts or in-game conflicts into public OOC (such as on the Discord server, the in-game global OOC channel, or anywhere else).
* Don't intentionally abuse server functions to upset (grief) people, or derail discussions. You know what this means, don't play stupid.
* No complaining about bans unless done properly via an appeal on our [https://sojourn13.space/forum/viewforum.php?f=13 forums] or in an ahelp or otherwise private means as an inquiry to administration staff.

== Don't be an asshole ==
It's fine to say stuff and whatnot but being a outright dick isn't alright, and there's a fine line with that. Also, spamming racist words is still not okay.

=== Do not inconvenience AFK or disconnected characters ===
Under normal circumstances, do not harm or otherwise inconvenience characters whose player is idle, ghosted, or disconnected entirely. There are some exceptions to this rule, as follows:
*Circumstance that warrant the interactions of AFK/SSD players are few and far between if there is ever a case were you are REQUIRED for to take any ID/Bag/Gear from someone that is SSD, Ahelp before hand and with your reason why. Not ahelping before may result in HARSH OOC punishment if you are found to be manipulating them while away, or causing any sort of general tampering with the player. (IE. Don't be an asshole who steals shit from afk players unless its required)
Note: If your moving someone to cryo after the time, this is ok, as long as you do not remove their items unless it's faction important and you have the means to return them properly
*If they've disconnected/idle for more than 15 minutes, you can put them in cryosleep. If you do that, take away all of their belongings except for their jumpsuit, shoes, ID, and PDA, and return everything else to its rightful department.
*If they've committed a crime, jail them as you normally would and conduct their sentence even if they aren't connected. 20 minutes in the brig is still 20 minutes in the brig.
*Emergencies bypass this rule. If it's an emergency and you need something an idle player has to fix it, you may take it. If a fire starts in a room and the AFK player is the only one who can open the door then it's an emergency. Needing to get a snack from the kitchen and robbing the chef does not count as an emergency.

=== ERP preferences must be respected ===
Players should have their ERP prefs listed in their “OOC Meta info” or “OOC Notes” on their characters. You are required to respect these preferences so long as they pertain to ERP. If you are unsure about the meaning of some of their preferences, then use LOOC to discuss it with them. If you accidentally go against someone’s preferences, or someone else goes against yours, work to correct it as quickly as possible, even if that means just deciding in LOOC amongst yourselves that ‘this didn’t happen’ and going your separate ways.

*If you do not like someone's erp preferences you won't be punished for saying so, but do not harass someone just because they like something you don't. It's far easier to simply avoid someone and causing drama will get you into trouble.

*If you are uncomfortable with an ERP theme that you hadn't thought to add (or didn't know existed) to a list of dislikes in your OOC notes, speak up in LOOC as normal. Conversely, those of you foolish enough to put 'anything goes' into your preferences, or anything else vague like this, do so at your own risk. '''You forfeit your right to complain about preference breaking''' if you do not put ''some'' indication of your dislikes into OOC preferences.

**'''Do not engage in any non-consensual scenes. If you are found to be doing non-consensual scenes even with OOC consent on server you may be banned from the community as a whole. If you have not consented to the scene - A-help IMMEDIATELY'''.
**Do not make false allegations of non-consensual scenes in game. Falsely accusing someone of rape or other non-consensual material will result in an immediate ban. This is incredibly bad faith and petty.
**'''Being found in violation of NON-CON rule(s) will be met with an automatic player kill (PK) and Perma Ban with no appeal given investigation. You've been warned as this is not tolerated here.'''

*Do not attempt to force yourself into ERP scenes where the other party (or parties) involved are not comfortable with it, or not even actually participating. This includes (but is not limited to) repeatedly trying to do ERP that a player has blatantly stated they are uncomfortable with, trying to guilt players into having a pity RP with you, etc. You get the idea. Don't do it.

*AFK/SSD/Disconnected players are not valid targets for any ERP.

=== The private areas are protected ===
The ‘dorms’ area on the map are reserved for ERP and are ‘protected’ from interruption. It is a violation of this rule to break into occupied dorms or harass players in dorms. Dorm areas are any personal apartments generally restricted to a specific person such as a head of staffs private bedroom or a dorm area claimed by a specific person, usually through a labeled door.
*The only exception is for security to arrest those who have committed crimes. Security is not allowed to indiscriminately inspect dorms for crimes, but a known criminal hiding in a dorm is not protected by this rule.
*The existence of dereliction of duty is also to be noted here, if you are working a job expected to perform a role and take time off to go to dorms you can, and likely will be interrupted via a warrant for abandoning your assigned job. For more info see rule 5.6 (You are expected to perform the job you signed up for).
*Conversely, it is not permissible to attempt to use dorms to hide from security, or to make their job of finding you harder. The dorms are for people who want to ERP in privacy. Don’t involve them in your shenanigans.

=== Do not disrupt non-public ERP scenes ===
TL;DR is you should avoid screwing with scenes that are not in public areas. The problem is, not everyone knows what is considered public or private. This is especially important for [[Security]] players to know.
*Dorms are considered private obviously. Don't mess with those under any circumstances unless someone inside actively invites you. (Calling for help is considered an invite.)
*If a person is ERPing in a public location they should be asked to vacate to a private dorm room. If they refuse they may be arrested immediately.

=== Speak English ===
We are an English server. All OOC communications are expected to be done in English. It's alright if your English is rough and imperfect, just as long as we can reasonably understand it.

*This also extends into IC communications, but is more flexible as some characters have heavy accents.
*Having a character sometime speak smatterings of other languages is acceptable, but speaking exclusively in these languages for entire sentences is not.

=== Roleplay as long as it's feasible ===
*This is an HRP (Heavy RolePlay) server. You are expected to roleplay your actions with other players as long as it's feasible. If someone engages you in purely ‘robust’ (aka game-mechanics driven) combat while you were attempting to roleplay with them, with no reasonable provocation, please use the admin-help feature to inform an admin.
**Reasonable provocation would be things that deem you too dangerous to be given even a chance to talk. For example, openly wielding a gun while threatening people, charging someone with a knife, trying to create a hazard, or being the target of a manhunt.

*If a fight does begin, you're not expected to type out every gunshot and dodge and attack. That would be absurd. Generally, you roleplay up until the point that it makes sense to start attacking, and then use game mechanics from there. You are allowed to respond to ‘robust’ violence with your own, if you desire, though you should attempt to return to roleplaying as soon as feasible. The environment is not designed for a focus on action, but rather for character-building and roleplaying. When a fight is over, resume roleplaying.

*Movement is considered a game mechanic for the purpose of this rule. Wordlessly running at a security officer who is attempting to arrest you, or wordlessly fleeing from them, is considered engaging in game-mechanic combat. The security officer has valid cause to stop trying to roleplay and stunlock you into the ground.

*Death may not be uncommon at the frontiers of space but it is still impactful. When a character dies, or your own character dies and is revived, death should be considered an immensely painful and graphic experience. One should stay in character during said experiences, statements of ‘oh well’ or mutilating a corpse for ‘fun’ would not be reasonable responses.

*'''You are to have fleshed out character records.''' These are used not only for roleplay but are to be utilized, if specified by staff, for long-term consequences for actions. Players are supported to use these as roleplay documents and treat others with these seriously. Our expectations for what should be in these can be found on [[https://sojourn13.space/wiki/Example_Paperwork#Character_Records|the Character Records page of our Example Paperwork wiki.]]

=== Do not join with an inappropriate ckey ===
Ckeys, better known as BYOND user names, must be appropriate. If any are deemed inappropriate, the ckey will be banned and you will be unable to play on our server until you make an account with an appropriate name.
*Ckeys that mock certain players or groups are an example of inappropriate.
*Ckeys that violate BYOND's terms of service may also be reported.

=== Do not misuse Global OOC ===
Many servers simply mute global OOC. We do not, because the OOC command is useful to have on in an RP heavy server.

* Global OOC is used, for instance, to contact someone you were typing a reply to had walked out of the room before you were done, and you're trying to ask them to come back. It's also useful if you're a new player, or an old player exploring new mechanics, who asks something like, "How do I make Tricord again?" or something short and similar. Short, sweet, and relevant OOC messages are generally okay. Welcoming old players returning, or new players joining, is also generally okay.

* Global OOC is ''not'' for idle banter, ranting, things pertaining to incidents in the current round (see previous rule), in-depth explanations (an explanation that takes more than a few lines), shitposting memes, or discussing topics not relating directly to the game. If you want to chatter OOCly, go to our Discord channel, which is linked from the home page or use LOOC so as to not disturb the rest of the server.

* Also, if someone does misuse OOC, do not complain in global OOC about their misusing of global OOC. Not only are you just making the problem worse, that is considered being a backseat admin, which is prohibited by other rules.

== Keep IC and OOC separate ==
*Don't complain in OOC or LOOC when your actions IC get you in trouble. If its a rules violation then Ahelp or open a ticket on the discord.
*IC (In-character) and OOC (Out-of-Character) actions and knowledge should be separated as much as possible. Don't use OOC channels to discuss what's going on IC until after the round is finished, don't use OOC knowledge to do things your character wouldn't know, such as operate medical machines when a cargo technician. You are not playing yourself in the game, you are controlling a character with their own wants and knowledge and the IC/OOC boundary is to help reflect that.
**Note that these same rules apply to LOOC as well.
*Disconnecting or using other OOC means to avoid IC consequences is against the rules. If you do urgently need to leave the server even though you're being punished, your options are either to surrender and get it over with, or use admin help to inform the admins, "I know Security is after me, but I have to go because (some emergency)." Failure to take ten seconds to tell an admin before disconnecting may result in harsher punishment.

=== Metacomms, metagaming, multi-keying, (etc) are not allowed ===
*Metacomms: Using third-party programs, such as Discord, IRC, Skype, or even the BYOND pager, to discuss and share information of the ongoing round. This excludes other players, can contribute to toxicity among the playerbase, and is often a tactic used by griefers and thus is a no-go.

*Metagaming: Using information obtained from elsewhere to influence IC decisions and actions. Your opinions or knowledge of other players or characters obtained via OOC methods should not direct your IC actions. If you have an OOC grudge against someone, you may not try to antagonize them IC, for example.
** Metagaming sometimes happens by accident due to game mechanics behaving undesirably due to intentional features or unintentional bugs and oversights. If it happens, ask an admin to help straighten things out if you can't do so among yourselves.

*Multi-keying: Logging in with multiple BYOND accounts on our game server. There is never any legitimate reason for you to do this and thus is not allowed.

= Create and play server-appropriate characters =
Although this is a furry roleplaying server based around 2D spess mans, that doesn't mean anything goes because that is possible. Suspension of disbelief is still important to a good experience, and breaking that suspension of disbelief is bad for roleplaying. Characters who break that suspension of disbelief are not allowed. Saying "it's what my character would do" isn't an automatic protection against this rule if what your character is doing breaks that immersion.

*Play a reasonably sane and mature character, give them a non-immersion breaking first and last name, do not play obvious reference characters, or characters from published works.

*Keep in mind that people do not like pain or dying and usually try to avoid it without good reason. Give your character a reasonable set of strengths, fears, and weaknesses. When writing things for IC, write things out that sound like speech, not emoticons or lolspeak.

*The setting contains no magic. Your character cannot have any superpowers, magical abilities, or anything that does not exist in the setting or cannot be reasonably replicated with game mechanics. If they are not someone who has a good reason to work on the colony, they should not be here.
**The exception to this is purely private roleplay. For example: If your character and another character are in a dorm by themselves, and the other is OOCly fine with it, your character can display potentially supernatural abilities. This is limited to that roleplay, though. You should not discuss anything about that in public. Use magic at your own risk however, because technically the moment your RP is discovered by someone else, it stops being private, putting you in potential violation of this rule.

*Obscenely oversized or undersized characters are forbidden. Minimum height is at least four feet. Maximum height is about eight feet. Anything more or less really pushes the already shaky believably of abhumans and established alien lore.

*If you are playing a lore based species such as sablekyne, mar'qua, opifex, or whatever else we add in the future, you are expected to play the race as they are canonically meant to be played.

*OOC Notes and Flavor Text are '''required'''. Your OOC notes must detail your ERP preferences, and your flavor text should not include non-physical attributes (do not include feelings your character has, or how they act). Character records are something that should be filled out, if you have an issue or don't know how to do it properly, contact a member of staff for help.

*To be a colonist your character '''must''' have at least a ''basic'' understanding of the English language. Outsiders, however, are exempt from this restriction and may be of people from various backgrounds that may not have a grasp of even basic English.

*If your character is suspended, permanently killed off, or otherwise removed from the colony as a consequence for something horrible they did in-character, you are expected to not play that character anymore. If found playing the character again, or a 'clone' to circumvent this result, OOC punishment will be issued.

* '''Do not play vibrantly colored or "sparkle dog" type characters.''' This basically means you should mainly have natural fur coloration and a relatively normal appearance. Yes, our character editor has a ton of color options, including neon colors and many design sprites to do strange things. Creativity is fun, making your appearance incredibly unrealistic or as obnoxious as possible will result in admin intervention. Some leeway is given to races with canonically vibrant colors such as cht'mants and cindarites or custom xenos but try to keep them muted instead of neon. Following the custom species guide does not make you immune from this rule. If an admin asks you to change your color, do so, we have this rule to maintain HRP.

* These following rules are taken directly from the Character Creation page[[https://sojourn13.space/wiki/Character_Creation]].
*Characters who are new to the server should shy away from head position or complicated jobs.
*Characters who have been present on the station for at least a month are safer to join head positions.
*Characters who have been present on the station for a decent period of time can work for up to 2 departments. This may be working Lonestar (Chef-Bartender-Janitor-Gardener-Artist-Cargo Tech-Miner) and Marshal (Supply Specialist-Marshal Officer-Ranger), though try to keep it believable within this sense. This may also include Science (Scientist-Roboticist) and Medical (Medical Doctor-Paramedic-Orderly), or any other variation one may think of. Blackshield counts the same as if you were working Marshals, and the Lodge does not count against your picked departments (but does count as a head role).
*Characters are only allowed to be one head role at any given time. One may not be both Science and Medical, and play both CRO and CBO. One must be chosen over the other.

== Do not kill or attack things (including yourself) for no good reason ==
*This includes yourself. Even in self-defense your goal is to fight off your attacker and survive, killing in a fight should only be done as a last-ditch effort when it's clear it's a you or them situation.

*Suicide or self-mutilation is not allowed without prior allowance by an admin. The reason for this is to maintain an atmosphere of reasonable and, at least mostly, mentally sound workers. The subject can be a poor attention grab, be used for guilt, or remove any immersion or story from someone. If you believe you have a reason, ask an admin.

*Excessive force responses are not allowed by our rules. Excessive force responses would be, for example, crushing someone’s skull for cutting you in line, stabbing someone’s eyes with a screwdriver for boredom, killing someone over a single punch, etc. Use proper reasoning for when you act in such a manner.

*Hiding player corpses as a self-antag / antag is not allowed. Staff may give an exemption in the case of an event but the body should still be possible to be found.
**Similarly, do not destroy bodies purposefully. Accidents happen regarding gibbing of a skull, destruction of someone’s body due to a bomb, etc. But whacking a target that is dead until it starts gibbing its limbs is not.
**Antags have some exemption to this; such as Blitzshells or Carrions. However admins are to specify if an antag may use these abilities or not as they can possibly end up being round-ending for a player.

*Make it clear through actions or words if you are moving into combat against someone. Even something as simple as “I’m killing you” will suffice - or even placing paper at the entrance to a cave saying ‘KEEP OUT’. Wordlessly shooting people without any clear intent or reasoning may result in administrative action depending on the context. We are a roleplay server.
**Players are, by no means, required to emote. They may choose to do so if they please. Drawing a gun when in a heated situation, such as when a gun is already drawn on them, or even being visibly armed during a fight is clear intent enough to meet this requirement. Use proper reasoning and judgment.
**If a player makes their intent known (I.e ‘get on the ground, now’, ‘give me your shit’) - you, as the person receiving said demand, are not required to say anything further. You may retaliate with force at this point if you deem fit. Sometimes ICly is preferable to try and talk, but you are not required to. Just know that actions have consequences ICly and they may apply to you depending on the legality of the order or reasoning of it.

*You are restricted from engaging in round-to-round legal action outside of the specific circumstances described in the post-hoc investigations section of the law.

**You may however, use previous conflicts as a justification for hostility with a person. This falls under self-antagging rules if you decide to pick a fight on your own. You are allowed to do so, but you must accept the consequences for such as it will not be considered legal(E.G murdering your murderer the next round may be valid if self antag rules are followed - but legally it is still murder).

**Fax-complaints about character's behavior may be faxed inter-round. These faxes should clarify when the event took place and if it is relevant to a current ongoing situation in-round. When in doubt if you can act on an inter-round issue, fax or A-help.

== Do not powergame ==
*Better known as 'playing to win'. As a security person this can be seen as going out of your way and needlessly endangering others to ‘win against’ criminals. As the Colony AI exploiting loopholes in your laws to get yourself out of them or getting the person who subverted you into trouble is another way. There is an implicit allowance for lawed characters to ERP. You may create loopholes for this reason only.

*While this shares several things in common with other rules, it still is it's own entity. Play to have fun, allow yourself to lose now and again and roll with the blows as it can make things potentially even more interesting.

*Having '''way''' too many skills for one character is another example of this. Just because you're the premier and have access to everywhere doesn't mean you should (or can) know how to do all the different jobs. (See [[Character Creation#Give them a set of skills|Character Creation]] regarding skills for more information.)

*[[Identifying Antagonists]] when you shouldn't be able to is also a violation of this rule.

== Do not godmode ==
* Often confused with powergaming, godmoding is to create abilities out of nowhere, or do impossible things. If the action cannot be reasonably emulated in the confines of the game's mechanics, and it gives you some kind of advantage or is exceptionally weird, it's probably not allowed. For example, if you don't have access to a mechanic for turning invisible, you can't turn invisible. Saying you're invisible doesn't mean squat.

* Creating a character who is immune to injuries or pain also falls under this. The game won't let you ignore getting shot, why would any player allow it either?
** If your character is literally coded to ignore pain, you can ignore pain. Cyborgs and robots are a notable example. They do not feel pain. They are not immune to injury, however.

* Accidental injuries are still in-character injuries unless an admin heals you. Admin heals are generally out of character to void the injury.

* '''Admins who are caught abusing admin powers to godmod will be immediately dealt with.'''

== Do not abuse whispers ==
Any actions that would obviously be visible should not be hidden using whispers, this includes ERP, whispers longer than a sentence, or actions that would obviously be visible to anyone glancing you way. If you need to speak something longer than a sentence but want to keep it quiet use the whisper command. Anyone caught using whispers to hide obviously visible actions of paragraphs of texts will get slapped for it.

== Rules of ‘Self-Antag’ ==
Self-Antagging covers any antagonism that a player, using the resources available to them as a player, can perform. It is not the same as merely antagging with neither approval nor an appropriate event. When self-antagging:
* Your goal should be to provide fun for players in the round. Not just for yourself. Create scenarios others can enjoy and interact or involve other players who are receptive to your antics.
* Don’t Self-Antag without proper IC reasoning. Reasoning along the lines of "I'm bored" or "Giving Security something to do" is NOT a valid reason to be an asshole. Make sure your reason(s) are believable and why your actions make logical IC sense to any Admin.
* In a similar vein to the above, you can't invent a reason to antag. Suddenly deciding to hold someone hostage because your character needs money is poor show. Instead consider helping anyone who asks you for favours or cash, only to snap once you run out.
* Your main goal should be to get away with something and live to fight another day. Not to aim to murder everyone in your sight.
* Don’t break machines or items when you are self-antaging, steal them instead. If the item has no worth to you nor any credit worth, don’t take it. If it does or would sell for a pretty penny, you may steal it and use or pawn it off.
** Similarly, don’t destroy or otherwise effectively grief Soteria or other faction machines that are needed for life-saving or are not replaceable. I.e - cryotubes, surgery tables, RnD machines, etc.
** This includes infrastructure, such as atmospherics, or SMES's.
* Think about how a normal person would behave under similar circumstances. A well established character who has been around awhile may be given a bit of wiggle room to keep rounds interesting.
* By Self-Antaging, you are consenting to consequences to your actions. Be it from a normal player, or any result that may come from command or security personnel.
** Do not complain about the consequences you face upon doing such actions. Being fired, brigged, or killed - depending on the severity of your actions - are all possible outcomes. If you value your character and their reputation, don’t do it.
* Permissible self-antagging does *not* include things that give you a mechanical antag status, such as Excelsior implantation. All mechanical antagging must be approved by admins via ahelp (or by using the Crusade ritual; Crusaders are mechanically antags and the ritual just pings admins asking them to give you the status).
* By default, outsiders are neither allies nor antags by default. You should be playing them as characters that happen to live near the colony at the time.

Due to the importance of certain items or objects, to get permission to break into certain high security places or steal specific rare or strong objects requires staff permission first. These include:

* Breaking into any of the colony armories.
* The AI room or stealing the AI directly.
* Heads of Staff rooms to steal unreplaceable gear/artifacts.
* The spare ID in the Premier's office.
** The council may borrow the spare to handle activities such as issuing a new or missing ID, but are NOT to abuse it without A-helping first.

The key goal to self antagging is to create roleplay that is enjoyable or otherwise fun for players to interact with to differ from the norm. Below are a list of examples but you should always consider "are other people having fun or am I just being a dick?"

* Buying and selling contraband.
* Starting a drug production operation in a secluded spot in the colony.
* Disguising yourself as a specific department and gaining access to it while pretending to be a member of that department until someone notices.
* Extorting people for cash with a good old fashioned mugging.
* Stealing money, cutting profits, etc.

Now that the guidelines are out of the way, this rule set are examples of what self-antagonists are '''NOT''' to do without admin permission.

* Large explosives such as plasma bombs, max-caps, or any form of gas attack (such as the use of plasma fire flooding) are NOT allowed without admin permission.
** Grenades in casings and the like are, however, free to use as you see fit.
* Being a self-antag does not mean a license to murder. Doing so may result not only in perma-brig or a PK depending on your actions outcome, but staff involvement as well.
** Shooting at security while on the run for example is fully fine and acceptable rules-wise, but you are not to purposefully kill people at random.
Do not self antag more than once per day. This is generous as is, you shouldn’t be running around multiple rounds in a row breaking stuff, stealing stuff, etc. There is a fine line between a self-antagonist and a shitter.
* Do not use self-antagonism as an excuse to ruin a player's experience. This includes targeting players you know you do not like, providing purposefully no enjoyment to the situation for them, etc. It’s just dickish behavior.
* Do not start hostile actions within the first 15-30 minutes of the rounds start. You may use this as prep time, or A-help asking to start early if it’s something you feel you need to do to get the proper prep time to begin with.
** Similarly, you are to cease escalation of antagonism once a round end vote passes. Security may hunt for you, and you may retaliate in that case - but you are NOT to start self-antaging in the last 15 minutes of a round nor continue actions of self antaging.

Remember - we play on what most servers consider an “Extended round type” and pride ourselves, as a server, sith offering a persistent atmosphere where previous actions are considered ‘canon’ versus the normal SS13 experience of Groundhog Day. We do not have normal full blown antagonists, such as a murderous traitor, a serial killer, a wizard, or Steve from accounting having a bad day and deciding it’s hijack time. We are a PvE server that wishes to allow some players driven conflict and meaningful stories from said conflict.

IC consequences that occur from being caught range. The ‘permanent killing’ of your character in the case of heinous crimes, or other possibilities that players may decide within reason. It is for that reason that, by self-antaging, you are '''CONSENTING''' to these consequences for the action you have taken.

=== Outsiders & Self-Antaging ===

Outsiders hold some different rules and freedoms to self antaging than others. Outsiders may range from sane, understandable characters - to flawed individuals - to escaped convicts, cannibals, and deranged individuals. As such, their Self antaging takes different forms.

This section is a short one regarding outsiders and their self-antaging specifications. Outsiders hold different restrictions and freedoms from a colonist or lodge member deciding to self-antag. This section will outline these points below.

* Outsiders, unlike colonists, may resort to murder more quickly and for simpler reasons than a colonist. You are still not to make a target unrevivable, destroy their body, or otherwise hide the body without admin permission.
** That being said, you may do amputations of a body part or two as - say - some antagonistic type of cannibal. But do not go past this limit. Be reasonable
* Outsiders are still expected, as others, to give some form of indication of intent or use clear wording of what they want or are doing. Mugging someone? Say what you want. Telling someone to get lost? Draw your gun and tell them to get out.
** Paper notes may also be placed at, say, the entry to your house or on the door warning ‘trespassers will be shot’ as a means to make intentions clear or stake ownership of an area/building. Doing so means you may shoot violators, just as colonists do to infiltrators or trespassers.
* Outsiders may freely use traps, mines, and mobs to aid in their self-antaging. Be tasteful and do not use them on tiles, such as Z-transitions or staircases, or under trees completely. You may use them on ladders though as players can see down them before climbing.
* Breaking into the colony is acceptable to do, but you are to obey the previous rules regarding what can be stolen or broken into. Off limit areas, such as armories or the premiers spare ID requires admin permission.
* Finally, remember - colonists and hunters may kill you just as freely as you may kill them. They are required, as you are, to make their intentions clear. But you do not have the legal protection of a colonist. By playing outsider and, by any means acting strange or akin to a self antag, you lose the right to complain about the consequences that come to you.

== You are expected to perform the job you signed up for ==
When your character joins the round, you are accepting the responsibilities that the job you have chosen brings with it. Remember: if you are playing in a slot, you are likely preventing other players from performing that role. It is important that you fulfill the tasks that you have signed up for!
*Marhals should protect the colony from danger, the guild should ensure that power is up and that people can breathe, medical should provide treatment to injuries and other services, cargo should bring in needed cargo on request, Science should do... science stuff, and service should provide food. Command's job is to make sure at least these basics are being fulfilled, and to react accordingly in an emergency.

*A player must take into account the qualifications (both physical and mental) of their character’s role before placing them into it. If staff find your character to be unsatisfactory in fulfilling the requirements of the role, we may instruct you to revise your character.
**This includes majorly disabled characters — quadruple amputees, deaf, or blind characters, and so on — which are only permitted on the colony in the assistant (and associated alt-titles) job slot.

*Repeatedly failing to perform to an acceptable standard can result in a ban untill appealed.

*If you are going AFK for an extended period of time (more than 15 minutes), and are occupying a limited-number job slot (any slot other than assistant), you must remove your character from the round using a cryopod (or other similar means) to free the slot. Repeated failure to do this may result in being banned from that job.

*Do not do other people’s jobs. If you joined as medical, do not attempt to hunt down criminals. If you joined as engineering, do not attempt to perform medical treatment on your coworkers. If you are a head position, allow your staff to do work before you do the work yourself; you are a supervisor and manager first and foremost as a head position.

*Do not hijack other people's jobs. For example, if you're a roboticist but someone needs surgery, and there's already a surgeon who isn't currently busy, then don't perform the surgery instead of letting them do it. Similar examples exist with every department, so use your judgement. Basically, if you're ''actively getting in the way'' of someone else trying to do their job, you're probably breaking this rule.

*Playing jobs that can be called upon at any time to assist other crew members in emergencies waives your right to have interruption-free (E)RP sessions in private, including the dorms. If you join as a Lifeline Tech, expect to be interrupted out of private scenes. If you’re an engineer, you are expected to set up power systems and repair any large-scale damage that hampers the rest of the crew, regardless of your intent to have sex with the assistants. (Example: The premier getting their rocks off with someone while they are being called to assist with colony matters. They signed up to be the arbiter of colony matters. ERP is not what you are here for in that role. "saying you are busy or occupied")

*If you do prospecting as an non-prospector for more than 30-60 minutes without being in an expedition with them and you are not doing your job, you may get a talking to. If you want to play like a prospector - just play the job instead of ignoring the one you signed up for.

*Maintenance diving is not a valid reason to be busy from your assigned job. If you are requested to perform the actions of your role while maintenance diving it is expected that you make your way out of maintenance in a timely manner.

== You are expected to obey the chain of command (within reason) ==
*Each head of staff is the de facto leader of their department, so listen to them. Likewise, you should obey decisions from faction owners (if a fax arrives) or council decisions unless directly overridden by an admin. If you consistently do not follow reasonable orders, you will be job banned.

*If you're playing a role that has [[AI#Interpreting_Your_Laws|AI laws]], you must obey these laws first and foremost to the best of your ability.

*As any role without AI laws, you can disobey orders you think are traitorous, harmful, immoral, or violating [[Laws]]. Use your judgement and consider whether or not disobeying the order could get you in trouble or get someone else horribly killed.

*If you are given an order or AI law that may break another server rule, please alert the admins for a second opinion before continuing.

Mind you, this is '''not''' a rule that lets people be fun police as heads of staff. If you feel that someone is ordering you do things that basically require you ''not'' to do your job, or to do your job in ways that aren't important/fun, then contact an admin for a second opinion or fax a faction owner in character.

== You are expected to forget events that are deemed non-canon ==
*This is to keep things a little more sane in-round, and to allow for players with preferences in non-consensual activities to have their fun with people who share those prefs as victims. It is therefore against this rule to remember and abuse the knowledge of who killed/raped after the round has passed unless both people involved agree. You should not have the memory to antagonize or persecute your attacker without the prior OOC agreement of the other parties in the roleplay. They can include this consent in their OOC Metainfo/Notes or discuss it with you in LOOC before or after the roleplay.

*Keep in mind that non-consensual RP, while OOC, is fine it is not on an IC level. Characters who make their non-con actions public or get caught in the act can and will be permanently killed if caught. For example, if a person is tried and executed for rape that character is permanently dead and cannot reappear on the colony. If you wish to do non-con keep it private. '''You've been warned.'''

*The round ending does not make you immune to a character perma-kill. Just because you evaded capture or was not killed by the time it restarted does not mean everyone forgets what your character did. If you get caught and the evidence is ironclad enough, you will be PK'd.

*This rule also applies to events that cause catastrophic damage to the colony, such as a code red/delta scenario. As a general rule event coordinators '''should''' say before or after an event if it is non-canon or not.

*If you are killed in a round and then revived in the same round, you're memory is entirely intact and may act accordingly.

*As a general rule, player deaths in round will be considered 'soft canon'. That the character died is canon, the exact details are left vague - this is to ensure that instances of a character being gibbed, eaten by a hivemind, etc - do not either result in a forced PK, nor lore-breaks wherein said character is magically back. Players are encouraged to come up with a believable explanation as to the particular details and others are expected to not reference the original and actual events.

*In line with the above, such 'retellings' of events must be in line with server lore particularly [https://sojourn13.space/wiki/Transhumanity Transhumanity] and the The Law of Inviolability.

= The intent of the rules is more important than the letter =
The purpose of the rules is to preserve a fun and enjoyable environment for all players. If everyone is enjoying themselves even while the ‘letter’ of a rule is not being followed, it’s likely that no staff intervention will be required. On the other hand, just because something isn't in the rules doesn't mean it's okay or allowed if it's upsetting a large number of players.

*It is within admin staff's discretion to decide that certain actions violate one or more rules, even if the specific action is not listed as part of the rule. This is simply the job of the staff to interpret the rules. You can appeal decisions to other admins if you believe one has a bias against you, but doing so after a ruling is passed will get you in trouble.

*Plenty of rules are left vague enough to cover as much as possible without being too oppressing. Attempting to rules-lawyer saying that "this rule doesn't specifically say I can't do X", even if what you are doing is disrupting the server, will generally be ignored. We assume most of you have enough common sense to recognize what a [[#Create_and_play_server-appropriate_characters|sane and stable individual]] would and wouldn't do within this fictional setting.

=== Listen to admin staff ===
* One admin's word is usually as good as any other. Though, just because one admin says something is okay in that moment does not mean it will always be okay under another admin or even the same admin.
** If this causes a contradiction, you can (and should) inform the new admin of what you were told previously. For example, a Head Admin says you can do something, but that admin has left the server. A lower ranked admin shows up and asks you to stop doing that thing. You can explain that the Head Admin previously said you could do this, but if the lower ranked admin ''still'' wants you to stop, then you should stop. (This obviously works vise-versa as well.)
** Intentionally not telling a new admin about a contradiction is considered lying. It's like asking your mom for ice cream, but she says no, so you go ask dad because you think he'll be less strict.
* Sojourn is not a straight democracy; our rules and guidelines exist for a reason and we have staff dedicated to enforcing them and help set further guidelines if necessary. '''However, these rules are always going to be incomplete, and as such, just because something isn't written doesn't mean it's allowed.''' If a staff member tells you to do something, do it. They tell you to stop, then stop. If you disagree with a ruling, don't try to argue it then and there, especially if things are hectic. Once things have calmed down, or preferably after the round has ended, you can try to contact the staff member privately to discuss the ruling, or talk to another admin if you cannot talk to or cannot convince the offending admin.

* If you have a question over something unclear or questionable, never be afraid to adminhelp. The staff on hand should discuss it among themselves and give you a ruling, from there on if the ruling is in bad judgement, it's on the admin who cleared it, not ''you''. '''The staff should also NEVER ban you purely for a complaint against them.''' Even if you're a complete asshole about it, as long as the argument stays private, you cannot be banned just for arguing. Although being an asshole usually won't win an argument, so you probably shouldn't do that anyway.
** Don't confuse this for "complaining grants you immunity to bans", because that's not how it works. If you are told to not break windows and you complain how that isn't fair, you're still getting banned for breaking windows if we disagree with your complaint. What this means is we won't ban you or make an existing ban worse just because you tell us we're being excessively mean, confusing, or unfair to you or someone else.

[[Category:Guides]]
[[Category:Rules]]

Moderator

2024-12-15T17:43:51Z

K5:

{{SidebarStaff}}

Moderators are the lower rank of the administrative branch. Their responsibilities lie in the straight-forward elements of server administration, and their role is primarily to collect information and correct player misbehaviour, rather than explicitly punishing the players.

== Letter of the Law ==
Moderators enforce the rules as written, however they are only empowered to take minor actions against denizens. As such, in the pursuit of enforcement, their role is more informative: they investigate and produce a complete summary of the situation, then present it to Administrators alongside a recommendation of what action should be taken.

== Player Guidance ==
When players aren't acting with impunity, the moderator is also responsible for guiding and correcting their mistakes. In the simplest situations, that means messaging them to inform them of the error. Usually, however, the moderator should undertake questioning before attempting to judge whether an activity is against the rules. Patience is a virtue here: unless the situation is truly urgent, moderators should allow the player to play through whatever situation they're currently in before initiating the conversation.

== Whitelist Applications ==
It is also the responsibility of the moderator to approve whitelists. The most important element of the whitelist to verify is age: absolutely no players under the age of 18 should be permitted to play on Sojourn. Beyond that, other points to consider are applicants' skill in writing English within a fast-paced roleplay environment, their understanding of what high roleplay means, and their understanding of consequences. While a ban history outside Sojourn is not usually a sufficient reason to deny an application, moderators have discretion in how to interpret such records. For example, someone with a long sequence of recent bans may be on the hunt for another server to misbehave on, whereas someone with many older bans may be given the benefit of the doubt and allowed the opportunity to demonstrate their reform.

== Logging ==
While the burden of ensuring all faxes (and any relevant tickets or ahelps) are appropriately logged falls to all staff with access to view them, moderators are explicitly tasked with recording them.

Main Page

2024-12-05T13:49:15Z

K5: Removes the mediawiki default links from the main page.

{| id="mp-topbanner" style="width:100%; Lore:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;"
| style="width:56%; color:#000;" |

{| style="width:100%; border:none; background:none; margin-left: 0em"
| style="text-align:center; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the '''Sojourn Station Wiki'''</div>
<div style="position: relative; top:0.2em; font-size:95%;">Read the '''[[Rules]]''' and join us at: '''https://sojourn13.space/wiki/Discord'''
</div>
|}
|}


{| style="margin:4px 0 0 0; width:100%; background:none;"
| class="MainPageBG" style="width:100%; border:1px solid #ddcef2; background:#faf5ff; vertical-align:top; color:#000;" |
{| style="vertical-align:top; text-align: center; background:#fcf9ff; color:#000; width:100%"
! style="padding:2px" | <div id="np-g" style="margin:3px; font-size:150%; font-weight:bold; border:1px solid #dfd3ef; text-align: center; color:#000; padding:0.1em
p0.1em">[[Image:Assistant_in_Shuttle.png]] New to Sojourn Station? [[Resources for New Players|Then here's where you can start to get a basic grasp of things]] and here's the [[Mission Statement]]</div>We also have a bugtracker at '''[https://github.com/sojourn-13/sojourn-station/issues Github]'''
We are a downstream of Eris, located '''[http://wiki.cev-eris.com/ here!]'''
|}



{| style="margin:4px 0 0 0; width:100%; background:none;"
| class="MainPageBG" style="width:100%; border:1px solid #ddcef2; background:#faf5ff; vertical-align:top; color:#000;" |
{| style="vertical-align:top; background:#faf5ff; color:#000; text-align: center; width:100%; font-size:2em; font-weight:bold;"
| [[Image:IconJobs.png|150px|link=Jobs]] [[Jobs]] 
| [[Image:Sojourn.png|150px|link=Lore]] [[Lore]] 
| [[Image:IconObjects.png|150px|link=Objects]] [[Objects]] 
| [[Image:IconTips.png|150px|link=Guides]] [[Guides]] 
|-
|}
|}



{| style="margin:4px 0 0 0; width:100%; background:none;"
| class="MainPageBG" style="width:100%; border:1px solid #ddcef2; background:#faf5ff; vertical-align:top; color:#000;" |
{| style="vertical-align:top; background:#faf5ff; color:#000; text-align: center; width:100%; font-size:2em; font-weight:bold;"
| [[Chain of Command|High Council]] 
| [[Core Species|Species]] 
| [[Critters|Monsters]] 
| [[Laws]] 
|-
|}
|}

{| style="margin:4px 0 0 0; width:100%; background:none;"
| class="MainPageBG" style="width:100%; border:1px solid #ddcef2; background:#faf5ff; vertical-align:top; color:#000;" |
{| style="vertical-align:top; background:#faf5ff; color:#000; text-align: center; width:100%; font-size:2em; font-weight:bold;"
| [[Tips]] 
| [[List of Factions|Colony Factions]] 
| [[Vending Machines]] 
| [[Standard Operating Procedure|SOP]] 
| [[Example Paperwork]] 
|-
|}
|}

|}

{{Guides|state=plain}}

Template:SidebarStaff

2024-12-05T13:43:58Z

K5:

{{Sidebar
| name=SidebarStaff

| title=Administration
| above=[[Server Policy]]

| heading1=Staff Ranks
| content1={{Sidebar | child=yes
| contentclass=hlist

| heading1=[[Server Oversight|Oversight]]
| content1=
* [[Head Administrator]]
* [[Staff Head]]
* [[Game Master]]
* [[Liaison]]

| heading2=Administration
| content2=
* [[Head Administrator]]
* [[Administrator]]
* [[Moderator]]
| heading3=Showrunning
| content3=
* [[Game Master]]
* [[Event Operator]]

| heading4=Staff
| content4=
* [[Staff Head]]
* [[Code Staff]]
* [[Lore Staff]]
* [[Staff Member|Staff (General)]]

}}

| heading2=Policies
| content2={{Sidebar | child=yes
| contentclass=hlist

| heading1=Oversight Policy
| content1=
* [[Headmin Domain]]
* [[Staff Head Purview]]
| heading2=Administrative Policy
| content2=
* [[Tickets]]
* [[Banning]]
* [[Appeals]]
* [[Rules]]
| heading3=Showrunning Policy
| content3=
* [[Event Checklist]]
* [[Event Archetypes|Archetypes]]
| heading4=Development Policy
| content4=
* [[Contributor Guide]]
* [[Coding Standards]] [[Features|(Features)]]
* [[Lore Writing]]
| heading5=Staff Policy
| content5=
* [[Code of Conduct]]
* [[Disclosure]]
| heading6=Player Policy
| content6=
* [[Persistency]]
* [[Roleplay]]

}}
}}<includeonly>[[Category:Staff]]</includeonly>

Game Master

2024-12-05T13:41:05Z

K5: /* Event Oversight */

Game Master

2024-12-05T13:39:56Z

K5:

Event Operator

2024-12-05T13:15:14Z

K5:

{{SidebarStaff}}

Event Operators are staff trained to handle the game's tools. They're capable of running approved events single-handedly, as well as helping other event operators with their events when more than one pair of hands is needed. Event Operators answer to [[Game Master|Game Masters]] and receive in-game permissions from them alongside event approval.

== Event Running ==
Formally, events are run by the Game Master that approves the event, with the assistance of the creator of the event. This leaves the role of the Operator primarily in the mechanical running of the event as described in the event plan, and following any other instructions.

In practice, the event team communicates to run the event smoothly and make any necessary adjustments as needed. More often than not, an event will be run by the Operator who created it, and will have extra flexibility in adjusting the event to suit their intentions.

== Event Composition ==
Beyond simply running an event, Operators also are the primary contact point of any denizens who want to create an event. They're responsible for guiding the denizen through the [[Event Checklist]] and making sure all the steps are followed to produce a great event. Once the event is ready, the Operator is also responsible for submitting it for review, along with an assurance that the denizen's event was built correctly.

Given their intimate relationship with the event process, Operators themselves receive extra privileges:

* They are not restricted to following the [[Event Checklist]] step by step, and may submit an event plan for approval without any prior communication.
* They may fast-track their event's approval process by having relevant development staff pre-approve lore and code elements or changes, allowing the Game Master to simply verify the approval once submitted.


<references />

Event Operator

2024-12-05T13:10:34Z

K5:

{{SidebarStaff}}

Event Operators are staff trained to handle the game's tools. They're capable of running approved events single-handedly, as well as helping other event operators with their events when more than one pair of hands is needed. Event Operators answer to [[Game Master|Game Masters]] and receive in-game permissions from them alongside event approval.

== Event Running ==
Formally, events are run by the Game Master that approves the event, with the assistance of the creator of the event. This leaves the role of the Operator primarily in the mechanical running of the event as described in the event plan, and following any other instructions.

In practice, the event team communicates to run the event smoothly and make any necessary adjustments as needed. More often than not, an event will be run by the Operator who created it, and will have extra flexibility in adjusting the event to suit their intentions.

== Event Composition ==
Operators have extra privileges in the production of an event compared to others:

* They are not restricted to following the [[Event Checklist]] step by step, and may submit an event plan for approval without any prior communication.
* They may fast-track their event's approval process by having relevant development staff pre-approve lore and code elements or changes, allowing the Game Master to simply verify the approval once submitted.


<references />

Template:SidebarStaff

2024-12-04T21:29:54Z

K5:

{{Sidebar
| name=SidebarStaff

| title=Administration
| above=[[Server Policy]]

| heading1=Staff Ranks
| content1={{Sidebar | child=yes
| contentclass=hlist

| heading1=[[Server Oversight|Oversight]]
| content1=
* [[Head Administrator]]
* [[Staff Head]]
* [[Game Master]]
* [[Liaison]]

| heading2=Administration
| content2=
* [[Head Administrator]]
* [[Administrator]]
* [[Moderator]]
| heading3=Showrunning
| content3=
* [[Game Master]]
* [[Event Operator]]

| heading4=Staff
| content4=
* [[Staff Head]]
* [[Code Staff]]
* [[Lore Staff]]
* [[Staff Member|Staff (General)]]

}}

| heading2=Policies
| content2={{Sidebar | child=yes
| contentclass=hlist

| heading1=Oversight Policy
| content1=
* [[Headmin Domain]]
* [[Staff Head Purview]]
| heading2=Administrative Policy
| content2=
* [[Tickets]]
* [[Banning]]
* [[Appeals]]
* [[Rules]]
| heading3=Showrunning Policy
| content3=
* [[Event Checklist]]
* [[Event Archetypes|Archetypes]]
| heading4=Development Policy
| content4=
* [[Contributor Guide]]
* [[Coding Standards]] [[Features|(Features)]]
* [[Lore Writing]]
| heading5=Staff Policy
| content5=
* [[Code of Conduct]]
* [[Disclosure]]
| heading6=Player Policy
| content6=
* [[Persistency]]
* [[Roleplay]]

}}

| below=This template is currently incomplete; some data is misplaced for testing purposes. Do not create pages from the redlinks.
}}<includeonly>[[Category:Staff]]</includeonly>

Staff Head

2024-12-04T21:20:37Z

K5:

{{SidebarStaff}}

Staff Heads are senior members of Sojourn's development team. The task of maintaining and improving Sojourn is split among the Staff Heads, who are each tasked with one or more aspects of the server to oversee. While they may be capable of contributing directly, Staff Heads are responsible for curating submissions from contributors and guiding developers and writers respectively.

== Mandates ==
Staff Heads receive complex mandates regarding what they should and shouldn't focus on within their sphere. Each mandate is categorized into a group:

; Code : These mandates focus on the technical well-being of the server, and are responsible for implementing features and elements within the game. Also responsible for the game's balance.
; Lore : These mandates maintain a healthy and enthralling lore base, and integrating all approved proposals sensibly into the existing lore. Also responsible for the wiki's completeness.
; Rules : These mandates are concerned with player-facing matters that directly influence interactions between players on the live server. Rules, SOP and Laws all fall under this umbrella.

== Contribution Policies ==
Staff Heads are responsible for the policies by which contributions are judged, and the processes necessary for converting an idea into a finished contribution.

See [[Contributor Guide]] and [[Coding Standards]].

== Quality Control ==
Staff Heads also have the final say in whether or not a contribution is of sufficient quality to be integrated. A lore contributor could write a wonderful story, but if it's full of typos and awkward phrasing the submission may be rejected until capable. For code, this involves maintaining code standards and the cleanliness of the code tree.

Keep in mind that there are multiple ways that a contribution may fail to be of appropriate quality.

For one, contributions should mesh appropriately with all aspects of the server; a lore writer is no more empowered to demand the existence of a nonexistent in-game item as a coder is to add accessible features that are completely unsupported by lore. Unless both aspects are resolved together through one interdisciplinary contribution, neither is desirable.

Contributions should be coherent and cohesive. An amazing change to the lore, if incomprehensible to any but the most studious of Sojourn scholars, is no more desirable than a new game mechanic that is utterly divorced from the game proper. Both can most likely be fixed, and should be to be approved.

Completeness is key as well. Staff Heads are the highest line of secrecy when it comes to upcoming features and releases, but not releasing a whole change at once is different from not having the whole change ready. Whether it be a multi-part lore writeup that gets drip-fed to players, or incremental changes to a department's layout to transition players smoothly into it, the final product should be available before the intermediates go live.

== Staff Vetting ==
Though the task of staff changes falls to Head Administrators, it is up to relevant staff heads to determine an applicant's continued competency in the matter. For well known applicants with a track record, simply examining their contributions may be enough to produce a recommendation. If others are being considered, staff heads are also expected to ask appropriate questions or set tasks to test the applicant's competency.

Keep in mind that anyone may contribute; one does not need a rank within staff to code or write. The staff roles grant credibility and a level of authority to the contributor, and directs other staff to consult with them when necessary. Anyone withholding their contributions for lack of a staff rank should have their value and intentions particularly well scrutinized.

Template:SidebarStaff

2024-12-04T20:55:33Z

K5:

{{Sidebar
| name=SidebarStaff

| title=Administration
| above=[[Server Policy]]

| heading1=Staff Ranks
| content1={{Sidebar | child=yes
| contentclass=hlist

| heading1=[[Server Oversight|Oversight]]
| content1=
* [[Head Administrator]]
* [[Staff Head]]
* [[Game Master]]
* [[Liaison]]

| heading2=Administration
| content2=
* [[Head Administrator]]
* [[Administrator]]
* [[Moderator]]
| heading3=Showrunning
| content3=
* [[Game Master]]
* [[Event Operator]]

| heading4=Staff
| content4=
* [[Staff Head]]
* [[Coder]]
* [[Lore Writer]]
* [[Staff Member|Staff (General)]]

}}

| heading2=Policies
| content2={{Sidebar | child=yes
| contentclass=hlist

| heading1=Oversight Policy
| content1=
* [[Headmin Domain]]
* [[Staff Head Purview]]
| heading2=Administrative Policy
| content2=
* [[Tickets]]
* [[Banning]]
* [[Appeals]]
* [[Rules]]
| heading3=Showrunning Policy
| content3=
* [[Event Checklist]]
* [[Event Archetypes|Archetypes]]
| heading4=Development Policy
| content4=
* [[Contributor Guide]]
* [[Coding Standards]] [[Features|(Features)]]
* [[Lore Writing]]
| heading5=Staff Policy
| content5=
* [[Code of Conduct]]
* [[Disclosure]]
| heading6=Player Policy
| content6=
* [[Persistency]]
* [[Roleplay]]

}}

| below=This template is currently incomplete; some data is misplaced for testing purposes. Do not create pages from the redlinks.
}}<includeonly>[[Category:Staff]]</includeonly>

Server Policy

2024-12-02T04:10:59Z

K5:

{{Stub}}
This page's contents are being migrated to their respective pages. Contents may be outdated.
[[Category:Staff]]

{{SidebarStaff}}

== Staff Roles ==
''This section is incomplete but accurate.''

=== Administrative Staff ===
Administrative staff handle all things to do with player activities on server. It is the role of the administration to determine where player actions contravene the server and to act to correct such instances.

==== Head Administrator ====
Head Administrators oversee the server as a whole, and act to maintain the administration rather than directly administering. Individually, they can override rulings made by administrators and moderators. Together, they can override decisions on server direction as made by the staff heads, as well as rulings made by individual headmins.

In the event that an administrator is unavailable, a head administrator may step in to act. However, this is discouraged, as receiving a ruling directly from a head administrator may leave a player feeling unable to seek appeal or recourse at a higher level.

==== Administrator ====
Administrators rule on player situations that need more complicated solutions than fall within a moderator's prerogative. Excessive rule-skirting, undesired behaviour and other complex issues fall under the Administrators' purview. Administrators also act as agents in enforcing IC rulings where the High Council is involved, and respond to faxes with the full authority of the council.

==== Moderator ====
Moderators act on straightforward issues involving player actions. Generally, this simply means enforcing rules as written in a cut and dry fashion, and helping collect information on situations that an Administrator would otherwise rule on. Moderators are the first line in ensuring that the server stays on track and appropriately in tone.

Moderators do not act on behalf of the High Council when exercising their moderation powers, but may make informational responses to faxes as supporting staff to a specific councillor.

As moderators do not have some server permissions granted directly to them, many of their rulings may need to have an administrator rubber stamp them and apply them.

=== Supporting Staff ===
Supporting staff handle all things to do with the server's state and development.

==== Staff Head ====
Staff Heads oversee the development of the server. Each one is given a specific family of tasks to oversee or maintain. Each staff head is either particular to Lore or Code tasks, and when there are four staff heads within either group, one of that group is granted the additional task of foreperson.

An additional, unique Staff Head role exists for maintaining the Rules. This role is also granted the powers and authority of an administrator, but is generally expected to focus on finding flaws in the rules and easing them out, over enforcing them, and to handle rule changes as dictated by headmins.

Staff Heads may respond to faxes regarding clear cut IC issues, in the same fashion as a moderator.

==== Game Master ====
A Game Master creates and runs larger events that may affect the lore or have permanent effects. They may also run normal events at will and create their own stories. Game Masters may also approve events by event operators.

Within the context of an event they are operating, Game Masters also receive authority just above that of a moderator.

==== Event Operator ====
Event Operators run normal events with the approval of a Game Master or Administrator. They also assist in events being run by Game Masters.

==== Developer ====
A member of development staff empowered to inspect and debug the server live, as well as provide technical support on the server where pertinent.

==== Development Staff ====
A contributor elevated to the rank of staff. Has a louder voice when making proposals to how the server should be improved. Is expected to be accurately authoritative when it comes to statements about the server. Works with the staff heads to make sure features are consistent with the playerbase's expectations.

=== Special Staff ===

==== Host ====
The font of all power, from which it is all delegated. Has final, unshakable authority over the server, when used.

==== Liaison ====
A player dedicated not to the server itself, but to the playerbase. Represents the playerbase within higher channels than regular staff, including a direct line of communication to the headmins and staff heads.

==== Regular Staff ====
A normal player elevated to the rank of staff, who participates in staff discussions, including those involving development staff, providing a layperson's perspective on changes and staff activities.

== Player Guidelines ==
This section details how players should interact with the administration in certain situations.

=== Appeals ===
Both moderator and administrator rulings may be appealed. Once the appeal is submitted, a Head Administrator will appoint an Administrator to review the case, or in some circumstances, decide to review the case personally. The appointed administrator may not be the administrator who ruled, and should avoid being the administrator who applied a moderator's ruling.

=== Feature Issues, Development Complaints & Bug Reports ===
* Complaints should only be directed at Head Administrators.
* Issues with features that are neither complaints nor bugs should be posted on the issue tracker, though the appropriate Staff Head is also a valid recipient.
* Finally, bug reports may be discussed directly with the developer of a feature if they are particularly pressing or part of a testmerged PR.

The definitions of the three are left intentionally vague, but bad faith reports will be dealt with.

== Administration Policies ==

=== Development and Staff Head Policies ===

==== Staff Head Overruling ====
Staff Heads have mostly unilateral powers when their task. However, tasks overlap, and the whole server is, in the end, a collective development effort. As such there are a handful of ways for them to overrule each other.

* If both forepersons and the Rules staff head agree, a decision can be overruled immediately.
* If there is a foreperson, they can start a motion to overrule a decision made by one of the heads in their group. This vote must be unanimous, with the exception of the head that made the decision. In the case of a foreperson's overruling, a headmin can instead start that vote.
* With the approval of a headmin, all staff heads may undertake a standard vote (with abstention permitted). Headmins may vote in this as well.
* Finally, a 66% supermajority of headmins may make a final decision on a matter.

=== On-Server Powers ===

==== Sounds ====
* Sounds should not be used gratuitously. Save admin sounds for events and other worthwhile situations.

Server Policy

2024-12-02T01:20:26Z

K5: /* Staff Head Overruling */

{{Stub}}
[[Category:Staff]]

{{SidebarStaff}}

== Staff Roles ==
''This section is incomplete but accurate.''

=== Administrative Staff ===
Administrative staff handle all things to do with player activities on server. It is the role of the administration to determine where player actions contravene the server and to act to correct such instances.

==== Head Administrator ====
Head Administrators oversee the server as a whole, and act to maintain the administration rather than directly administering. Individually, they can override rulings made by administrators and moderators. Together, they can override decisions on server direction as made by the staff heads, as well as rulings made by individual headmins.

In the event that an administrator is unavailable, a head administrator may step in to act. However, this is discouraged, as receiving a ruling directly from a head administrator may leave a player feeling unable to seek appeal or recourse at a higher level.

==== Administrator ====
Administrators rule on player situations that need more complicated solutions than fall within a moderator's prerogative. Excessive rule-skirting, undesired behaviour and other complex issues fall under the Administrators' purview. Administrators also act as agents in enforcing IC rulings where the High Council is involved, and respond to faxes with the full authority of the council.

==== Moderator ====
Moderators act on straightforward issues involving player actions. Generally, this simply means enforcing rules as written in a cut and dry fashion, and helping collect information on situations that an Administrator would otherwise rule on. Moderators are the first line in ensuring that the server stays on track and appropriately in tone.

Moderators do not act on behalf of the High Council when exercising their moderation powers, but may make informational responses to faxes as supporting staff to a specific councillor.

As moderators do not have some server permissions granted directly to them, many of their rulings may need to have an administrator rubber stamp them and apply them.

=== Supporting Staff ===
Supporting staff handle all things to do with the server's state and development.

==== Staff Head ====
Staff Heads oversee the development of the server. Each one is given a specific family of tasks to oversee or maintain. Each staff head is either particular to Lore or Code tasks, and when there are four staff heads within either group, one of that group is granted the additional task of foreperson.

An additional, unique Staff Head role exists for maintaining the Rules. This role is also granted the powers and authority of an administrator, but is generally expected to focus on finding flaws in the rules and easing them out, over enforcing them, and to handle rule changes as dictated by headmins.

Staff Heads may respond to faxes regarding clear cut IC issues, in the same fashion as a moderator.

==== Game Master ====
A Game Master creates and runs larger events that may affect the lore or have permanent effects. They may also run normal events at will and create their own stories. Game Masters may also approve events by event operators.

Within the context of an event they are operating, Game Masters also receive authority just above that of a moderator.

==== Event Operator ====
Event Operators run normal events with the approval of a Game Master or Administrator. They also assist in events being run by Game Masters.

==== Developer ====
A member of development staff empowered to inspect and debug the server live, as well as provide technical support on the server where pertinent.

==== Development Staff ====
A contributor elevated to the rank of staff. Has a louder voice when making proposals to how the server should be improved. Is expected to be accurately authoritative when it comes to statements about the server. Works with the staff heads to make sure features are consistent with the playerbase's expectations.

=== Special Staff ===

==== Host ====
The font of all power, from which it is all delegated. Has final, unshakable authority over the server, when used.

==== Liaison ====
A player dedicated not to the server itself, but to the playerbase. Represents the playerbase within higher channels than regular staff, including a direct line of communication to the headmins and staff heads.

==== Regular Staff ====
A normal player elevated to the rank of staff, who participates in staff discussions, including those involving development staff, providing a layperson's perspective on changes and staff activities.

== Player Guidelines ==
This section details how players should interact with the administration in certain situations.

=== Appeals ===
Both moderator and administrator rulings may be appealed. Once the appeal is submitted, a Head Administrator will appoint an Administrator to review the case, or in some circumstances, decide to review the case personally. The appointed administrator may not be the administrator who ruled, and should avoid being the administrator who applied a moderator's ruling.

=== Feature Issues, Development Complaints & Bug Reports ===
* Complaints should only be directed at Head Administrators.
* Issues with features that are neither complaints nor bugs should be posted on the issue tracker, though the appropriate Staff Head is also a valid recipient.
* Finally, bug reports may be discussed directly with the developer of a feature if they are particularly pressing or part of a testmerged PR.

The definitions of the three are left intentionally vague, but bad faith reports will be dealt with.

== Administration Policies ==

=== Development and Staff Head Policies ===

==== Staff Head Overruling ====
Staff Heads have mostly unilateral powers when their task. However, tasks overlap, and the whole server is, in the end, a collective development effort. As such there are a handful of ways for them to overrule each other.

* If both forepersons and the Rules staff head agree, a decision can be overruled immediately.
* If there is a foreperson, they can start a motion to overrule a decision made by one of the heads in their group. This vote must be unanimous, with the exception of the head that made the decision. In the case of a foreperson's overruling, a headmin can instead start that vote.
* With the approval of a headmin, all staff heads may undertake a standard vote (with abstention permitted). Headmins may vote in this as well.
* Finally, a 66% supermajority of headmins may make a final decision on a matter.

=== On-Server Powers ===

==== Sounds ====
* Sounds should not be used gratuitously. Save admin sounds for events and other worthwhile situations.

Standard Operating Procedure (DNR)

2024-12-01T21:27:28Z

K5: Created page with "{{stub}} {{SOP}}"

Template:SOP

2024-12-01T21:27:21Z

K5:

{{Sidebar
| name = SOP

| title = [[Standard Operating Procedure]]

| heading1 = General
| content1class = plainlist
| content1 =
* [[Standard Operating Procedure (Command)|Command]]
* [[Standard Operating Procedure (General)|General]]
* [[Standard Operating Procedure (Legal)|Legal]]
| heading2 = Departmental
| content2class = plainlist
| content2 =
* [[Standard Operating Procedure (Marshals)|Marshals]]
* [[Standard Operating Procedure (Blackshield)|Blackshield]]
* [[Standard Operating Procedure (Prospectors)|Prospectors]]
* [[Standard Operating Procedure (Soteria Medical)|Medical]]
* [[Standard Operating Procedure (Soteria Research)|Research]]
* [[Standard Operating Procedure (Guild)|Guild]]
* [[Standard Operating Procedure (Lonestar & Service)|Lonestar]]
* [[Standard Operating Procedure (Church)|Church]]
| heading3 = Special
| content3class = plainlist
| content3 =
* [[Standard Operating Procedure (DNR)|Revival]]
}}<includeonly>[[Category:Standard Operating Procedure]]</includeonly>

Persistency

2024-12-01T21:24:59Z

K5: Created page with "{{SidebarStaff}}"

Law

2024-11-26T02:59:44Z

K5: Redirected page to Laws

#REDIRECT [[Laws]]

Staff Head

2024-11-26T02:48:03Z

K5:

Contributor Guide

2024-11-26T02:26:17Z

K5:

{{SidebarStaff}}

== Rules ==
* PRs may be put forth are not necessarily supported by their creator. They may be made on behalf of others or even just on a notion. All are free to make Pull Requests for consideration and ultimate responsibility for the inclusion(or exclusion) on content falls squarely on the head of the Lead-Dev. No coder should be shouted at solely for a change they've requested. 
*Players and admins shall not dictate to devs or contributors how they 'must' spend their time coding. While changes will invariably become necessary for any number of reasons(story arcs, balance, etc) these changes should either be requested, or directly given to the lead-dev to determine implementation. At the end of the day, all developers who work on this project do so of their own volition and in their free time.

== Guidelines ==
#All are free to work on content as they please, but in the interest of not wasting ones time it is often in the best interest to discuss possible PRs before the work is done so as to gauge concerns.
# Content should be made with respect to the setting, atmosphere, balance and performance impact.
# Changelogs MUST be detailed. While this is down to your discretion as to how much or little is 'relevant' , the most pertinent details should be laid out in clear and easy to read. E.G a new gun should have its damage, penetration and accuracy detailed. By following this guideline we hope to ease the process of balancing new content without stimying its addition.
# In the same way as the above, anything more than minor content should be thoroughly Q.A tested to ensure no bugs, erroneous behaviors, runtime, et cetera are going to cause immediate issue.
# PRs should contain, if any - generalized performance impact. I.e how much performance this will take amount of loops running or active cost to maintain this feature.
# While there are bound to be PRs that are so minor as to not necessarily require testing, it is considered good practice to do so anyway. PRs should be tested to at least a basic level of completion and in the PR should have the following info; What this PR does, How I tested it, What the test result is.
# PRs with lore implications will at times be subject to A. review by creative lead or headmins, and B. Reasonable explanation as to why/how this change took place. E.G; PR A intends to balance FBPs by restricting departmental types to their respective departments, PR creator may be expected to work with lore team to provide a plausible reason for why this change has taken place.
# PR titles should be descriptive, no shit posts please.
# Non-minor/non-bugfix PRs will generally be testmerges for anywhere from five days onward before being marked ready for full inclusion. Take this time to receive feedback and make any necessary changes. Any changes to and already test merged PR need to be communicated to the person who testmerged it.
#concerns about a PR should generally be directed towards head admins for relaying to head devs/maintainers. This is per k5s preference.

Game Master

2024-11-26T02:22:56Z

K5:

Template:SidebarStaff

2024-11-26T02:02:24Z

K5:

{{Sidebar
| name=SidebarStaff

| title=Administration
| above=[[Server Policy]]

| heading1=Staff Ranks
| content1={{Sidebar | child=yes
| contentclass=hlist

| heading1=[[Server Oversight|Oversight]]
| content1=
* [[Head Administrator]]
* [[Staff Head]]
* [[Game Master]]
* [[Liaison]]

| heading2=Administration
| content2=
* [[Head Administrator]]
* [[Administrator]]
* [[Moderator]]
| heading3=Showrunning
| content3=
* [[Game Master]]
* [[Event Operator]]

| heading4=Staff
| content4=
* [[Staff Head]]
* [[Coder]]
* [[Lore Writer]]
* [[Staff Member|Staff (General)]]

}}

| heading2=Policies
| content2={{Sidebar | child=yes
| contentclass=hlist

| heading1=Oversight Policy
| content1=
* [[Headmin Domain]]
* [[Staff Head Purview]]
| heading2=Administrative Policy
| content2=
* [[Tickets]]
* [[Banning]]
* [[Appeals]]
| heading3=Showrunning Policy
| content3=
* [[Event Checklist]]
* [[Event Archetypes|Archetypes]]
| heading4=Development Policy
| content4=
* [[Contributor Guide]]
* [[Coding Standards]] [[Features|(Features)]]
* [[Lore Writing]]
| heading5=Staff Policy
| content5=
* [[Code of Conduct]]
* [[Disclosure]]
| heading6=Player Policy
| content6=
* [[Persistency]]
* [[Roleplay]]

}}

| below=This template is currently incomplete; some data is misplaced for testing purposes. Do not create pages from the redlinks.
}}<includeonly>[[Category:Staff]]</includeonly>

Template:SidebarStaff

2024-11-26T02:02:04Z

K5:

{{Sidebar
| name=SidebarStaff

| title=Administration
| above=[[Server Policy]]

| heading1=Staff Ranks
| content1={{Sidebar | child=yes
| contentclass=hlist

| heading1=[[Server Oversight|Oversight]]
| content1=
* [[Head Administrator]]
* [[Staff Head]]
* [[Game Master]]
* [[Liaison]]

| heading2=Administration
| content2=
* [[Head Administrator]]
* [[Administrator]]
* [[Moderator]]
| heading3=Showrunning
| content3=
* [[Game Master]]
* [[Event Operator]]

| heading4=Staff
| content4=
* [[Staff Head]]
* [[Coder]]
* [[Lore Writer]]
* [[Staff Member|Staff (General)]]

}}

| heading2=Policies
| content2={{Sidebar | child=yes
| contentclass=hlist

| heading1=Oversight Policy
| content1=
* [[Headmin Domain]]
* [[Staff Head Purview]]
| heading2=Administrative Policy
| content2=
* [[Tickets]]
* [[Banning]]
* [[Appeals]]
| heading3=Showrunning Policy
| content3=
* [[Event Checklist]]
* [[Event Archetypes|Archetypes]]
| heading4=Development Policy
| content4=
* [[Contributor Guide]]
* [[Coding Standards]] [[Features|(Features)]]
* [[Lore Writing]]
| heading5=Staff Policy
| content5=
* [[Code of Conduct]]
* [[Disclosure]]
| heading6=Player Policy
| content6=
* [[Persistency]]
* [[Roleplay]]

}}

| below=This template is currently incomplete; some data is misplaced for testing purposes. Do not create pages from the redlinks.
}}[[Category:Staff]]

Head Administrator

2024-11-26T02:01:34Z

K5:

{{SidebarStaff}}

Head Administrators (Headmins) are the highest rank of the administration, and the lead role within Server Oversight. Individually, they manage the policy of the administration. As a team, Head Administrators oversee the entirety of the staff team and the mandates of the Staff Heads.

== Personnel Management ==
Head Administrators are responsible for changes to staff. They're expected to vet and approve new members from the most ordinary regular staff all the way up to Oversight. It is also up to the body of Head Admins to determine and change mandates for other members of Oversight when necessary.

== Dispute Resolution ==
Head Administrators do not perform direct administrative actions involving players. Instead, their role in the administrative process has to do with task assignment and mitigating the usual concerns an administration may have.

As an example, Head Administrators may assign an administrator to an unban appeal, both to prevent the practice of Admin Shopping - coordinating an appeal such that a friendly administrator can unfairly unban - as well as avoiding unfair treatment by a hostile admin.

== Administrative Duty ==
Where Moderators dutifully uphold the letter of the rules and Administrators pursue the spirit of the rules, Head Administrators oversee the purpose of the rules, holding the server to the highest standard and shutting down any attempts at interpreting the rules in obtuse or shocking ways.

== Maintaining Rules ==
Although there are separate roles for Staff Heads dedicated to penning the rules, laws and SOP that are followed on Sojourn, Head Administrators are de facto responsible for those tasks in their absence.

Template:SidebarStaff

2024-11-26T01:13:39Z

K5:

{{Sidebar
| name=SidebarStaff

| title=Administration
| above=[[Server Policy]]

| heading1=Staff Ranks
| content1={{Sidebar | child=yes
| contentclass=hlist

| heading1=[[Server Oversight|Oversight]]
| content1=
* [[Head Administrator]]
* [[Staff Head]]
* [[Game Master]]
* [[Liaison]]

| heading2=Administration
| content2=
* [[Head Administrator]]
* [[Administrator]]
* [[Moderator]]
| heading3=Showrunning
| content3=
* [[Game Master]]
* [[Event Operator]]

| heading4=Staff
| content4=
* [[Staff Head]]
* [[Coder]]
* [[Lore Writer]]
* [[Staff Member|Staff (General)]]

}}

| heading2=Policies
| content2={{Sidebar | child=yes
| contentclass=hlist

| heading1=Oversight Policy
| content1=
* [[Headmin Domain]]
* [[Staff Head Purview]]
| heading2=Administrative Policy
| content2=
* [[Tickets]]
* [[Banning]]
* [[Appeals]]
| heading3=Showrunning Policy
| content3=
* [[Event Checklist]]
* [[Event Archetypes|Archetypes]]
| heading4=Development Policy
| content4=
* [[Contributor Guide]]
* [[Coding Standards]] [[Features|(Features)]]
* [[Lore Writing]]
| heading5=Staff Policy
| content5=
* [[Code of Conduct]]
* [[Disclosure]]
| heading6=Player Policy
| content6=
* [[Persistency]]
* [[Roleplay]]

}}

| below=This template is currently incomplete; some data is misplaced for testing purposes. Do not create pages from the redlinks.
}}

Server Oversight

2024-11-26T00:55:43Z

K5:

{{SidebarStaff}}

Server Oversight are a set of higher ranking staff roles, whose appointments are tied to a mandate. A member of Oversight without a defined mandate serves at the Head Administrators' discretion.

== Head Administrator ==
{{Main|Head Administrator}}
Head Administrators are the broadest category of oversight, whose role includes overseeing the mandates of other oversight roles. They themselves receive an appointment instead of a mandate, which may be time-limited, conditional, or circumstantial.

== Staff Head ==
{{Main|Staff Head}}
Staff Heads share the task of developing the server among themselves. Their mandates can be categorized as belonging to Code, Lore, or Rules. They are discouraged, but not forbidden, from entering the territory of another category, and are expected to do so should that category be understaffed. Within their own category, their mandates determine who has the final say over a matter.

== Game Master ==
{{Main|Game Master}}
The mandates of Game Masters regard the lore and features that they're most capable of overseeing. However, they serve more as a way to determine which GM should be handling a matter, as GMs generally should be able to pursue any event's approval in the absence of others.

== Liaison ==
{{Main|Liaison}}
The mandates of Liaison are optional, as their role grants no power except access to staff channels beyond what normal staff might see.

Rules

2024-11-26T00:50:00Z

K5:

{{GetStartedHeader}}
{{SidebarStaff}}

These are the rules for the server and ''are subject to change without notice''. For further clarification, use common sense. If you did get banned, there's probably a good reason for it, but if you disagree, you can always make an appeal on the discord. Although these are rules, but they are not infallible, complete, or concrete, and probably never will be despite our best efforts. If ''ever'' something feels wrong, either don't do it, or admin-help it first. Above all, use your common sense, listen to the game staff, and try to keep the game fun for everyone; not just yourself.

If you disagree with the rules as they currently stand, talk about it on the discord or with admins and maybe we can improve them through some healthy criticism and debate.

'''These rules are designed to be written in such a way that you can ''usually'' understand them just by reading the headers''', because reading ''all of this'' would be insanity for most people. If you cannot understand a rule just by looking at it, or wish to know about possible exceptions or examples, click the rule to learn more.

If you find yourself spending too much time reading this page, or are confused about any rules, please contact an admin on Discord to make suggestions on how these rules could be better worded.

== You must be 18 or older to play on this server ==
'''There are no exceptions.''' If the staff suspects that you are underage for any reason, you will be banned from playing on the server until you are able to prove to the satisfaction of the staff that you are at least 18 years old.

*Use of real world slurs, ‘lolspeak’, and other indications of immaturity may be taken as signs that you are underage.

*Knowing another user is underaged but not reporting it is considered grounds for an immediate, permanent ban.

*The age of consent in your country is irrelevant. Your opinion about this rule is irrelevant.

*You may also not play a character who is under 18 years of age.

== Obey the community's global rules ==
These rules apply ''everywhere'', including Discord, the server, and even private discussions with non-admins. However, not all of the global rules are even possible to break in the server, so this wiki page only covers what's relevant to the game server. The overlap from the global rules are:

* No spam.
* No OOCly illegal discussions or content (such as child porn, drugs, piracy, real world threats, etc).
* Respect other users, don't use real-world slurs, and don't intentionally drag private conflicts or in-game conflicts into public OOC (such as on the Discord server, the in-game global OOC channel, or anywhere else).
* Don't intentionally abuse server functions to upset (grief) people, or derail discussions. You know what this means, don't play stupid.
* No complaining about bans unless done properly via an appeal on our [https://sojourn13.space/forum/viewforum.php?f=13 forums] or in an ahelp or otherwise private means as an inquiry to administration staff.

== Don't be an asshole ==
It's fine to say stuff and whatnot but being a outright dick isn't alright, and there's a fine line with that. Also, spamming racist words is still not okay.

=== Do not inconvenience AFK or disconnected characters ===
Under normal circumstances, do not harm or otherwise inconvenience characters whose player is idle, ghosted, or disconnected entirely. There are some exceptions to this rule, as follows:
*Circumstance that warrant the interactions of AFK/SSD players are few and far between if there is ever a case were you are REQUIRED for to take any ID/Bag/Gear from someone that is SSD, Ahelp before hand and with your reason why. Not ahelping before may result in HARSH OOC punishment if you are found to be manipulating them while away, or causing any sort of general tampering with the player. (IE. Don't be an asshole who steals shit from afk players unless its required)
Note: If your moving someone to cryo after the time, this is ok, as long as you do not remove their items unless it's faction important and you have the means to return them properly
*If they've disconnected/idle for more than 15 minutes, you can put them in cryosleep. If you do that, take away all of their belongings except for their jumpsuit, shoes, ID, and PDA, and return everything else to its rightful department.
*If they've committed a crime, jail them as you normally would and conduct their sentence even if they aren't connected. 20 minutes in the brig is still 20 minutes in the brig.
*Emergencies bypass this rule. If it's an emergency and you need something an idle player has to fix it, you may take it. If a fire starts in a room and the AFK player is the only one who can open the door then it's an emergency. Needing to get a snack from the kitchen and robbing the chef does not count as an emergency.

=== ERP preferences must be respected ===
Players should have their ERP prefs listed in their “OOC Meta info” or “OOC Notes” on their characters. You are required to respect these preferences so long as they pertain to ERP. If you are unsure about the meaning of some of their preferences, then use LOOC to discuss it with them. If you accidentally go against someone’s preferences, or someone else goes against yours, work to correct it as quickly as possible, even if that means just deciding in LOOC amongst yourselves that ‘this didn’t happen’ and going your separate ways.

*If you do not like someone's erp preferences you won't be punished for saying so, but do not harass someone just because they like something you don't. It's far easier to simply avoid someone and causing drama will get you into trouble.

*If you are uncomfortable with an ERP theme that you hadn't thought to add (or didn't know existed) to a list of dislikes in your OOC notes, speak up in LOOC as normal. Conversely, those of you foolish enough to put 'anything goes' into your preferences, or anything else vague like this, do so at your own risk. '''You forfeit your right to complain about preference breaking''' if you do not put ''some'' indication of your dislikes into OOC preferences.

**'''Do not engage in any non-consensual scenes. If you are found to be doing non-consensual scenes even with OOC consent on server you may be banned from the community as a whole. If you have not consented to the scene - A-help IMMEDIATELY'''.
**Do not make false allegations of non-consensual scenes in game. Falsely accusing someone of rape or other non-consensual material will result in an immediate ban. This is incredibly bad faith and petty.
**'''Being found in violation of NON-CON rule(s) will be met with an automatic player kill (PK) and Perma Ban with no appeal given investigation. You've been warned as this is not tolerated here.'''

*Do not attempt to force yourself into ERP scenes where the other party (or parties) involved are not comfortable with it, or not even actually participating. This includes (but is not limited to) repeatedly trying to do ERP that a player has blatantly stated they are uncomfortable with, trying to guilt players into having a pity RP with you, etc. You get the idea. Don't do it.

*AFK/SSD/Disconnected players are not valid targets for any ERP.

=== The private areas are protected ===
The ‘dorms’ area on the map are reserved for ERP and are ‘protected’ from interruption. It is a violation of this rule to break into occupied dorms or harass players in dorms. Dorm areas are any personal apartments generally restricted to a specific person such as a head of staffs private bedroom or a dorm area claimed by a specific person, usually through a labeled door.
*The only exception is for security to arrest those who have committed crimes. Security is not allowed to indiscriminately inspect dorms for crimes, but a known criminal hiding in a dorm is not protected by this rule.
*The existence of dereliction of duty is also to be noted here, if you are working a job expected to perform a role and take time off to go to dorms you can, and likely will be interrupted via a warrant for abandoning your assigned job. For more info see rule 5.6 (You are expected to perform the job you signed up for).
*Conversely, it is not permissible to attempt to use dorms to hide from security, or to make their job of finding you harder. The dorms are for people who want to ERP in privacy. Don’t involve them in your shenanigans.

=== Do not disrupt non-public ERP scenes ===
TL;DR is you should avoid screwing with scenes that are not in public areas. The problem is, not everyone knows what is considered public or private. This is especially important for [[Security]] players to know.
*Dorms are considered private obviously. Don't mess with those under any circumstances unless someone inside actively invites you. (Calling for help is considered an invite.)
*If a person is ERPing in a public location they should be asked to vacate to a private dorm room. If they refuse they may be arrested immediately.

=== Speak English ===
We are an English server. All OOC communications are expected to be done in English. It's alright if your English is rough and imperfect, just as long as we can reasonably understand it.

*This also extends into IC communications, but is more flexible as some characters have heavy accents.
*Having a character sometime speak smatterings of other languages is acceptable, but speaking exclusively in these languages for entire sentences is not.

=== Roleplay as long as it's feasible ===
*This is an HRP (Heavy RolePlay) server. You are expected to roleplay your actions with other players as long as it's feasible. If someone engages you in purely ‘robust’ (aka game-mechanics driven) combat while you were attempting to roleplay with them, with no reasonable provocation, please use the admin-help feature to inform an admin.
**Reasonable provocation would be things that deem you too dangerous to be given even a chance to talk. For example, openly wielding a gun while threatening people, charging someone with a knife, trying to create a hazard, or being the target of a manhunt.

*If a fight does begin, you're not expected to type out every gunshot and dodge and attack. That would be absurd. Generally, you roleplay up until the point that it makes sense to start attacking, and then use game mechanics from there. You are allowed to respond to ‘robust’ violence with your own, if you desire, though you should attempt to return to roleplaying as soon as feasible. The environment is not designed for a focus on action, but rather for character-building and roleplaying. When a fight is over, resume roleplaying.

*Movement is considered a game mechanic for the purpose of this rule. Wordlessly running at a security officer who is attempting to arrest you, or wordlessly fleeing from them, is considered engaging in game-mechanic combat. The security officer has valid cause to stop trying to roleplay and stunlock you into the ground.

*Death may not be uncommon at the frontiers of space but it is still impactful. When a character dies, or your own character dies and is revived, death should be considered an immensely painful and graphic experience. One should stay in character during said experiences, statements of ‘oh well’ or mutilating a corpse for ‘fun’ would not be reasonable responses.

*'''You are to have fleshed out character records.''' These are used not only for roleplay but are to be utilized, if specified by staff, for long-term consequences for actions. Players are supported to use these as roleplay documents and treat others with these seriously. Our expectations for what should be in these can be found on [[https://sojourn13.space/wiki/Example_Paperwork#Character_Records|the Character Records page of our Example Paperwork wiki.]]

=== Do not join with an inappropriate ckey ===
Ckeys, better known as BYOND user names, must be appropriate. If any are deemed inappropriate, the ckey will be banned and you will be unable to play on our server until you make an account with an appropriate name.
*Ckeys that mock certain players or groups are an example of inappropriate.
*Ckeys that violate BYOND's terms of service may also be reported.

=== Do not misuse Global OOC ===
Many servers simply mute global OOC. We do not, because the OOC command is useful to have on in an RP heavy server.

* Global OOC is used, for instance, to contact someone you were typing a reply to had walked out of the room before you were done, and you're trying to ask them to come back. It's also useful if you're a new player, or an old player exploring new mechanics, who asks something like, "How do I make Tricord again?" or something short and similar. Short, sweet, and relevant OOC messages are generally okay. Welcoming old players returning, or new players joining, is also generally okay.

* Global OOC is ''not'' for idle banter, ranting, things pertaining to incidents in the current round (see previous rule), in-depth explanations (an explanation that takes more than a few lines), shitposting memes, or discussing topics not relating directly to the game. If you want to chatter OOCly, go to our Discord channel, which is linked from the home page or use LOOC so as to not disturb the rest of the server.

* Also, if someone does misuse OOC, do not complain in global OOC about their misusing of global OOC. Not only are you just making the problem worse, that is considered being a backseat admin, which is prohibited by other rules.

== Keep IC and OOC separate ==
*Don't complain in OOC or LOOC when your actions IC get you in trouble. If its a rules violation then Ahelp or open a ticket on the discord.
*IC (In-character) and OOC (Out-of-Character) actions and knowledge should be separated as much as possible. Don't use OOC channels to discuss what's going on IC until after the round is finished, don't use OOC knowledge to do things your character wouldn't know, such as operate medical machines when a cargo technician. You are not playing yourself in the game, you are controlling a character with their own wants and knowledge and the IC/OOC boundary is to help reflect that.
**Note that these same rules apply to LOOC as well.
*Disconnecting or using other OOC means to avoid IC consequences is against the rules. If you do urgently need to leave the server even though you're being punished, your options are either to surrender and get it over with, or use admin help to inform the admins, "I know Security is after me, but I have to go because (some emergency)." Failure to take ten seconds to tell an admin before disconnecting may result in harsher punishment.

=== Metacomms, metagaming, multi-keying, (etc) are not allowed ===
*Metacomms: Using third-party programs, such as Discord, IRC, Skype, or even the BYOND pager, to discuss and share information of the ongoing round. This excludes other players, can contribute to toxicity among the playerbase, and is often a tactic used by griefers and thus is a no-go.

*Metagaming: Using information obtained from elsewhere to influence IC decisions and actions. Your opinions or knowledge of other players or characters obtained via OOC methods should not direct your IC actions. If you have an OOC grudge against someone, you may not try to antagonize them IC, for example.
** Metagaming sometimes happens by accident due to game mechanics behaving undesirably due to intentional features or unintentional bugs and oversights. If it happens, ask an admin to help straighten things out if you can't do so among yourselves.

*Multi-keying: Logging in with multiple BYOND accounts on our game server. There is never any legitimate reason for you to do this and thus is not allowed.

= Create and play server-appropriate characters =
Although this is a furry roleplaying server based around 2D spess mans, that doesn't mean anything goes because that is possible. Suspension of disbelief is still important to a good experience, and breaking that suspension of disbelief is bad for roleplaying. Characters who break that suspension of disbelief are not allowed. Saying "it's what my character would do" isn't an automatic protection against this rule if what your character is doing breaks that immersion.

*Play a reasonably sane and mature character, give them a non-immersion breaking first and last name, do not play obvious reference characters, or characters from published works.

*Keep in mind that people do not like pain or dying and usually try to avoid it without good reason. Give your character a reasonable set of strengths, fears, and weaknesses. When writing things for IC, write things out that sound like speech, not emoticons or lolspeak.

*The setting contains no magic. Your character cannot have any superpowers, magical abilities, or anything that does not exist in the setting or cannot be reasonably replicated with game mechanics. If they are not someone who has a good reason to work on the colony, they should not be here.
**The exception to this is purely private roleplay. For example: If your character and another character are in a dorm by themselves, and the other is OOCly fine with it, your character can display potentially supernatural abilities. This is limited to that roleplay, though. You should not discuss anything about that in public. Use magic at your own risk however, because technically the moment your RP is discovered by someone else, it stops being private, putting you in potential violation of this rule.

*Obscenely oversized or undersized characters are forbidden. Minimum height is at least four feet. Maximum height is about eight feet. Anything more or less really pushes the already shaky believably of abhumans and established alien lore.

*If you are playing a lore based species such as sablekyne, mar'qua, opifex, or whatever else we add in the future, you are expected to play the race as they are canonically meant to be played.

*OOC Notes and Flavor Text are '''required'''. Your OOC notes must detail your ERP preferences, and your flavor text should not include non-physical attributes (do not include feelings your character has, or how they act). Character records are something that should be filled out, if you have an issue or don't know how to do it properly, contact a member of staff for help.

*To be a colonist your character '''must''' have at least a ''basic'' understanding of the English language. Outsiders, however, are exempt from this restriction and may be of people from various backgrounds that may not have a grasp of even basic English.

*If your character is suspended, permanently killed off, or otherwise removed from the colony as a consequence for something horrible they did in-character, you are expected to not play that character anymore. If found playing the character again, or a 'clone' to circumvent this result, OOC punishment will be issued.

* '''Do not play vibrantly colored or "sparkle dog" type characters.''' This basically means you should mainly have natural fur coloration and a relatively normal appearance. Yes, our character editor has a ton of color options, including neon colors and many design sprites to do strange things. Creativity is fun, making your appearance incredibly unrealistic or as obnoxious as possible will result in admin intervention. Some leeway is given to races with canonically vibrant colors such as cht'mants and cindarites or custom xenos but try to keep them muted instead of neon. Following the custom species guide does not make you immune from this rule. If an admin asks you to change your color, do so, we have this rule to maintain HRP.

* These following rules are taken directly from the Character Creation page[[https://sojourn13.space/wiki/Character_Creation]].
*Characters who are new to the server should shy away from head position or complicated jobs.
*Characters who have been present on the station for at least a month are safer to join head positions.
*Characters who have been present on the station for a decent period of time can work for up to 2 departments. This may be working Lonestar (Chef-Bartender-Janitor-Gardener-Artist-Cargo Tech-Miner) and Marshal (Supply Specialist-Marshal Officer-Ranger), though try to keep it believable within this sense. This may also include Science (Scientist-Roboticist) and Medical (Medical Doctor-Paramedic-Orderly), or any other variation one may think of. Blackshield counts the same as if you were working Marshals, and the Lodge does not count against your picked departments (but does count as a head role).
*Characters are only allowed to be one head role at any given time. One may not be both Science and Medical, and play both CRO and CBO. One must be chosen over the other.

== Do not kill or attack things (including yourself) for no good reason ==
*This includes yourself. Even in self-defense your goal is to fight off your attacker and survive, killing in a fight should only be done as a last-ditch effort when it's clear it's a you or them situation.

*Suicide or self-mutilation is not allowed without prior allowance by an admin. The reason for this is to maintain an atmosphere of reasonable and, at least mostly, mentally sound workers. The subject can be a poor attention grab, be used for guilt, or remove any immersion or story from someone. If you believe you have a reason, ask an admin.

*Excessive force responses are not allowed by our rules. Excessive force responses would be, for example, crushing someone’s skull for cutting you in line, stabbing someone’s eyes with a screwdriver for boredom, killing someone over a single punch, etc. Use proper reasoning for when you act in such a manner.

*Hiding player corpses as a self-antag / antag is not allowed. Staff may give an exemption in the case of an event but the body should still be possible to be found.
**Similarly, do not destroy bodies purposefully. Accidents happen regarding gibbing of a skull, destruction of someone’s body due to a bomb, etc. But whacking a target that is dead until it starts gibbing its limbs is not.
**Antags have some exemption to this; such as Blitzshells or Carrions. However admins are to specify if an antag may use these abilities or not as they can possibly end up being round-ending for a player.

*Make it clear through actions or words if you are moving into combat against someone. Even something as simple as “I’m killing you” will suffice - or even placing paper at the entrance to a cave saying ‘KEEP OUT’. Wordlessly shooting people without any clear intent or reasoning may result in administrative action depending on the context. We are a roleplay server.
**Players are, by no means, required to emote. They may choose to do so if they please. Drawing a gun when in a heated situation, such as when a gun is already drawn on them, or even being visibly armed during a fight is clear intent enough to meet this requirement. Use proper reasoning and judgment.
**If a player makes their intent known (I.e ‘get on the ground, now’, ‘give me your shit’) - you, as the person receiving said demand, are not required to say anything further. You may retaliate with force at this point if you deem fit. Sometimes ICly is preferable to try and talk, but you are not required to. Just know that actions have consequences ICly and they may apply to you depending on the legality of the order or reasoning of it.

*You are restricted from engaging in round-to-round legal action outside of the specific circumstances described in the post-hoc investigations section of the law.

**You may however, use previous conflicts as a justification for hostility with a person. This falls under self-antagging rules if you decide to pick a fight on your own. You are allowed to do so, but you must accept the consequences for such as it will not be considered legal(E.G murdering your murderer the next round may be valid if self antag rules are followed - but legally it is still murder).

**Fax-complaints about character's behavior may be faxed inter-round. These faxes should clarify when the event took place and if it is relevant to a current ongoing situation in-round. When in doubt if you can act on an inter-round issue, fax or A-help.

== Do not powergame ==
*Better known as 'playing to win'. As a security person this can be seen as going out of your way and needlessly endangering others to ‘win against’ criminals. As the Colony AI exploiting loopholes in your laws to get yourself out of them or getting the person who subverted you into trouble is another way. There is an implicit allowance for lawed characters to ERP. You may create loopholes for this reason only.

*While this shares several things in common with other rules, it still is it's own entity. Play to have fun, allow yourself to lose now and again and roll with the blows as it can make things potentially even more interesting.

*Having '''way''' too many skills for one character is another example of this. Just because you're the premier and have access to everywhere doesn't mean you should (or can) know how to do all the different jobs. (See [[Character Creation#Give them a set of skills|Character Creation]] regarding skills for more information.)

*[[Identifying Antagonists]] when you shouldn't be able to is also a violation of this rule.

== Do not godmode ==
* Often confused with powergaming, godmoding is to create abilities out of nowhere, or do impossible things. If the action cannot be reasonably emulated in the confines of the game's mechanics, and it gives you some kind of advantage or is exceptionally weird, it's probably not allowed. For example, if you don't have access to a mechanic for turning invisible, you can't turn invisible. Saying you're invisible doesn't mean squat.

* Creating a character who is immune to injuries or pain also falls under this. The game won't let you ignore getting shot, why would any player allow it either?
** If your character is literally coded to ignore pain, you can ignore pain. Cyborgs and robots are a notable example. They do not feel pain. They are not immune to injury, however.

* Accidental injuries are still in-character injuries unless an admin heals you. Admin heals are generally out of character to void the injury.

* '''Admins who are caught abusing admin powers to godmod will be immediately dealt with.'''

== Do not abuse whispers ==
Any actions that would obviously be visible should not be hidden using whispers, this includes ERP, whispers longer than a sentence, or actions that would obviously be visible to anyone glancing you way. If you need to speak something longer than a sentence but want to keep it quiet use the whisper command. Anyone caught using whispers to hide obviously visible actions of paragraphs of texts will get slapped for it.

== Rules of ‘Self-Antag’ ==
To start with, here are some of the bare bone basic rules when self-antagging.
* Your goal should be to provide fun for players in the round. Not just for yourself. Create scenarios others can enjoy and interact or involve other players who are receptive to your antics.
* Don’t Self-Antag without proper IC reasoning. Reasoning along the lines of "I'm bored" or "Giving Security something to do" is NOT a valid reason to be an asshole. Make sure your reason(s) are believable and why your actions make logical IC sense to any Admin.
* Your main goal should be to get away with something and live to fight another day. Not to aim to murder everyone in your sight.
* Don’t break machines or items when you are self-antaging, steal them instead. If the item has no worth to you nor any credit worth, don’t take it. If it does or would sell for a pretty penny, you may steal it and use or pawn it off.
** Similarly, don’t destroy or otherwise effectively grief Soteria or other faction machines that are needed for life-saving or are not replaceable. I.e - cryotubes, surgery tables, RnD machines, etc.
** This includes infrastructure, such as atmospherics, or SMES's.
* Think about how a normal person would behave under similar circumstances. A well established character who has been around awhile may be given a bit of wiggle room to keep rounds interesting.
* By Self-Antaging, you are consenting to consequences to your actions. Be it from a normal player, or any result that may come from command or security personnel.
** Do not complain about the consequences you face upon doing such actions. Being fired, brigged, or killed - depending on the severity of your actions - are all possible outcomes. If you value your character and their reputation, don’t do it.
* Permissible self-antagging does *not* include things that give you a mechanical antag status, such as Excelsior implantation. All mechanical antagging must be approved by admins via ahelp (or by using the Crusade ritual; Crusaders are mechanically antags and the ritual just pings admins asking them to give you the status).

Due to the importance of certain items or objects, to get permission to break into certain high security places or steal specific rare or strong objects requires staff permission first. These include:

* Breaking into any of the colony armories.
* The AI room or stealing the AI directly.
* Heads of Staff rooms to steal unreplaceable gear/artifacts.
* The spare ID in the Premier's office.
** The council may borrow the spare to handle activities such as issuing a new or missing ID, but are NOT to abuse it without A-helping first.

The key goal to self antagging is to create roleplay that is enjoyable or otherwise fun for players to interact with to differ from the norm. Below are a list of examples but you should always consider "are other people having fun or am I just being a dick?"

* Buying and selling contraband.
* Starting a drug production operation in a secluded spot in the colony.
* Disguising yourself as a specific department and gaining access to it while pretending to be a member of that department until someone notices.
* Extorting people for cash with a good old fashioned mugging.
* Stealing money, cutting profits, etc.

Now that the guidelines are out of the way, this rule set are examples of what self-antagonists are '''NOT''' to do without admin permission.

* Large explosives such as plasma bombs, max-caps, or any form of gas attack (such as the use of plasma fire flooding) are NOT allowed without admin permission.
** Grenades in casings and the like are, however, free to use as you see fit.
* Being a self-antag does not mean a license to murder. Doing so may result not only in perma-brig or a PK depending on your actions outcome, but staff involvement as well.
** Shooting at security while on the run for example is fully fine and acceptable rules-wise, but you are not to purposefully kill people at random.
Do not self antag more than once per day. This is generous as is, you shouldn’t be running around multiple rounds in a row breaking stuff, stealing stuff, etc. There is a fine line between a self-antagonist and a shitter.
* Do not use self-antagonism as an excuse to ruin a player's experience. This includes targeting players you know you do not like, providing purposefully no enjoyment to the situation for them, etc. It’s just dickish behavior.
* Do not start hostile actions within the first 15-30 minutes of the rounds start. You may use this as prep time, or A-help asking to start early if it’s something you feel you need to do to get the proper prep time to begin with.
** Similarly, you are to cease escalation of antagonism once a round end vote passes. Security may hunt for you, and you may retaliate in that case - but you are NOT to start self-antaging in the last 15 minutes of a round nor continue actions of self antaging.

Remember - we play on what most servers consider an “Extended round type” and pride ourselves, as a server, sith offering a persistent atmosphere where previous actions are considered ‘canon’ versus the normal SS13 experience of Groundhog Day. We do not have normal full blown antagonists, such as a murderous traitor, a serial killer, a wizard, or Steve from accounting having a bad day and deciding it’s hijack time. We are a PvE server that wishes to allow some players driven conflict and meaningful stories from said conflict.

IC consequences that occur from being caught range. The ‘permanent killing’ of your character in the case of heinous crimes, or other possibilities that players may decide within reason. It is for that reason that, by self-antaging, you are '''CONSENTING''' to these consequences for the action you have taken.

=== Outsiders & Self-Antaging ===

Outsiders hold some different rules and freedoms to self antaging than others. Outsiders may range from sane, understandable characters - to flawed individuals - to escaped convicts, cannibals, and deranged individuals. As such, their Self antaging takes different forms.

This section is a short one regarding outsiders and their self-antaging specifications. Outsiders hold different restrictions and freedoms from a colonist or lodge member deciding to self-antag. This section will outline these points below.

* Outsiders, unlike colonists, may resort to murder more quickly and for simpler reasons than a colonist. You are still not to make a target unrevivable, destroy their body, or otherwise hide the body without admin permission.
** That being said, you may do amputations of a body part or two as - say - some antagonistic type of cannibal. But do not go past this limit. Be reasonable
* Outsiders are still expected, as others, to give some form of indication of intent or use clear wording of what they want or are doing. Mugging someone? Say what you want. Telling someone to get lost? Draw your gun and tell them to get out.
** Paper notes may also be placed at, say, the entry to your house or on the door warning ‘trespassers will be shot’ as a means to make intentions clear or stake ownership of an area/building. Doing so means you may shoot violators, just as colonists do to infiltrators or trespassers.
* Outsiders may freely use traps, mines, and mobs to aid in their self-antaging. Be tasteful and do not use them on tiles, such as Z-transitions or staircases, or under trees completely. You may use them on ladders though as players can see down them before climbing.
* Breaking into the colony is acceptable to do, but you are to obey the previous rules regarding what can be stolen or broken into. Off limit areas, such as armories or the premiers spare ID requires admin permission.
* Finally, remember - colonists and hunters may kill you just as freely as you may kill them. They are required, as you are, to make their intentions clear. But you do not have the legal protection of a colonist. By playing outsider and, by any means acting strange or akin to a self antag, you lose the right to complain about the consequences that come to you.

== You are expected to perform the job you signed up for ==
When your character joins the round, you are accepting the responsibilities that the job you have chosen brings with it. Remember: if you are playing in a slot, you are likely preventing other players from performing that role. It is important that you fulfill the tasks that you have signed up for!
*Marhals should protect the colony from danger, the guild should ensure that power is up and that people can breathe, medical should provide treatment to injuries and other services, cargo should bring in needed cargo on request, Science should do... science stuff, and service should provide food. Command's job is to make sure at least these basics are being fulfilled, and to react accordingly in an emergency.

*A player must take into account the qualifications (both physical and mental) of their character’s role before placing them into it. If staff find your character to be unsatisfactory in fulfilling the requirements of the role, we may instruct you to revise your character.
**This includes majorly disabled characters — quadruple amputees, deaf, or blind characters, and so on — which are only permitted on the colony in the assistant (and associated alt-titles) job slot.

*Repeatedly failing to perform to an acceptable standard can result in a ban untill appealed.

*If you are going AFK for an extended period of time (more than 15 minutes), and are occupying a limited-number job slot (any slot other than assistant), you must remove your character from the round using a cryopod (or other similar means) to free the slot. Repeated failure to do this may result in being banned from that job.

*Do not do other people’s jobs. If you joined as medical, do not attempt to hunt down criminals. If you joined as engineering, do not attempt to perform medical treatment on your coworkers. If you are a head position, allow your staff to do work before you do the work yourself; you are a supervisor and manager first and foremost as a head position.

*Do not hijack other people's jobs. For example, if you're a roboticist but someone needs surgery, and there's already a surgeon who isn't currently busy, then don't perform the surgery instead of letting them do it. Similar examples exist with every department, so use your judgement. Basically, if you're ''actively getting in the way'' of someone else trying to do their job, you're probably breaking this rule.

*Playing jobs that can be called upon at any time to assist other crew members in emergencies waives your right to have interruption-free (E)RP sessions in private, including the dorms. If you join as a Lifeline Tech, expect to be interrupted out of private scenes. If you’re an engineer, you are expected to set up power systems and repair any large-scale damage that hampers the rest of the crew, regardless of your intent to have sex with the assistants. (Example: The premier getting their rocks off with someone while they are being called to assist with colony matters. They signed up to be the arbiter of colony matters. ERP is not what you are here for in that role. "saying you are busy or occupied")

*If you do prospecting as an non-prospector for more than 30-60 minutes without being in an expedition with them and you are not doing your job, you may get a talking to. If you want to play like a prospector - just play the job instead of ignoring the one you signed up for.

*Maintenance diving is not a valid reason to be busy from your assigned job. If you are requested to perform the actions of your role while maintenance diving it is expected that you make your way out of maintenance in a timely manner.

== You are expected to obey the chain of command (within reason) ==
*Each head of staff is the de facto leader of their department, so listen to them. Likewise, you should obey decisions from faction owners (if a fax arrives) or council decisions unless directly overridden by an admin. If you consistently do not follow reasonable orders, you will be job banned.

*If you're playing a role that has [[AI#Interpreting_Your_Laws|AI laws]], you must obey these laws first and foremost to the best of your ability.

*As any role without AI laws, you can disobey orders you think are traitorous, harmful, immoral, or violating [[Laws]]. Use your judgement and consider whether or not disobeying the order could get you in trouble or get someone else horribly killed.

*If you are given an order or AI law that may break another server rule, please alert the admins for a second opinion before continuing.

Mind you, this is '''not''' a rule that lets people be fun police as heads of staff. If you feel that someone is ordering you do things that basically require you ''not'' to do your job, or to do your job in ways that aren't important/fun, then contact an admin for a second opinion or fax a faction owner in character.

== You are expected to forget events that are deemed non-canon ==
*This is to keep things a little more sane in-round, and to allow for players with preferences in non-consensual activities to have their fun with people who share those prefs as victims. It is therefore against this rule to remember and abuse the knowledge of who killed/raped after the round has passed unless both people involved agree. You should not have the memory to antagonize or persecute your attacker without the prior OOC agreement of the other parties in the roleplay. They can include this consent in their OOC Metainfo/Notes or discuss it with you in LOOC before or after the roleplay.

*Keep in mind that non-consensual RP, while OOC, is fine it is not on an IC level. Characters who make their non-con actions public or get caught in the act can and will be permanently killed if caught. For example, if a person is tried and executed for rape that character is permanently dead and cannot reappear on the colony. If you wish to do non-con keep it private. '''You've been warned.'''

*The round ending does not make you immune to a character perma-kill. Just because you evaded capture or was not killed by the time it restarted does not mean everyone forgets what your character did. If you get caught and the evidence is ironclad enough, you will be PK'd.

*This rule also applies to events that cause catastrophic damage to the colony, such as a code red/delta scenario. As a general rule event coordinators '''should''' say before or after an event if it is non-canon or not.

*If you are killed in a round and then revived in the same round, you're memory is entirely intact and may act accordingly.

*As a general rule, player deaths in round will be considered 'soft canon'. That the character died is canon, the exact details are left vague - this is to ensure that instances of a character being gibbed, eaten by a hivemind, etc - do not either result in a forced PK, nor lore-breaks wherein said character is magically back. Players are encouraged to come up with a believable explanation as to the particular details and others are expected to not reference the original and actual events.

*In line with the above, such 'retellings' of events must be in line with server lore particularly [https://sojourn13.space/wiki/Transhumanity Transhumanity] and the The Law of Inviolability.

= The intent of the rules is more important than the letter =
The purpose of the rules is to preserve a fun and enjoyable environment for all players. If everyone is enjoying themselves even while the ‘letter’ of a rule is not being followed, it’s likely that no staff intervention will be required. On the other hand, just because something isn't in the rules doesn't mean it's okay or allowed if it's upsetting a large number of players.

*It is within admin staff's discretion to decide that certain actions violate one or more rules, even if the specific action is not listed as part of the rule. This is simply the job of the staff to interpret the rules. You can appeal decisions to other admins if you believe one has a bias against you, but doing so after a ruling is passed will get you in trouble.

*Plenty of rules are left vague enough to cover as much as possible without being too oppressing. Attempting to rules-lawyer saying that "this rule doesn't specifically say I can't do X", even if what you are doing is disrupting the server, will generally be ignored. We assume most of you have enough common sense to recognize what a [[#Create_and_play_server-appropriate_characters|sane and stable individual]] would and wouldn't do within this fictional setting.

=== Listen to admin staff ===
* One admin's word is usually as good as any other. Though, just because one admin says something is okay in that moment does not mean it will always be okay under another admin or even the same admin.
** If this causes a contradiction, you can (and should) inform the new admin of what you were told previously. For example, a Head Admin says you can do something, but that admin has left the server. A lower ranked admin shows up and asks you to stop doing that thing. You can explain that the Head Admin previously said you could do this, but if the lower ranked admin ''still'' wants you to stop, then you should stop. (This obviously works vise-versa as well.)
** Intentionally not telling a new admin about a contradiction is considered lying. It's like asking your mom for ice cream, but she says no, so you go ask dad because you think he'll be less strict.
* Sojourn is not a straight democracy; our rules and guidelines exist for a reason and we have staff dedicated to enforcing them and help set further guidelines if necessary. '''However, these rules are always going to be incomplete, and as such, just because something isn't written doesn't mean it's allowed.''' If a staff member tells you to do something, do it. They tell you to stop, then stop. If you disagree with a ruling, don't try to argue it then and there, especially if things are hectic. Once things have calmed down, or preferably after the round has ended, you can try to contact the staff member privately to discuss the ruling, or talk to another admin if you cannot talk to or cannot convince the offending admin.

* If you have a question over something unclear or questionable, never be afraid to adminhelp. The staff on hand should discuss it among themselves and give you a ruling, from there on if the ruling is in bad judgement, it's on the admin who cleared it, not ''you''. '''The staff should also NEVER ban you purely for a complaint against them.''' Even if you're a complete asshole about it, as long as the argument stays private, you cannot be banned just for arguing. Although being an asshole usually won't win an argument, so you probably shouldn't do that anyway.
** Don't confuse this for "complaining grants you immunity to bans", because that's not how it works. If you are told to not break windows and you complain how that isn't fair, you're still getting banned for breaking windows if we disagree with your complaint. What this means is we won't ban you or make an existing ban worse just because you tell us we're being excessively mean, confusing, or unfair to you or someone else.

[[Category:Guides]]
[[Category:Rules]]

Features

2024-11-26T00:49:30Z

K5:

{{SidebarStaff}}

One of Sojourn's core intents is to preserve a classic SS13 style interface. While quality of life and modernizations are always welcome, doing so at the expense of Old School features is something that will accrue scrutiny. Below are a list of features that, in some way or another, should be preserved or avoided.

= Features =
This section details an incomplete list of features that should not be removed.

* Classic Verb Interaction (Non-Hotkey Mode)

== Restricted Features ==
Restrictions on features that may be added in the future.

* Classic-style interactions and verbs should not be removed when adding aliases to them.

= Anti-Features =
These features have been expressly rejected.

* Overhead Chat in Viewport (RuneChat)
* Non-Square Maximal Viewports
* Any ERP-Specific Features
** Mechanical ERP
** Vore
** "Anti-Ghost" features

== Scrutinized Features ==
These features don't strictly go against these principles, but will likely lead to a request for justification.

* Viewport sizes other than 15x15.

Contributor Guide

2024-11-26T00:48:53Z

K5:

{{SidebarStaff}}

==<center>Contribution guidelines</center>==
<hr>
<center>'''Hardline rules'''</center><hr>
* PRs may be put forth are not necessarily supported by their creator. They may be made on behalf of others or even just on a notion. All are free to make Pull Requests for consideration and ultimate responsibility for the inclusion(or exclusion) on content falls squarely on the head of the Lead-Dev. No coder should be shouted at solely for a change they've requested. 
*Players and admins shall not dictate to devs or contributors how they 'must' spend their time coding. While changes will invariably become necessary for any number of reasons(story arcs, balance, etc) these changes should either be requested, or directly given to the lead-dev to determine implementation. At the end of the day, all developers who work on this project do so of their own volition and in their free time. <hr>

==== <center>Guidelines</center> ====
#All are free to work on content as they please, but in the interest of not wasting ones time it is often in the best interest to discuss possible PRs before the work is done so as to gauge concerns.
# Content should be made with respect to the setting, atmosphere, balance and performance impact.
# Changelogs MUST be detailed. While this is down to your discretion as to how much or little is 'relevant' , the most pertinent details should be laid out in clear and easy to read. E.G a new gun should have its damage, penetration and accuracy detailed. By following this guideline we hope to ease the process of balancing new content without stimying its addition.
# In the same way as the above, anything more than minor content should be thoroughly Q.A tested to ensure no bugs, erroneous behaviors, runtime, et cetera are going to cause immediate issue.
# PRs should contain, if any - generalized performance impact. I.e how much performance this will take amount of loops running or active cost to maintain this feature.
# While there are bound to be PRs that are so minor as to not necessarily require testing, it is considered good practice to do so anyway. PRs should be tested to at least a basic level of completion and in the PR should have the following info; What this PR does, How I tested it, What the test result is.
# PRs with lore implications will at times be subject to A. review by creative lead or headmins, and B. Reasonable explanation as to why/how this change took place. E.G; PR A intends to balance FBPs by restricting departmental types to their respective departments, PR creator may be expected to work with lore team to provide a plausible reason for why this change has taken place.
# PR titles should be descriptive, no shit posts please.
# Non-minor/non-bugfix PRs will generally be testmerges for anywhere from five days onward before being marked ready for full inclusion. Take this time to receive feedback and make any necessary changes. Any changes to and already test merged PR need to be communicated to the person who testmerged it.
#concerns about a PR should generally be directed towards head admins for relaying to head devs/maintainers. This is per k5s preference.

Template:SidebarStaff

2024-11-26T00:48:31Z

K5:

{{Sidebar
| name=SidebarStaff

| title=Administration
| above=[[Server Policy]]

| heading1=Staff Ranks
| content1={{Sidebar | child=yes
| contentclass=hlist

| heading1=[[Server Oversight|Oversight]]
| content1=
* [[Head Administrator]]
* [[Staff Head]]
* [[Game Master]]
* [[Liaison]]

| heading2=Administration
| content2=
* [[Head Administrator]]
* [[Administrator]]
* [[Moderator]]
| heading3=Showrunning
| content3=
* [[Game Master]]
* [[Event Operator]]

| heading4=Staff
| content4=
* [[Staff Head]]
* [[Coder]]
* [[Lore Writer]]
* [[Staff Member|Staff (General)]]

}}

| heading2=Policies
| content2={{Sidebar | child=yes
| contentclass=hlist

| heading1=Oversight Policy
| content1=
* [[Headmin Domain]]
* [[Staff Head Purview]]
| heading2=Administrative Policy
| content2=
* [[Tickets]]
* [[Banning]]
* [[Appeals]]
| heading3=Showrunning Policy
| content3=
* [[Event Checklist]]
* [[Event Archetypes|Archetypes]]
| heading4=Development Policy
| content4=
* [[Contributor Guide]]
* [[Coding Standards]] [[Features|(Features)]]
* [[Lore Writing]]
| heading5=Staff Policy
| content5=
* [[Code of Conduct]]
* [[Disclosure]]

}}

| below=This template is currently incomplete; some data is misplaced for testing purposes. Do not create pages from the redlinks.
}}

Server Oversight

2024-11-25T23:58:48Z

K5: /* Staff Head */

{{SidebarStaff}}

Server Oversight are a set of higher ranking staff roles, whose appointments are tied to a mandate.

== Head Administrator ==
{{Main|Head Administrator}}
Head Administrators are the broadest category of oversight, whose role includes overseeing the mandates of other oversight roles. They themselves receive an appointment instead of a mandate, which may be time-limited, conditional, or circumstantial.

== Staff Head ==
{{Main|Staff Head}}
Staff Heads share the task of developing the server among themselves. Their mandates can be categorized as belonging to Code, Lore, or Rules. They are discouraged, but not forbidden, from entering the territory of another category, and are expected to do so should that category be understaffed. Within their own category, their mandates determine who has the final say over a matter.

== Game Master ==
{{Main|Game Master}}
The mandates of Game Masters regard the lore and features that they're most capable of overseeing. However, they serve more as a way to determine which GM should be handling a matter, as GMs generally should be able to pursue any event's approval in the absence of others.

== Liaison ==
{{Main|Liaison}}
The mandates of Liaison are optional, as their role grants no power except access to staff channels beyond what normal staff might see.

Template:SOP

2024-11-24T20:31:52Z

K5:

{{Sidebar
| name = SOP

| title = [[Standard Operating Procedure]]

| heading1 = General
| content1class = plainlist
| content1 =
* [[Standard Operating Procedure (Command)|Command]]
* [[Standard Operating Procedure (General)|General]]
* [[Standard Operating Procedure (Legal)|Legal]]
| heading2 = Departmental
| content2class = plainlist
| content2 =
* [[Standard Operating Procedure (Marshals)|Marshals]]
* [[Standard Operating Procedure (Blackshield)|Blackshield]]
* [[Standard Operating Procedure (Prospectors)|Prospectors]]
* [[Standard Operating Procedure (Soteria Medical)|Medical]]
* [[Standard Operating Procedure (Soteria Research)|Research]]
* [[Standard Operating Procedure (Guild)|Guild]]
* [[Standard Operating Procedure (Lonestar & Service)|Lonestar]]
* [[Standard Operating Procedure (Church)|Church]]
}}<includeonly>[[Category:Standard Operating Procedure]]</includeonly>

Standard Operating Procedure

2024-11-24T20:25:51Z

K5: Reverted edit by LillyTrilby (talk) to last revision by K5

{{SOP}}

== Standard Operating Procedure - Master List ==
The information contained in the article below is written here instead of the individual [[Jobs|manuals]] for each profession because this is all information the entire crew should know, so they may know what to expect, what their rights are, and what other staff should be doing to best service the crew. For those looking for information on the Hunting Lodge, click [[The Hunters Codex|this]].

(( Players reading this page should keep in mind '''THESE ARE NOT OOC RULES!''' These are just how the colony, in-character, would have something handled. Whether or not you are following these policies is irrelevant if you break [[Rules|the actual rules]]. Breaking SOP is usually IC, and usually only results in IC punishment like being fired. ))

=== Departmental Standard Operating Procedures ===
Along with the guidelines listed below, each and every department has it's own subset of job-specific Standard Operating Procedure that is to be adhered to whenever possible. '''General Standard Operating Procedures include colonist rights and legal limitations of where these rights generally end.'''

[[Category:Guides for New Players]]
[[Category:Lore]]
{{Guides}}

Module:Documentation/config

2024-11-20T03:02:58Z

K5:

p = {}

Module:Documentation/config

2024-11-20T03:02:19Z

K5:

t = {}