Access Request Management

ARM SOP An Introduction to ARM

ARM is at best described as the vibe check branch of staff on nova.

Responsibilities are Lax for most of the time but if the applications are picking up you are expected to handle them whenever free.

Handling applications

Select your ticket. First In First Out. Start with a warm or neutral greeting.

Gathering. Gather the players CKEY | Birthday in mm/yyyy | Discord user ID.

Server bot. Use the server bot at #access-bot-channel. There you use three commands /player (CKEY here) This will tell you of any information they will have on the server. If available skip to step 7

/lookup (Ckey here) This will pull records from the Centcom Ban DB to allow reference to the players with past bans from other servers opted into the Ban DB if available. See here

/User (Discord ID here) This is to check discord user creation and time on Novacord.

Checklist. With all primary points of information gathered. You want to make sure they’re all valid like a checklist as described below.

ARM Application checklist

Ckey age - Needs to be longer than 2 weeks Player DoB - Needs to be 18+ and consistent with past applications if any /User - Discord age anything past 2 weeks /Lookup - No recent bans younger than 3 months /Player or Returning - If record is present check #Player-Approvals/Rejections and pinned messages for Skyrat applications and skip to Step 7, otherwise go to step 2 Prompts - Check step 6 Codewords - Codewords are at #community-rules and Wiki policy Rule 11 Special request applications - Ping relevant Head (Eg. github / charprefs) Banned player application - /Notes Ckey in #Admin-bot-channel

Ticking off boxes on this checklist. Firstly if anything is amiss you will need to question the player on the relevant topic. There you can debate with others or yourself on whether this player is a good fit for the server. Like Papers Please you need to clear discrepancies and get a proper picture of the players personality.

Reading prompts. This is your primary tool as someone whose checking if the player applying is a good fit for the server. You will have three primary points to check.

Was the sentence constructed with a clear proficiency in english? Did they put effort into the sentences? (Eg. Emotes, character interactions, Longer than 1 sentence) Did they answer according to the expectation of the prompt?

Checking Previous ARM records. While checking on players you will see that they put into their application that they are a “Returning player” or the /player command will show that they have a Ckey record on Nova Sector. When this happens you need to check #Player-Approvals/Rejections and pinned messages for their Skyrat/Nova applications.

Accepting applications. If the checklist is complete and you have nothing else to add or question. Proceed to #Player-approvals. Start with the Discord ID then copy-paste the application under that. Lastly, add any additional notes and end with a line break (```---```).

Rejecting applications. If the player just doesn’t fill the checklist, fails the vibe check or simply just doesn’t reply. The base denial time is 2 weeks. Following the same format as approvals. Special denial reason lengths are listed below.

Ckey under 2 weeks old: Deny till age reaches 2 weeks or check page 4 Belligerent attitude in ticket: 1 month Refusal to age check after report: Denied till age check Recent Ban from another server: Vouch from MRP server with stable 30 players (Case by Case basis) No reply in application longer than 2 days: Reapply anytime

Finalizing an accepted application. The final step! Back to the #Access-Bot-channel. When the approval is filled out and you’ve given the player the green light. You need to use this command !tgs whitelist Ckey. The moment that the command is entered, the player will have exactly 1 week to join the in game server and see the menu.

Special cases. For the confused. For required age checks ping @ignari If they have a record on server but do not have a application check #Refugee-Recovery-Plan. If that fails ping @Senior-Access-Request-Manager.