Admin Guide
AVIQ and Kronos are Avenue's administrative and Anti Exploit systems, custom developed by PostedDevOfficial. AVIQ takes the form of a Discord bot, Roblox module, and administrative web panel. Those with AVIQ permissions can utilize these to perform their duties.
Commands
Permission Levels
All members who are ranked Assistant Manager+ will gain access to various commands. Ranks and their respective admin levels are shown below.
| Rank | Admin Level |
|---|---|
| Assistant Manager | Moderator |
| Department Manager | Moderator |
| Store Executive | Admin |
| Store Director | Admin |
| Junior Administrator | Super Admin |
| Head Administrator | Super Admin |
| Administrative Director | Super Admin |
| Group Developer | Super Admin |
| Board of Directors | Super Admin |
| Vice Chairperson | Creator |
| Lead Chairman | Creator |
Depending on the role, you will only be able to perform certain commands. For example, users with Moderator commands cannot run ;pban, but users with Super Admin commands can.
Executing Commands
When executing commands, you must take care to ensure you are doing it correctly.
- AVIQ allows you to run a command by typing "/e" in front of a command.
- To run a command privately with the "/e" method, you need to first open up the chat to run a command like you usually would. Before running the command, however, you need to type "/e."
- EX: /e :m Hello!
- This will make the command private, and hidden from the chat.
- To run a command privately with the "/e" method, you need to first open up the chat to run a command like you usually would. Before running the command, however, you need to type "/e."
- You may also use the console to carry out a command.
- To use the console, you need to first press ";" or "'" on your keyboard. This will cause a GUI to appear at the top of your screen. When using the console, the prefix is not required. A button is provided for mobile players.
Anti-Exploit
As mentioned at the start of this document, AVIQ features a built-in Anti-Exploit system called Kronos, which keeps out exploiters, and automatically bans/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 you are hosting a shift, and you notice that an exploiter gets banned, please do not call for an SHR unless they can rejoin. It may take up to 30 seconds for them to be kicked again, as the HTTP API needs to be re-synced!
Downtime
Downtime, also known to many as "THE ADMIN ISNT WORKING!!!!!1!!!" 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.
Visit the status page to view the status of various AVIQ services.
- In this scenario, the Head Administrators+ kindly request that you do not spam ping us, DM us repeatedly, or anything of the sort when this occurs. Doing so is punishable and could get you possibly demoted.
- A simple fix may be rejoining. If a server shuts down, many people rejoining exactly at the same time can overload the system and may cause your admin loading to be delayed. For this reason, we request that you wait a few minutes before rejoining.
Acceptable Usage
This section outlines everything that you can and cannot do with your commands. All major admin abuse is logged and will result in an instant punishment!
Arguments = What you need to supply to run the command
Allowed = What you may use this command for
Not Allowed = What you may not use this command for
Punishment = What happens if you use it inappropriately
Logs All Attempts = Whether doing this logs
Available Commands
| Command | Arguments | Allowed | Not Allowed | Punishment | Logged |
|---|---|---|---|---|---|
| :respawn / :res / :refresh / :ref | A player | Yourself and willing players | :respawn all or unwilling users | Warning to permanent ban | No |
| :kick | Player, reason | 3+ warnings or valid reason | 3 or less warnings, invalid reason | Blacklist to permanent ban | Yes |
| :ban | Player, reason | Valid reason (see Punishment Guide) | Invalid reason | Warning to permanent ban | Yes |
| :unban | Player, reason | Valid reason | Invalid reason | Warning to permanent ban | No |
| :pban | Player, reason | Valid reason | Invalid reason | Warning to permanent ban | Yes |
| :sm / :m | Message | Important announcements | Unimportant messages | Warning to permanent ban | No |
| :tp / :bring | Player(s) | Freeing stuck players | Other reasons | Warning/demotion | Yes |
| :ff / :unff | Player | Training use only | Other reasons | Warning | Yes |
| :view / :unview | Player | Watching suspicious players | Stalking SHRs | Warning | Yes |
Conclusion
Please ensure that you read all the information thoroughly before you use your commands. If you have any questions, contact PostedDevOfficial.