SOSA Policies

Read our rules and other policies before playing!
User avatar
iiKaqrix
Site Admin
Articles: 0
Posts: 1818
Joined: Wed Nov 06, 2019 9:23 pm
Location: United Kingdom

Policy AC: Unbanned Members

Post by iiKaqrix »

POLICY AC: UNBANNED MEMBERS
ARTICLE §1

If a member is unbanned from the SOSA Network they shall NOT receive any Department Roles (excluding civilian - as long they weren't previously command) upon joining back. However, you will be able to reobtain your VIP roles. Anyone that joins back wishing to reobtain their VIP roles are to first make a ticket requesting for the roles to be given back, as of which a BOD member of PR member will confirm this and have the roles be given to you through our ticket system.

Definitions: • Roles - TeamSpeak and Discord roles that define your position in said Department and permissions in-game.
Image
Corporal Ken Sasaki
Commanding Officer — Recruitment & Training
[email protected]

User avatar
Ellis Green
Articles: 0
Posts: 29
Joined: Wed Oct 23, 2019 4:16 pm

Policy AD: Jailing & Admin Jailing

Post by Ellis Green »

POLICY AD: JAILING & ADMIN JAILING
ARTICLE §1

Both Admin Jails and Regular Jails issued to players in-game are to have a maximum sentencing of 60 minutes. Admin Jails are carried out by Executives solely for the purpose of removing someone swiftly from the area that is deliberately interrupting a scene. Regular Jails are carried out and issued by Law Enforcement Officers and are to max out at 60 minutes, no longer. Members of SAHP are to still refer to the Penal Code yet must be maxing out their jail times for players at 60 minutes regardless of whether the jail times stated stack a top of on another and go over.

If the player goes over the 60-minute jail sentence based on what offences have stacked, the player must still be sentenced for 60 minutes. As well as, Law Enforcement aren't permitted to re-jail that person once there initial jail sentence has expired based on the additional offences that they had done that would otherwise be typically added on.

Ben Gepard
Articles: 0
Posts: 1444
Joined: Sat Nov 09, 2019 2:02 am
Contact:

Policy AE: Leaking Discords

Post by Ben Gepard »

POLICY AE: LEAKING DISCORDS
ARTICLE §1

Leaking paid, or locked assets destroys community relations, and demotivates the people that create content from releasing it. At no time will SOSA endorse, or support this practice. If a member is found to be in a leaking Discord, they will be ticketed and asked for the purpose. They are liable to be warned, or banned depending on their involvement.

User avatar
Ellis Green
Articles: 0
Posts: 29
Joined: Wed Oct 23, 2019 4:16 pm

Policy AF: Leave of Absence [LOA]

Post by Ellis Green »

POLICY AF: LEAVE OF ABSENCE [LOA]
ARTICLE §1

A leave of absence, otherwise abbreviated as an LOA, is a system that allows department members, executives, and development team members to take a break away from the server for a select amount of time.

ARTICLE §2

  • All LOA start and end dates are to be checked first to ensure that they are official and finalized In order to prevent unnecessary changes to your LOA dates. In the circumstance that you start and end dates need to be changed, you're to Immediately create a ticket and request for the dates to be altered.
  • In the event that you require an extension onto your current LOA, you're to Immediately create a ticket and request for an extension, as well as confirmation on how long you want the extension to be. Any prolonged extensions are to first be authorized by department high command before being approved.
  • Between the time that you begin and end your LOA, any and all department hours/work that is logged In-between those dates will not be valid and accounted for. Department High Command and Department Staff that are responsible In overseeing logged hours for their department will be held accountable for this and are never to promote or award you based off of these hours.
  • LOA's that exceed a month are to be first authorized and approved upon by the respective high command members for the department(s) that the Individual is in.


ARTICLE §3

Department Staff, Sub-Division Leaders and Department High Command are held at a higher accountability to ensure a departments consistency and fluency at all times. Because of that, In the event that said roles were to go on an LOA for a prolonged period of time, we automatically reserve the right to remove that person from their role for the purpose of the departments consistency. The SOSA Community Directorate reserve the right to remove department high commands in the circumstance that they're to suddenly go on a prolonged LOA. Department High Command within SOSA also reserve the right to remove department staff and sub-division leaders if this were also the case.

User avatar
Ellis Green
Articles: 0
Posts: 29
Joined: Wed Oct 23, 2019 4:16 pm

Policy AG: Department Name Changes

Post by Ellis Green »

POLICY AG: DEPARTMENT NAME CHANGES
ARTICLE §1
  • Official name changes for department members are to be requested first through a ticket. This can be done by doing .newticket in #bot-commands.
  • Between each official name change, there is a two month cooldown.
  • All official name changes are to be first approved off first by each department high command that the member is a part off. If a department was to reject the name change, then the request will be denied.

Post Reply