# Kronos Admin Guide

## Table of contents
{: .no_toc .text-delta }

1. TOC
{:toc}

Kronos is RoSCO's administrative system and anti-exploit, custom developed by FirXD and Pixel Softworks. Kronos takes the form of a Discord bot, Roblox module, and a private administrative web panel. Those with Kronos permissions can utilize these to perform their duties.

### Commands
{: .text-red-300 }
#### 1A - Permission Levels
{: .text-grey-dk-000 }
{: .no_toc }
All members who are ranked Floor Supervisor+ will gain access to various commands. Ranks and their respective admin levels are shown below. 

| Rank        | Admin Level         | 
|:-------------|:------------------|
| Floor Supervisor           | Moderator | 
| Floor Manager           | Moderator | 
| Assistant Manager | Moderator   | 
| Store Manager           | Moderator     | 
| Assistant Director          | Administrator | 
| Store Director          | Administrator | 
| Board of Directors           | Administrator | 
| Senior Board of Directors         | Administrator | 
| Intern Administrator           | Super Admin | 
| Junior Administrator           | Super Admin | 
| Senior Administrator          | Super Admin | 
| Head Administrator           | Super Admin | 
| Executive Director           | Super Admin | 
| Store Developer          | Moderator | 
| Group Owner           | Creator | 

Depending on the role, certain commands can be executed. For example, users with Moderator commands **cannot** run :pban. However, players with Super Admin may.

#### 1B - Executing Commands
{: .text-grey-dk-000 }
{: .no_toc }
When executing commands, ensure they are being utilized correctly. 

* Kronos provides the ability to hide commands by typing "/e" in front of them.
  * To run a command privately with the "/e" method, open up the chat to run a command per usual. After doing so, place a "/e" before the desired command.
    * EX:  **_/e :m Hello!_**
  * This will make the command private. This also makes the command hidden from the chat.
* The console can also be used to carry out a command. 
  * To use the console, press ";" or "'" on your keyboard. This will prompt a GUI to appear at the top of your screen. When using the console, the prefix is **not** required. 
    * EX: ; (Console Opens) 
      
      **_exploitlogs_**

      (Exploit logs GUI is then shown as expected) 
      
### Anti-Exploit
{: .text-red-300 }
As mentioned at the start of this document, Kronos features a built-in anti-exploit system called Hyperion, which keeps out exploiters. The anti-exploit system automatically permanently bans or kicks depending on the severity. 

* All detected exploits can be viewed with the :exploitlogs command. Please do not stay under the impression that :exploitlogs will show exploiters who are currently in the server and show what they are doing. The system cannot detect everything and only logs when an exploiter is automatically banned.
* If a player appears in :exploitlogs, there is no need to request in-game assistance, as the exploiter has more than likely been banned by the Hyperion anti-exploit. If an exploiter is present, contact an available HR, attempt to gather sufficient evidence, and open a ticket.

### Downtime
{: .text-red-300 }
Downtime is a time in which a critical error has occurred within the code, stopping all commands being run, and by extension, your admin being given.

Click [here](https://status.firxd.me) to view the status of various Kronos services.

* In this scenario, the Head Administrators+ kindly request that players do not spam ping us, DM us repeatedly, or anything of the sort when this occurs. Doing so can lead to consequences. FirXD and Pixel Softworks have likely been informed of the problems and are working diligently to fix them. 
* A simple fix may just be rejoining. If a server shuts down, many players rejoining at the same time can overload the system and may cause admin loading to be delayed. For this reason, we request that players wait a few minutes before rejoining.

### Acceptable Usage
{: .text-red-300 }
This is the main section of the document. It will outline the acceptable and unacceptable usages of admin commands.

All major admin abuse (running :pban all, etc.) is logged and will result in an instant punishment! The command will be immediately canceled, and SHRs will be notified.

#### 4A - All Commands Usage
{: .text-grey-dk-000 }
{: .no_toc }

When executing commands, be sure to type at least 50% of the player's username.

| Command Name | Description |
|:-------------|:------------|
| :respawn / :res / :refresh / :ref | Use this command to respawn yourself and anybody who may request it. You may NOT do :respawn all or respawn users who do not request a respawn. |
| :kick (Assistant Director+) | Use this command to update in-game ranks, kick failed or passed LRs at a training session, or for any other valid reason. |
| :ban (Assistant Director+) | Use this command for trollers, rule violators, removing a blacklisted or permanently banned user, or for  other valid reason. |
| :unban (Assistant Director+) | Use this command if an HR accidentally bans the wrong person or if an invalid ban reason was put. | 
| :pban (Junior Administrator+) | Use this command to permanently ban players (valid reasons are on the Punishment Guide). | 
| :sm / :m  / :fm (Junior Administrator+) | Use this command to make announcements in the store or at training sessions. | 
| :shutdown (Junior Administrator+ & the host of a training) | Use this command to conclude a training session after everyone is finished. SHRs may use this command if several players are banned from a server as a result of an admin abuse attack, for development updates, or if a server is lagging and nonfunctional. This command may not be used without valid reasoning. |
| :slock / unslock (Host of a training session) | Use this command to lock a training session at :00. This command should not be used to unlock a server during a training session. |
| :tp / :bring (Assistant Director+) | Use this command if a player is stuck somewhere and needs to be freed. |
| :to | Use this command to be teleported to another player, as well as for other valid reasons. |
| :view / :unview | Use this command to watch suspicious players (example: exploiters). Do not use this command to stalk SHRs or view shift hosts. | 
| :ff / :unff | Use this command for LRs who pass a training session and need to be taken to the ranking line. | 
| :fly (Junior Administrator+) | SHRs should use this command to supervise the store or a training session. | 

| Acceptable Commands       |
|:-------------|
| _:cmds_ |
| _:bans_           |
| _:info_         |
| _:pm (Junior Administrator+)_           |
| _:admins_           |
| _:chatlogs_           |
| _:logs_           |
| _:exploitlogs_           | 
| _:showtools_ | 

| Unacceptable Commands       |
|:-------------|
| :crash |
| :h |

### Conclusion
You have reached the end of the Admin Guide! Staff members should thoroughly read all the information in this guide before using admin commands. Direct any questions to an SHR. Keep in mind that the list of acceptable commands MAY change at any time, and not everything is listed. It's up to you to use proper judgement to determine weather using a command is correct.