77th JSOC / Public Servers / Rules

From 77th JSOC - Wiki
Jump to navigation Jump to search

Previous

Rules

List of rules

  • Do not disobey admins or HQ (an admin’s word is final).
  • Follow the Chain of Command: Admins → HQ → Pilots/UAV → Squad Leaders.
  • Only HQ can allow vehicle usage (vehicles stay at the base until permission is granted by HQ)
  • Verbal abuse and bullying will not be tolerated.
  • Respect other players. (If you are having issues with another player, contact an admin. If you have a complaint, create a ticket on the 77th JSOC Discord).
  • Intentional team-killing will not be tolerated.
  • Griefing and obstructive play will not be tolerated.
  • Hacking and mission exploitation will not be tolerated.
  • Excessive mic spamming, especially of Side and Global channels, will not be tolerated.
  • No lone wolfing (Players must operate within a squad)
  • HQ, pilots and UAV need to be on Teamspeak (microphone not required for pilots and UAV).
  • When there is no HQ, pilots/UAV are to sort out the squads.
  • CAP/CAS/UAV/Artillery/Armor are not to take down any targets unless called in by squad leaders. Calling in support
  • Recruitment & advertising is not allowed on our platforms.
  • An infantry squad consists of a bare minimum of 6 players and a maximum of 11 players.
  • An armor crew must fill all the vehicle crew slots.
  • No TS-only squads, if a squad has a teammate not on TS the squad is not allowed to exclude him.
  • All server elements need to have appropriate callsigns, Squad names are allowed to be only within the Phonetic Alphabet. Alpha, Bravo, Charlie and etc.
  • Unnecessary destruction of BLUFOR vehicles will not be tolerated.
  • Side channel voice is reserved for admins and HQ only.
  • Firing a weapon at the base -- unless at an enemy -- Is not permitted.

back to top

Rule clarifications:


The rule clarifications are not an all-encompassing explanation of the rules and how they are applied, they are guidelines to help players understand how the rules work but are not limited to these examples only.

In the end, it's up to the current admin online to judge what and how a rule applies to a specific event.

In the end, the Admin applying the rules needs to use their judgment on the matter presented. The admin present has the final say in any issues and they will apply any resolution as they see fit.

If a player believes a situation is not clear or that they are being mistreated they are welcome to go on TeamSpeak and talk to a PR member, and/or create a ticket on our Discord. Any ticket raised on our Discord will be processed by a member independent of the issue/situation who will provide a non-biased response.

Never argue with an admin on the server, follow the admins guidelines on the server and seek clarification on TS or on Discord.


Rules and reasoning:


Do not disobey admins or HQ (an admin’s word is final):

Admins are present to uphold server standards and ensure that the 77th JSOC vision for the servers is maintained. An admin’s word is final on the server. Therefore, if told to do something by an admin, do not prolong the issue by arguing. Do as you have been told by the admin.

If you feel that the situation could have been handled differently, you are welcome to talk to the admin in question on Teamspeak. Alternatively, you may speak with a member of the public relations team (PR member) or create a ticket on our Discord.

The HQ is the highest-ranking public player on the server, their job is to facilitate a good server flow and uphold server standards. Follow their directions as long as they are within the server rules.

back to top


Follow the Chain of Command: Admins → HQ → Pilots/UAV → Squad Leaders:

The chain of command is the cornerstone of the 77th JSOC servers, we rely heavily on the command structure to run our servers and it is of utmost importance that it is adhered to at all times. The chain of command is in place for all players to know who they need to follow and listen to. A higher person in the chain reserves the right to guide any player lower down in the chain of command.

Admins:
The highest-ranking person(s) on the server are Admins, what they say is what goes.

Headquarters (HQ):
After the admins, Headquarters (HQ) is the highest-ranked player on the server. The HQ decides how the server will operate within the rules and guidelines dictated to them by the 77th JSOC and its admins (HQ Handbook).

Pilots/UAV:
When the HQ is present Pilots/UAV fulfill a supportive role. Additionally, in HQ’s absence, they will fulfil his administrative duties. A pilot is the commander of the aircraft they are flying. Pilots always have the final say inside their helicopter.

Squad Leaders (SL):
Squad Leaders lead their squads during combat operations while communicating with the command structure to ensure the smooth operation of the server and its squads. They are the direct superior of their squad members leading their squad within the guidelines and rules set by the 77th JSOC.

back to top


Only HQ can allow vehicle usage (vehicles stay at the base until permission is granted by HQ):

HQ is the only public player allowed to permit the use of vehicles, with the exclusion of the regularly spawning assets for UAV/Pilots, this includes any vehicles that spawn at base/are found in the field or are bought by HQ through the reward system. For a detailed list of vehicles affected please check the HQ Handbook subsection about the reward system.

Only an active HQ can grant the use of the above-mentioned vehicles, the server needs to be in good working order for HQ to be allowed to deploy any vehicles.

If there is no HQ on the server, all vehicles affected by this rule need to stay at the base or RTB. If an HQ signs off before a vehicle squad gets to the AO they must return back to base or stay at base and stand down until another HQ comes online.

A degree of lenience can be given to ground assets deployed and already at the AO if an HQ signs off. The asset may stay deployed for the duration of the AO and will have to RTB as soon as the AO is over. This exception is not a given and can at any time be revoked if a pilot/UAV or admin deems it necessary.

back to top


Verbal abuse and bullying will not be tolerated / Respect other players:

Harmful, threatening, abusive, defamatory, slanderous, hateful, racially, or ethnically offensive language directed at a player in text or over VON is not tolerated and may lead to an admin intervening.
If you are having issues with another player, talk to an admin and provide evidence. The admin will support you in any way he sees fit for the situation.

Remember, if any of this behavior is presented towards you, do not reciprocate, this may only get you into problems too. Always keep calm and collected.

Keep in mind, that we are a multinational community, and differences in culture may cause misunderstandings and conflicts. Always keep in mind that people from different countries may view behaviors and manners differently, extra caution may be advised so you won't come across in an unsatisfactory way in the eyes of others.

back to top


Intentional team-killing will not be tolerated:

Any form of intentional team killing is not tolerated on the 77th JSOC servers.

No exceptions.

There are systems in place on the server for bug fixing. Therefore, there is no reason for team killing in a “bug fixing” situation.

Anyone teamkilling may be subject to reprimands.

back to top


Griefing and obstructive play will not be tolerated:

A player who is deliberately trying to annoy others and make anyone else's game experience on our servers less enjoyable is regarded as Griefing others.
Trolling behaviour falls under the same rules as Griefing.

Anyone found to hinder other players' ability to play on the server within the boundaries of the rules and guidelines established by the 77th JSOC will be regarded as obstructing others' gameplay.

back to top


Hacking and mission exploitation will not be tolerated:

Any form of hacking/scripting/exploitation will not be tolerated.

Any mission file exploits/bug exploits giving players or teams advantages not intended by the server developers will be regarded as unlawful and are all subject to reprimands.

back to top


Excessive mic spamming, especially of Side and Global channels, will not be tolerated:

Mic spamming is not tolerated on any channel, this includes side and global channels but is not exclusive to those channels.
Any player abusing the VON system in any VON channel on the 77th-JSOC servers may be reprimanded.

Excessive mic spamming includes but is not limited to, making sounds predominantly used to annoy or disturb others.
It is not limited to only using the mic, anyone using a soundboard or other devices to broadcast soundbites, different sounds or music may be reprimanded for excessive mic spamming.

back to top


No lone wolfing (players must be in a squad):

To promote squad-based gameplay, all infantry players are required to be part of a squad when playing on our servers.
Any player deploying to the AO without a squad will be regarded as a lonewolf (This includes the UAV operator).

Players joining a squad only to leave the squad to go alone or to form a squad below minimum squad size when reaching the AO will be regarded as a lonewolf.

Players need to work with their squad and listen to their squad leader. A player straying away from their squad and refusing to follow their squad leader’s orders will be regarded as a lonewolf.

Players need to stay in a combat-effective squad and within a relative distance to give each other support. Players straying away from their squad’s supportive range will be regarded as a lonewolf.

SLs can not overrule server rules, an SL can not order a squad member to move outside of the squad's effective support range, and players moving outside the effective support range of a squad will be regarded as a lonewolf.

Pilots may not be part of an infantry squad and are the only players allowed to leave base by themselves to perform their role as transport/CAP/CAS pilots.

HQ/UAV may not be part of a squad and will be regarded as lonewolfing if they leave the main base.

back to top


HQ, pilots and UAV need to be on Teamspeak (microphone not required for pilots and UAV):

Players in HQ/Pilot/UAV slots must be in the correct TeamSpeak channel for the server they are on.
This means the HQ/Pilot/UAV channel for EU1, EU2 or EU3 respectively.
They may not have their speakers muted for an extended period of time and must be able to hear the communications in the TS channel.

The players in these roles are required to have the exact same name in-game and on TS to guarantee that admins can see if they are in the correct TS channel or not.
Players failing to use the same name in-game and on TS may be removed from the server slot by an admin.

Only HQ is required to have a mic to ease communications on TS and the server. Pilots and UAVs are required to be able to hear TS and communicate proficiently via text in-game.

back to top


When there is no HQ, pilots/UAV are to sort out the squads:

When no HQ is online the duties and responsibilities of HQ fall on the pilots/UAV, the pilots/UAV will have to follow the same set of guidelines that normally regulates HQ and his actions.
To this end, it is a good practice for all pilots/UAV to read and understand the Pilot handbook about pilots third function as well as the HQ Handbook.
Pilots/UAV will have to perform all tasks placed on HQ in their absence with the exception of granting the use of vehicles, this function is reserved for HQ only.

back to top


CAP/CAS/UAV/Artillery/Armor are not to take down any targets unless called in by squad leaders:

The ROE for support assets is to be followed at all times, for clarifications for specific support elements please refer to the handbook for applicable support assets (Role Guides).

Mortars are regarded as an artillery asset on our servers and must follow the same ROE as artillery.
This means that they can only engage targets with mortars when being called in by a squad leader not part of the squad carrying/using the mortars.

A fire mission/support request needs to follow a specific format and contain certain information to be a valid mission.
For clarifications on the format for a valid fire mission/support mission please read section 5.2.4 calling in support of the SL handbook.
If the support request does not follow the guidelines set in the SL handbook it should be regarded as an invalid request and disregarded.

back to top


Recruitment & advertising is not allowed on our platforms:

The 77th JSOC regard all our outlets/servers and services as our platforms and do not allow any kind of advertising and/or recruitment on them for any other similar outlets/servers/platforms or services.

Any type of attempt to advertise and/or recruit players from/on any of the 77th-JSOC platforms will see the offender removed.
If a player is found to be recruiting/advertising for a unit/group the player and all the members of the unit/group involved may be removed from all our platforms.

back to top


An infantry squad consists of a bare minimum of 6 players and a maximum of 11 players:

To promote squad-based gameplay and guarantee a minimum manpower requirement for a combat-effective squad the minimum squad size will always have to be 6. To prevent a squad size too large to be handled by the squad leader a maximum squad size is set to 11. All squads deploying to the AO need to be within these set limits, if they exceed limitations they are not allowed to deploy to the AO.

An exception to squad size is only to be made when the server population does not support the minimum squad size, in these circumstances a squad below the minimum size can be deployed with the clause that they will be reinforced up to the minimum squad size with any new player connecting.

HQ/UAV may not be part of a squad.

back to top


An armor crew must fill all the vehicle crew slots:

Armour assets must have all their crew slots filled. No more, no less. This means that an armor crew generally consists of 3 members with a few exceptions for the AWCs(Nyx), they only fit 2.

Each armor asset used will be regarded as its own entity and needs to be its own squad with only the vehicle crew members for the specific asset in it.

back to top


No TS-only squads, if a squad has a teammate not on TS the squad is not allowed to exclude him:

No one is allowed to be excluded from any squad or support asset due to the lack of TeamSpeak, the only TS-required slots are HQ/Pilot/UAV.
If a squad or support asset has a squad member not on TS they must utilize the in-game text and VON system for communications so as to not exclude the player without TS.
This rule is not exclusive to Teamspeak, any third-party communications software outside the game is applicable to this rule.

back to top


All server elements need to have an appropriate callsign, Squad names are allowed to be only within the Phonetic Alphabet:

All server elements need to have appropriate callsigns for their function, any inappropriate callsigns will be changed.
The callsigns must reflect the function of the element and not come across as offensive or irrelevant.

Examples of HQ would be: HQ, Crossroad, CentCom

Examples of pilots would be: Pilot 1, Pilot 2, Vortex, Hawk, Raptor, Transport

Examples of UAV would be: UAV, Hawk

An armor unit should use an appropriate callsign for its function, any inappropriate callsign will be changed.
Examples of Armour would be: Hammer, Kilo (Armour), Rhino, etc.

All infantry-based squads must use a name out of the NATO phonetic alphabet.
They are not allowed to have any additions to their names. They should purely be the phonetic name, nothing more, nothing less.
Squad leaders must start with a vacant name already available on the squad signs at the base since this will guarantee an available lineup point for the squad.
If all squad names at the base are taken a squad leader may continue to choose from the NATO phonetic alphabet not included on the base signs.

back to top


Unnecessary destruction of BLUFOR vehicles will not be tolerated:

No BLUFOR vehicles are to be destroyed unnecessarily.
This includes destroying the vehicle for a chance to receive another type or to destroy vehicles that are damaged but recoverable.
This rule applies to all vehicles, for transport helicopters, there may be some exceptions.
For a detailed procedure when dealing with helicopters, see the Pilot handbook subsection: 4.2.1 Damaged helicopter.

back to top


Side channel voice is reserved for admins and HQ only:

The side channel VON system may only be used by an acting HQ or an Admin, anyone abusing the side channel VON will be removed from the server.

back to top


Firing a weapon at the base -- unless at an enemy -- Is not permitted:

It is not permitted to fire any type of weapon at the base, place or detonate any kind of charges at the base.
The only vehicles permitted to fire in the base are the static AA and Artillery, these units are only allowed to be used by HQ/UAV/Pilots for base defense purposes/fire support.


back to top