Horizon Security Team
Welcome to the HLST handbook. Here are the rules and reminders you must follow! This will be updated, we will notify you however it is your job to review all changes
Updates
Last Updated: 4.2.23
Main Rules
A - Game Rules,
B - Group Rules,
C - Misc
1A - You must be On-Duty to patrol/have hlst items
2A - Breaking game rules is forbidden, security members are held to higher standards
3A - Exploiting and glitching is forbidden while on-duty
4A - You must be On-Duty to patrol/have hlst items
5A - Respect all players, especially higher ranked members
6A - On duty Resistance members may be killed on sight
7A - You must warn players before killing them
8A - Spawn killing, or killing in any spawn location is not allowed
9A - You may not, under any circumstances destroy horizon property (destroying core, breaking things, etc)
9A - You may not restrict players from using game items, unless it interferes with the core
1B - Do not spam the group wall
2B - Bragging about your rank is forbidden
3B - Abusing group permissions is highly frowned upon
1C - Toxicity/Toxic behavior is not allowed anywhere
2C - Be helpful to new players/members
3C - No claiming to be a higher rank
Information
Going on/off duty
A member is considered on-duty when they have an official uniform and ranktag on. While on duty, you must abide by all rules stated here.
Packages/layered clothing are allowed, but they must not obstruct the uniform, unless you have a uniform bypass. Tshirts are also not allowed if they obstruct the uniform. They must be small badges that do not cover more than 25% of the uniform
Spawn killing/warnings
You may not spawn kill whatsoever, unless the user is an exploiter. Before you can kill someone, you must warn them, saying that their behavior is going against the objective. If they continue, warn again, after that you may kill them.
If a user has been warned for the same thing before, you do not have to warn them. If there is reason to believe the user does not have chat, you may communicate using the clipboard
Keeping facilities safe
The primary objective of HLST is to keep all of the facilities safe. This is accomplished by keeping any core stable, and killing any resistance members
Ranks
Note: Tools are kept between ranks
(I.E, a Cadet still has the Recruit stun stick)
Recruit (DEFAULT) [LR]
Recruit is the default rank, given to all members
Trained Recruit [LR]
This is the second rank. Shows that you are ready and want to continue
Requirements: 20 points
Cadet [MR]
This is the third rank. This is the first one that gives new tools, and is also the first MR rank
Requirements: 50 points + Cadet Eval
Tools: Baton
Trained Cadet [MR]
This is the 4th rank. Here, users are held to a higher regard
Requirements: 100 points + Trained Cadet Eval
Permissions: Allowed to request deductions
Tools: Stun gun, amour
Elite Cadet [MR]
This is the 5th rank. Most players will stop here, the best of the best. This is the last MR rank, and the first hosting rank
Requirements: 200 points + Elite Cadet eval + Practice assist
Permissions: Allowed to give Kos, Can host assists
Tools: Rifle, Sentry gun, area shield
Weapons Officer [HR]
The first HR rank, and the only one to be obtainable with points
Requirements: 350 points + Weapons Eval + Trainer Nomination + Practice response
Permissions: Level 1 mod in the HLST game servers, add/deduct points, host responses
Tools: Sword, shotgun, level 2 sentry
Field Commander [HR]
The second HR rank, you need to be nominated by 3 trainers, or appointed by Clay
Requirements: Nomination from 3 trainers + practice patrol
Permissions: Level 2 mod in the HLST game servers, request demotions/ranklocks, moderation powers in the community guild, host patrols
Tools: Gravity field
Trainer [HR]
The final rank. Trainers do it all, and keep the group afloat
Requirements: Get appointed by Clay herself
Permissions: Admin in the HLST game servers, Admin powers in the community guild, demote and ranklock users, host trainings
Bot [MISC]
A misc role, used for the NOVA bot
This is a work in progress
Its not fully finished, and is being worked on.
Please check back for updates