This is a public handbook and may be distributed freely.
MR Guidelines
As a member of the MR team, you are expected to act as a role model for the LR team. Below is a general foundation of guidelines you are expected to follow. Please keep in mind that this list may be updated at any time.
- Don’t be biased - Treat all members of StarByte the same way.
- Be professional - You are expected to act in a professional matter at all times at StarByte, regardless of if you are currently working or not.
- Grammar - Spelling, punctuation, and grammar is required at all times in the Training Center and is necessary at all times in StarByte to be eligible for a promotion.
As well as the above general rules, you are expected to follow all staff and public guidelines at StarByte.
Consequences will be imposed upon you if you cannot follow our guidelines. StarByte is dedicated to have dependable staff members, so it is imperative that we uphold all staff guidelines strictly. MR rules follow a general Warning → Demotion → Termination → Rank Ban policy for most rule violations. Members ranked Director Intern and above are authorized to give consequences to any member of the MR team who has broken a rule.
Activity Requirements
Each rank in the MR team has a maximum capacity of 15 members. As such, it is imperative that all members be active. At StarByte, there are 2 separate activity requirements; minimum and recommended. Minimum activity is activity that all members must uphold to remain in their rank. If you fail to meet those requirements, you will be demoted. Recommended activity is activity that is recommended for all staff members to meet. If you fail to meet it, you will not be eligible for a promotion.
All members of the MR team must meet the following Minimum Activity Guidelines:
- 25 minutes per week in-game
- 1 training session attended per month
All members of the MR team are recommended to meet the following Recommended Activity Guidelines:
- 45 minutes per week in-game
- 2 training sessions attended per month
- Consistent activity
- Consistent spelling, punctuation, and grammar
Please be advised that if you are consistently meeting your minimum activity guidelines but fail to meet your recommended ones, you may be demoted in favor of other better suited and more active members. You will be given 1-month advance notice if you are at risk of being demoted for bare minimum activity, and you must have been doing the bare minimum for 2 or more months.
If you fail to meet your minimum activity guidelines, you’ll be given one warning and then demoted the next quota period. You will not be given any other advance notice. Activity warnings expire after being promoted.
Those on an activity leave are exempt from all activity guidelines and are given a 1-week grace period after it ends in which they are only required to do half of their activity guidelines. For example, if you were to go on a 2-week activity notice, you would not be required to have any activity in StarByte. Once 2 weeks have passed, the next week you would be required to be in game for 12 minutes and be recommended to be in game for 20 minutes. Session requirements will still be enforced.
Inactivity Notices
Members of the MR team are granted inactivity notices for up to 4 weeks (28 days) up to twice every 3 months. They should only be used for instances where you cannot meet your activity requirements, such as a family vacation or temporarily not having enough time.
Purposely using an activity notice twice every 3 months when not required is unacceptable and will result in a demotion.
To create an inactivity notice, please create a general ticket in the communications server. Additionally, create a general ticket if you wish to end your inactivity notice early. Don’t end your inactivity notice early if you have less than 3 days remaining.
Extensions are granted for an extra week upon request, however extensions longer than that use an extra inactivity notice.
Joining StarByte or claiming sessions before your inactivity notice is up without ending it early is unacceptable. If you are caught doing so, your inactivity notice will immediately end without a grace period, and you will be given a staff warning.
If you are caught lying about any matters of your inactivity notice, you’ll immediately be terminated for first offenses and issued a rank ban if it happens again.
If you require an inactivity notice longer than 4 weeks, contact a member of the Executive Team directly. You can be granted an inactivity notice of up to 8 weeks in genuine cases where you won’t be able to be active at StarByte for extended periods of time. In cases where you require an activity notice longer than 8 weeks, please create a general ticket and ask to resign. You’ll be ranked Lead Technician instead of customer and will be eligible to be promoted back to Staff Assistant after 12 weeks.
Unclaiming Registers
Members of the MR team and above are given a tool that they can use to unclaim staff members’ registers if required. To start, look in your inventory. You should have a tool that says “Unclaim Register”. Equip it, then click on a register.
You’ll notice a blue highlight appear for a second letting you know the register has been unclaimed and then disappear shortly after.
The register has been unclaimed, and anyone can now claim it. After this, the player who previously owned the register will be respawned to clear the register UI if they had it open.
The unclaim register tool should only be used in cases where the staff member operating it refuses to unclaim it themselves. You should always request them to unclaim it first before doing so yourself.
After unclaiming someone’s register, you should give them an official staff warning if it’s their first offense and demote them if it’s not. Continue supervising after you’ve handled the situation.
Please be aware that each time you use the unclaim tool on a register, it is logged in the communications server regardless of if anyone’s claimed it or not. Yes, the tool works on all registers and no you should not be “testing it out”. Misuse of the tool is considered admin abuse and will result in a rank ban.
Issuing Consequences to LRs
LRs must be given a consequence if you have to unclaim their register, warn, kick, or ban them.
Before giving a consequence, always prepare one of the following messages:
You’ve been issued an official staff warning for [reason].
You’ve been issued an official demotion to [rank] for [reason].
You’ve been terminated from the staff team for [reason].
If the staff member is being demoted or terminated, run the :demote or :terminate command on them.
Walk outside of StarByte away from spawn to somewhere you won’t attract attention.
Unclaim their register if they have one claimed, then run the :res command on them. Bring them using the :bring command, then paste the applicable message. Allow for 10 seconds to pass, then run the :ban [user] [reason] command on them.
Immediately forcefield yourself and log the punishment in the communications server.
In a case where an LR has done something that requires a pban or a rank ban, run the :ban command on them and request the punishment in the communications server.
StarByte Admin Commands
At StarByte, we use a modification of Basic Admin Essentials named StarByte Admin Utilities, or SAU for short. When you join the game, you’ll automatically be given admin commands based on your rank. Admin commands are used for ranking and moderation. Below is a list of commands you as an MR have access to.
= Allowed
= Restricted - Use with caution
= Prohibited - Only with permission from an HR+
| Command | Usage | Description | Clearance |
|---|---|---|---|
| :respawn/:res | :res [player] | Respawns a player. | |
| :kick | :kick [player] [reason] | Kicks a player from the game with specified reason. | |
| :ban | :ban [player [reason] | Bans a player from the game for 3 days with specified reason. | |
| :cmds | Shows the available commands. | |
|
| :admins | Shows all admins of the server. | |
|
| :ingameadmins | Shows all admins in the server. | |
|
| :chatlogs | Shows all chats in the server, public or private. | |
|
| :pm | :pm [user] [message] | Privately send a player a notification with a specified message with the option to reply. | - If a player requests it, if it is required to remain confidential, or if you wish to privately remind someone. |
| :to | :to [player] | Teleports yourself to a specified player. | |
| :tp | :tp [player 1] [player 2] | Teleports a specified player to another. | |
| :bring | :bring [player] | Teleports a specified player to yourself. | |
| :info | :info [player] | Shows a specified player’s info. | - If you suspect a player of being an alt or need to check their rank |
| :joinlogs | Shows everybody who has joined the server. | - If you suspect someone of evading a punishment |
|
| :view | :view [player] | Spectates a player. | - Should not be used in place of regular MR duties. |
| :unview | Unspectates a player. | |
|
| :ref/:refresh | :ref [player] | Respawns a player and teleports them back to their previous location. | - When updating a player’s rank after a promotion. |
| :ff | :ff [player] | Forcefields a player. | - On yourself if you are going to be AFK for 1-5 minutes. Periods of time above require leaving. |
| :unff | :unff [player] | Unforcefields a player. | - On yourself. |
| :uniform | :uniform [player] | Puts a StarByte uniform on a player. | - On yourself or on another person with permission from an HR+. |
| Ranking Commands | |||
| :promote | :promote [player] | Moves a player’s rank up one. | - After a promotion request was approved. |
| :demote | :demote [player] | Moves a player’s rank down one. | - After a punishment request was approved. |
| :terminate | :terminate [player] | Moves a player’s rank to customer. | - After a punishment request was approved. |
| :setrank | :setrank [player] [rank number] | Sets a player’s rank to the specified number. | |
Claiming Shifts and Training Sessions
Sessions and shifts are a major part of your career at StarByte. While shifts are not necessarily a part of your requirements, sessions are. Both are to be claimed in the communications server in the #claiming channel of the MR team category.
At 10 PM EST every Thursday and Sunday, the channel opens. The first one to claim a session with the following format gets it.
Time and Date:
Role: [host or co-host]
Members of the HR team and above do not have to claim sessions, as they are automatically roled Spectator in trainings. If you are interested in being a trainer in a training, you do not have to claim it either. Trainings open at xx:40 and being selected for trainer is a first come-first serve basis.
If you consistently claim sessions and fail to attend them without notice, you will be issued a staff warning and a strike if continued.
Promoting LRs
A major part of your career at StarByte is noticing and promoting LRs. To start, look out for any Technician you see following the rules and being professional. Request their promotion in the communications server via the appropriate channel. Once it is approved, check if they are still in-game. If not, use the bot in the communications server to set their rank to the next one. Otherwise, perform the following steps:
Run the :promote [player] command in-game. Wait 30 seconds.
If they have a register claimed, use the unclaim tool on it. Walk outside of StarByte to a place where you won’t attract attention. Run the :res [player] command on them and bring them. Paste the following message:
Congratulations on being promoted to Lead Technician! As an LT, you now have access to the Repair Shop as well as certain admin commands. Feel free to rejoin!
Afterwards, brief them on their new admin commands as well as answer questions if they have any. Return to your normal MR duties afterwards.
Support Calls
Via the register UI, LRs can call support by pressing the support button. All MRs and above will receive a notification at the top of their screen with the caller’s name and an option to teleport. Once someone teleports, the support call will disappear for everyone. If you teleport to someone, be prepared to ask the LR how you can assist them and handle their concerns as efficiently as possible.
Abuse of the support call feature should be treated as admin abuse, and if caught :ban them immediately and request their rank ban in the server.
Thank you for reading our handbook. If you have any questions, please open a ticket in our communications server.
ZlacticaStudios
Chairman
Executive Team