Kronos Admin Guide
Table of contents
- 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
1A - Permission Levels
All members who are ranked Floor Supervisor+ will gain access to various commands. Ranks and their respective admin levels are shown below.
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
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.
- 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.
- 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)
-
- 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.
Anti-Exploit
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
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 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
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
When executing commands, be sure to type at least 50% of the player's username.
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.
