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:
- 15 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:
- 30 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.
Failing to meet the quota 1 time will result in a staff strike. Failing to meet it again will result in a demotion to Lead Technician. Strikes expire after 90 days; demotions do not expire. Activity strikes and demotions are counted towards your overall active infractions. So, if you are given an activity strike and go on later to commit an offense worthy of a strike, you will instead be demoted. If you already have an active strike and would have been given an inactivity strike, you would instead be demoted to Lead Technician. Inactivity terminations in cases of already having a demotion on your record also count towards your record. If you already were terminated in the past and an inactivity termination would be your 2nd one, it will instead result in a rank ban.
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 10 minutes and be recommended to be in game for 15 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 termination.
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 do either of those things while on an active inactivity notice, you will be demoted to Lead Technician and issued a rank ban if it happens again.
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.
If you are unclaiming a register as a result of refusal to follow direct instructions, they are to be terminated alongside that. Please follow the “Issuing Consequences to Staff” section for more information. If you are unclaiming a register as a result of leaving their station without unclaiming it or for any other reason, you should issue a staff warning.
Please be aware that each usage of the unclaim tool is logged. Abuse of this tool is strictly forbidden and falls under admin abuse, an offense punishable by a rank ban. There is no need to “test” the tool.
Issuing Consequences to Staff
StarByte runs under a strict punishment guide:
Staff Warning
A reminder issued to staff upon breaking a minor rule once. Each staff member is allowed to have 1 staff warning on their record at once. To assign one, go to their account via Hyra’s search feature. Then, go to the logbook tab. Use the “Warning” template. Log it as a warning, and have it expire after 14 Days.
A staff strike issued to staff upon breaking a minor rule after receiving a warning or breaking a more serious rule. Each staff member is allowed to have 1 staff strike on their record at once. To assign one, go to their account via Hyra’s search feature. Then, go to the logbook tab. Use the "Strike " template. Log it as a warning, and have it expire after 90 Days. As a reminder, you must get an HR’s permission to hand out a staff strike.
Demotion
A demotion issued to staff upon breaking a rule after receiving a strike or breaking a serious rule. Each staff member is allowed to have 1 demotion on their record at once. To assign one, go to their account via Hyra’s search feature. Then, go to the logbook tab. Use the “Demotion” template. As an MR, you are not permitted to demote LRs. They should instead be terminated. If you are an HR demoting an MR, log it as a demotion to Lead Technician. Follow the HR guide for issuing consequences to MRs from there.
A termination issued to staff upon breaking a rule after receiving a demotion or breaking a very serious rule. Each staff member is allowed to have 1 termination on their record at once. To assign one, go to their account via Hyra’s search feature. Then, go to the logbook tab. Use the “Termination” template. Log it as a termination. Ensure the target rank is to “StarByte Customer”. As a reminder, you must get an HR’s permission to hand out a termination.
Rank Ban
A rank ban issued to staff upon being terminated twice or breaking an extremely serious rule. To assign one, go to the group page. Go to the “Members” tab in the group settings. Search their name. Click the 3 dots to the top right of their name, then click “Ban User”. This will ban them from the group, effectively prohibiting them from enjoying group exclusive benefits and holding a rank within StarByte. If the user has already left the group, they need to be permanently banned from the game. Contact a member of the Executive Team to manually ban them from StarByte games. Only HRs may Rank Ban.
To issue a warning or a strike, follow these steps:
- Unclaim their register. Teleport to them. In a respectful and professional manner, tell them they are being warned or striked and for what reason. Let them know the punishment for breaking the rules again.
- Immediately
:ffyourself and log the punishment using Hyra.
To issue a demotion or termination, follow these steps:
:ffyourself and log the punishment using Hyra.:banthe user with the reason for their demotion as the ban message. Do not say “Demoted.” or some variant as the ban reason.
To issue a rank ban, follow these steps:
:ffyourself and log the punishment using Hyra. Log it as a termination and add somewhere that it is a rank ban.- Go to the Members page in the Roblox group settings, then find their username and ban them.
:banthe user with the reason for their demotion as the ban message. Do not say “Demoted.” or some variant as the ban reason.
Punishment Guide
The following is a short list of offenses with set punishments. You are required to follow this punishment guide. Taking an action against an offense that is not on the punishment guide will result in at minimum a staff strike, with the possibility for it to be considered Admin Abuse, punishable by a rank ban.
- Trolling
- Standing on counters
- Standing in avatars
- Caps abuse
- Disrespect towards community members
- Register hopping
- Excessively large avatars
- Disrespect towards staff members
- Bypassing
- Minor threats
- Ro-banging
- Lying to an HR+
- Disrespect towards HR+ members
- Major threats
- Exploiting
- Abusing glitches
- MR+ Evasion (Leaving to avoid a ban)
- Impersonation
- Using alternate accounts
- Other violations of Roblox TOS
All bans are automatically done with the usage of Roblox’s Ban API which utilizes alt detection. In the event of leaving to avoid a punishment that would otherwise result in a ban, a prompt Ban API request is necessary to ensure the permanent ban by an Executive Team member done manually. Leaving to avoid a punishment for any other offense is punishable by a 3 day ban applied by the Executive Team manually.
Staff Only Punishment Guide
- Failure to greet customers
- Unprofessionalism
- Giving false information to a customer
- Leaving your register unattended
- Failing to supervise (MR+)
- Lack of grammar in the training center (MR+)
- Falsely claiming a session/shift (MR+)
- False logbook entries (MR+)
- False session logs (MR+)
- Claiming a session via the Discord and failing to attend it without a valid reason/prior notice (MR+)
- Breaking session hosting limits
- Inactivity
- Breaking in-game rules under the “Verbal Warning → Kick…” section
- Failure to adhere to the punishment guide (MR+)
- Incorrectly promoting/disciplining staff (MR+)
- Incorrect usage of commands at the training center (MR+)
- Deliberate lies to customers
- Minor leaking of confidential information (MR+)
- Breaking in-game rules under the “Kick → Ban…” section
- Minute farming (MR+)
- Failure to moderate (MR+)
- Biasness
- Breaking in-game rules under the “Ban → Permanent Ban…” section
- Insubordination
- Malicious/Deceptive inactivity notices (MR+)
- False announcements (MR+)
- Playing with the ranking sticks (MR+)
- Malicious/Deceptive logbook entries/session logs (MR+)
- 2 terminations
- Admin Abuse
- Free-ranking (MR+)
- Corruption
- Miscellaneous malicious/deceptive practices
- Breaking in-game rules under the “Permanent Ban” section
- Major/Mass Admin Abuse
- Continuing to break rules after a successful rank ban appeal
- Account lending
Members of the Leadership Team and above reserve the right to give alternative consequences to any offenses listed above, and are not restricted to the punishment guide.
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
| 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. | |
|
| :ulogs | Shows all logs of register actions and tool transfers in the server. | |
|
| :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+. |
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.
Every day at exactly 1 hour before the session you wish to claim starts, you may send a message in the claiming channel. If you are the first one to send the claim, you will get it.
Claims will be marked invalid if:
- They are not sent at exactly 1 hour before the session
- They are edited
- They are missing information
- They are not made using the appropriate format
- The claimer is not eligible to host the session
- A co-host/ranker is sent after the session was claimed
- Answering “ZlacticaStudios” to the first grammatical exercise question in the MR applications will make you eligible for an HR rank if you specify while applying for the “Management Team” rank.
Promoting LRs
As an MR, you are eligible to promote up to 3 LRs at shifts who have surpassed your expectations.
The minimum requirements for promoting someone is:
- Demonstrating proper spelling, punctuation, and grammar (Less than THREE grammatical errors)
- Refraining from following the host of the shift
- Professionalism and a willingness to help customers
- Be a Technician
If you believe someone has met those expectations, follow the ranking guide from there.
Additionally, those of the Administration Team and above may promote users outside of shifts. The requirements remain the same, and you are still required to follow the ranking guide.
Administration Team members are allowed to promote 2 people a day outside of shifts. Staff Assistants - Management Team members are allowed to recommend people for promotions if they are following the promotion requirements outside of shifts. To do so, visit this link and enter their username and reason. AT+ members are not eligible to make promotion recommendations due to them already being eligible to promote outside of shifts. SA - MT members may only recommend 2 promotions a day to be courteous to others and allow other MRs to have chances to promote. Promotion recommendations expire after 7 days.
Ranking
Only those of the Management Team are eligible to rank other Staff Members. Staff Assistants and Supervising Team members who rank others will be considered Admin Abusers and will be punished as such. Hosts, Co-Hosts, and Spectators at trainings are given a ranking stick used to promote LRs who have completed their training. Hosts and Co-Hosts must be Management Team+ to Host or Co-Host for that reason.
Additionally, ranking as part of promotions or demotions is also a Management Team privilege.
To demote or promote a user, follow these steps:
- In the MR or HR bot commands channel on the Discord server, run the /setrank command on their username. Please note that ranking is performed through numerical responses only, so type 1 instead of “StarByte Customer”.
- Go to the Hyra Staff Page (Hyra)
- Push CTRL + K or go to the Search space in the top left
- Enter their username
- Go to the “Logbook” tab
- Select the appropriate template
- Submit!
If you are demoting a user, follow the steps outlined in “Issuing Consequences to Staff”. If you are promoting a user, follow these steps:
- Come up to their register
- Say, “Congratulations! You have been promoted to [Rank].”
- If they are becoming a Technician, tell them they are now able to work in the Repair Shop and tell them how to operate the Repair Shop registers
- If they are becoming a Lead Technician, tell them they will be receiving new admin commands and how they can rank up from there
- Tell them to rejoin to claim their rank
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