77th JSOC / Public Servers / Rules: Difference between revisions

From 77th JSOC - Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<div class="tableOfContents">__TOC__</div>
<div class="tableOfContents">__NOTOC__</div>
[http://www.77th-jsoc.com/wiki1/77th_JSOC Previous]<br>
[http://www.77th-jsoc.com/wiki1/77th_JSOC Previous]<br>
<h1 class="guidelines">Rules</h1>
<h1 class="guidelines">Rules</h1>
<h2 class="guidelines">List of rules</h2>
<h2 class="guidelines">List of rules</h2>
<ul class="rules">
<ul class="rules">
     <li>Do not disobey admins or HQ (an admin’s word is final).</li>
     <li>1. Do not disobey Admins or HQ (an Admin’s word is final).</li>
     <li>Follow the Chain of Command: Admins → HQ → Pilots → Squad Leaders.</li>
     <li>2. Follow the Chain of Command: PR Members → Admins → HQ → Pilots/UAV → Squad Leaders.</li>
     <li>Only HQ can allow vehicle usage (vehicles stay at the base until permission is granted by HQ)</li>
     <li>3. Bullying and verbal or written abuse will not be tolerated on any of our platforms.</li>
    <li>Verbal abuse and bullying will not be tolerated.</li>
     <li>4. Respect other players. If you are having issues with another player, contact an Admin.</li>
     <li>Respect other players. (If you are having issues with another player, contact an admin. If you have a complaint, post it on the 77th JSOC [https://77th-jsoc.com/forum/viewforum.php?f=29 forum]).</li>
    <li>5. Intentional teamkilling is not allowed under any circumstances.</li>
     <li>Intentional team-killing will not be tolerated.</li>
     <li>6. Hacking and mission exploitation will not be tolerated.</li>
     <li>Griefing and obstructive play will not be tolerated.</li>
     <li>7. Griefing and obstructive behaviour will not be tolerated on any of our platforms.</li>
     <li>Hacking and mission exploitation will not be tolerated.</li>
     <li>8. Excessive microphone spamming will not be tolerated on any of our platforms.</li>
     <li>Excessive mic spamming, especially of Side and Global channels, will not be tolerated.</li>
     <li>9. Recruitment and advertising are not permitted on any of our platforms.</li>
     <li>No lone wolfing (Players must operate within a squad)</li>
     <li>10. Players must operate within a squad.</li>
     <li>HQ, pilots and UAV need to be on Teamspeak (microphone not required for pilots and UAV).</li>
     <li>11. An infantry squad must consist of a minimum of 6 players and a maximum of 11 players.</li>
     <li>When there is no HQ, pilots are to sort out the squads.</li>
     <li>12. A squad is not allowed to exclude any player without a valid reason.</li>
     <li>CAP/CAS/UAV/Artillery/Armor are not to take down any targets unless called in by squad leaders. [http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Guides_/_SL_/_Squad_Leader_Handbook#Calling_in_support: Calling in support]</li>
     <li>13. HQ, Pilots, and UAV operators must be on TeamSpeak and able to hear. HQ must have a working microphone.</li>
     <li>Recruitment & advertising is not allowed on our platforms.</li>
     <li>14. When there is no HQ, squad assignment becomes the responsibility of the Pilots and UAV operators.</li>
     <li>An infantry squad consists of a bare minimum of 6 players and a maximum of 11 players.</li>
     <li>15. Firing any weapon at the base is not permitted.</li>
     <li>An armor crew must fill all the vehicle crew slots.</li>
     <li>16. Support Assets may only engage direct threats when called in by an Infantry Squad Leader close to an Objective, except in cases of self-defense.</li>
     <li>No TS-only squads, if a squad has a teammate not on TS the squad is not allowed to exclude him.</li>
     <li>17. Only an active HQ may authorise the use of Reward Assets.</li>
     <li>All server elements need to have appropriate callsigns, Squad names are allowed to be only within the Phonetic Alphabet. Alpha, Bravo, Charlie and etc.</li>
     <li>18. An Armour crew must occupy all vehicle crew positions, use appropriate roles, and operate exclusively as a Support Asset.</li>
     <li>Unnecessary destruction of BLUFOR vehicles will not be tolerated.</li>
     <li>19. Deliberate or unnecessary destruction of BLUFOR assets is prohibited.</li>
     <li>Side channel voice is reserved for admins and HQ only.</li>
     <li>20. All server elements must select an appropriate callsign from the available drop-down menu.</li>
     <li>Firing a weapon at the base -- unless at an enemy -- Is not permitted.</li>
     <li>21. Play Your Role.</li>
   
</ul>
</ul>
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]


<h1 class="guidelines">Rule clarifications:</h1>
<h1 class="guidelines">Rule clarifications</h1>




<p class="guidelines">
<p class="guidelines">The following clarifications are not intended to be a comprehensive explanation of the rules or how they are applied. They are provided as guidelines to help players better understand the rules, but are not limited to the examples listed.</p>
    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.
<p class="guidelines">If a player believes a situation is unclear or feels they have been treated unfairly, they are encouraged to speak with a member of the Public Relations (PR) team on TeamSpeak and/or create a ticket on our [https://discord.gg/77th-jsoc-official Discord]. Any ticket submitted through Discord will be reviewed by a staff member who was not involved in the situation, ensuring an objective and impartial response.</p>
</p>


<p class="guidelines">
In the end, it's up to the current admin online to judge what and how a rule applies to a specific event.
</p>


<p class="guidelines">
<h2 class="guidelines">Rules and reasoning</h2>
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.
</p>


<p class="guidelines">
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 post a complaint/query on the forums. Any complaints/queries posted on the forum will be processed by a member independent of the issue/situation who will provide a non-biased response.
</p>


<p class="guidelines">
<h3 class="guidelines">1. Do not disobey Admins or HQ (an Admin’s word is final):</h3>
Never argue with an admin on the server, follow the admins guidelines on the server and seek clarification on TS or the forums.
<p class="guidelines">Admins are responsible for upholding server standards and ensuring that the 77th JSOC vision for the servers is maintained.</p>
</p>
<p class="guidelines">If you believe a situation could have been handled differently, you are welcome to discuss it with the Admin involved on TeamSpeak. Alternatively, you may speak with a member of the Public Relations (PR) team or create a ticket on our [https://discord.gg/77th-jsoc-official Discord], providing any evidence you have available.</p>
<p class="guidelines">The HQ is the highest-ranking public player on the server. Their role is to facilitate smooth server flow and uphold server standards. Follow their directions, provided they are consistent with the server rules.</p>
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h2 class="guidelines">Rules and reasoning:</h2>
<h3 class="guidelines">2. Follow the Chain of Command: PR Members → Admins → HQ → Pilots/UAV → Squad Leaders:</h3>
<p class="guidelines">The Chain of Command is the cornerstone of the 77th JSOC servers. We rely heavily on this command structure to ensure our servers operate smoothly and successfully. It exists so that all players understand who they are expected to follow and listen to. Individuals higher in the Chain of Command may direct players below them; however, no member of the Chain of Command may instruct another player to violate the server rules.</p>
<p class="guidelines">'''Public Relations (PR) Members:'''
<br>
The highest-ranking individuals on the server are 77th JSOC Private Members who are part of the Public Relations department. All players are expected to follow their guidance in matters involving public interactions and administrative actions.</p>
<p class="guidelines">'''Admins:'''
<br>
Admins, including Ambassadors, are the second-highest authority on the server. They are responsible for enforcing the server rules and maintaining server standards.</p>
<p class="guidelines">'''Headquarters (HQ):'''
<br>
HQ determines how the server operates within the 77th JSOC Rules and Guidelines. They are responsible for coordinating the overall mission and ensuring effective server flow.</p>
<p class="guidelines">'''Pilots/UAV:'''
<br>
When HQ is present, Pilots and UAV operators serve in a supporting role. In the absence of HQ, they assume HQ’s administrative duties and responsibilities.
<br>
A Pilot has full authority over the aircraft they are flying. They always have the final decision regarding the safety of the aircraft, the flight route, and the suitability of a landing zone (LZ). While Pilots should coordinate with the requesting Squad Leader whenever possible, they may refuse any landing zone they consider unsafe.</p>
<p class="guidelines">'''Squad Leaders (SL):'''
<br>
Squad Leaders are responsible for leading their squads while coordinating with the command structure to ensure the smooth operation of both the server and its squads. They are the direct superiors of their squad members and are expected to lead within the 77th JSOC Rules and Guidelines.</p>
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">Do not disobey admins or HQ (an admin’s word is final):</h3>
<h3 class="guidelines">3. Bullying and verbal or written abuse will not be tolerated on any of our platforms:</h3>
<p class="guidelines">
<p class="guidelines">All players are expected to treat others with respect when interacting on 77th JSOC platforms, including the game server, TeamSpeak, Discord, forums, and any other official community channels.</p>
    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.
<p class="guidelines">Harmful, threatening, abusive, defamatory, slanderous, hateful, racially, or ethnically offensive language directed at a player, whether communicated verbally or in writing, is not acceptable and may result in administrative action.</p>
</p>
<p class="guidelines">Remember, if any of this behaviour is presented towards you, do not reciprocate it.</p>
 
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
<p class="guidelines">
    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 complaint/query on the [https://77th-jsoc.com/forum/viewforum.php?f=29 forum].
</p>


<p class="guidelines">
    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.
</p>


<h3 class="guidelines">4. Respect other players. If you are having issues with another player, contact an Admin:</h3>
<p class="guidelines">If you have an issue with another player, speak with an Admin or a member of the Public Relations (PR) team on TeamSpeak, or create a ticket on our [https://discord.gg/77th-jsoc-official Discord], providing any evidence you have available. An Admin may observe the situation, intervene if necessary, or provide further guidance.</p>
<p class="guidelines">Keep in mind that we are a multinational community, and differences in culture may sometimes lead to misunderstandings or conflicts. Behaviours and manners can be interpreted differently across cultures, so always be mindful of how your actions and words may be perceived by others. Exercising courtesy and respect helps maintain a welcoming environment for everyone.</p>
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">Follow the Chain of Command: Admins → HQ → Pilots → Squad Leaders:</h3>
<h3 class="guidelines">5. Intentional teamkilling is not allowed under any circumstances:</h3>
<p class="guidelines">
<p class="guidelines">Any form of intentional teamkilling is strictly prohibited on the 77th JSOC servers.</p>
    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.
<p class="guidelines">This rule also applies to High Value Targets (HVTs), prisoners, and civilians where the actions are deemed deliberate or excessive.</p>
</p>
<p class="guidelines">There are no exceptions to this rule. If you encounter a bug or gameplay issue, do not attempt to resolve it by teamkilling. The server provides systems and procedures to address such situations, and most issues can be resolved by respawning or rejoining the server.</p>
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]


<p class="guidelines">
    '''Admins:'''
<br />
The highest-ranking person(s) on the server are Admins, what they say is what goes.
</p>


<p class="guidelines">
<h3 class="guidelines">6. Hacking and mission exploitation will not be tolerated:</h3>
    ''' Headquarters (HQ):'''
<p class="guidelines">Any form of hacking, scripting, cheating, or exploitation is strictly prohibited.</p>
<br />
<p class="guidelines">This includes the use of mission file exploits, game bugs, or unintended mechanics to gain an advantage for yourself or your team beyond what was intended by the server developers. Any such behaviour will be considered a violation of the server rules and may result in administrative action.</p>
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 ([http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Guides_/_HQ/_HQ_Handbook HQ Handbook]).
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
</p>
 
<p class="guidelines">
'''Pilots:'''
<br />
When the HQ is present Pilots fulfill a supportive role. Additionally, in HQ’s absence, they will fulfill his administrative duties. A pilot is the commander of the aircraft they are flying. Pilots always have the final say inside their helicopter.
</p>


<p class="guidelines">
'''Squad Leaders (SL):'''
<br />
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.
</p>


<h3 class="guidelines">7. Griefing and obstructive behaviour will not be tolerated on any of our platforms:</h3>
<p class="guidelines">Griefing, trolling, or any deliberate attempt to annoy other players or reduce their enjoyment of our servers, TeamSpeak, Discord, or any other official 77th JSOC platform is strictly prohibited.</p>
<p class="guidelines">Obstructive behaviour is defined as any action or decision that unnecessarily disrupts server flow or interferes with the normal operation of the mission.</p>
<p class="guidelines">Reckless use of vehicles or aircraft that disrupts server flow, endangers players or equipment, or creates an unnecessary risk of asset loss may be considered obstructive behaviour. This includes, but is not limited to, unsafe flying near or over the base, landing aircraft or slinging vehicles or objects within the infantry spawn area, ramming targets or objectives, and any other misuse of vehicles that creates avoidable danger or disruption.</p>
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">Only HQ can allow vehicle usage (vehicles stay at the base until permission is granted by HQ):</h3>
<h3 class="guidelines">8. Excessive microphone spamming will not be tolerated on any of our platforms:</h3>
<p class="guidelines">
<p class="guidelines">Microphone spamming is not permitted in any in-game voice channel or on any official 77th JSOC platform.</p>
    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 [http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Guides_/_HQ/_HQ_Handbook#Reward_System: HQ Handbook] subsection about the reward system.
<p class="guidelines">This rule is not limited to voice communication and also applies to the use of soundboards or any other devices that broadcast sound effects, audio clips, music, or other noises.</p>
</p>
<p class="guidelines">An exception is made for music played inside a vehicle at a reasonable volume, provided that everyone in the vehicle is comfortable with it and no one objects.</p>
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]


<p class="guidelines">
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.
</p>


<p class="guidelines">
<h3 class="guidelines">9. Recruitment and advertising are not permitted on any of our platforms:</h3>
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.
<p class="guidelines">The 77th JSOC considers all of its servers, services, and community platforms to be official 77th JSOC spaces. Advertising or recruiting for other communities, units, groups, or services is not permitted on any of these platforms.</p>
</p>
<p class="guidelines">Any player found advertising or recruiting through a 77th JSOC platform may be permanently removed from the community.</p>
<p class="guidelines">If a player is found to be recruiting or advertising on behalf of a specific unit or group, all members of that unit or group who are involved may also be removed from all 77th JSOC platforms.</p>
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]


<p class="guidelines">
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 or admin deems it necessary.
</p>


<h3 class="guidelines">10. Players must operate within a squad:</h3>
<p class="guidelines">To promote teamwork and squad-based gameplay, all infantry players must join a squad before deploying to an objective.</p>
<p class="guidelines">Squad members are expected to remain within a reasonable distance of one another to provide effective support. Players who separate from their squad without a valid reason may be considered to be lonewolfing.</p>
<p class="guidelines">Players are expected to work together with their squad and follow the directions of their Squad Leader. However, a Squad Leader may not instruct a squad member to operate outside the squad’s effective support range.</p>
<p class="guidelines">Pilots may not be members of an infantry squad and are the only players permitted to leave the main base alone in order to perform their role.</p>
<p class="guidelines">HQ and UAV operators may not be members of a squad and are not permitted to leave the main base.</p>
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">Verbal abuse and bullying will not be tolerated / Respect other players:</h3>
<h3 class="guidelines">11. An infantry squad must consist of a minimum of 6 players and a maximum of 11 players:</h3>
<p class="guidelines">
<p class="guidelines">To promote squad-based gameplay, infantry squads must have at least 6 players and no more than 11 players before they may be deployed to an objective.</p>
    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.
<p class="guidelines">If a deployed squad falls below the minimum size of 6 players, it should be reinforced where possible by HQ, Pilots, or UAV. Once the squad has completed its current objective, it may not be redeployed to another objective until it once again meets the minimum squad size requirement.</p>
<br />
<p class="guidelines">If a Squad Leader leaves during an objective and the squad becomes disorganised or unable to operate effectively, HQ or an Admin may instruct the squad to respawn at the main base so it can be reorganised.</p>
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.
</p>
 
<p class="guidelines">
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.
</p>
 
<p class="guidelines">
Keep in mind, 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.
</p>
 
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">Intentional team-killing will not be tolerated:</h3>
<h3 class="guidelines">12. A squad is not allowed to exclude any player without a valid reason:</h3>
<p class="guidelines">
<p class="guidelines">Players may only be removed from a squad for a legitimate reason. For example, a player who is being disruptive, offensive, or is otherwise violating the server rules may be removed from the squad.</p>
    Any form of intentional team killing is not tolerated on the 77th JSOC servers.
<p class="guidelines">A valid reason for removing a player includes behaviour that negatively affects the squad or breaches the 77th JSOC Rules and Guidelines.</p>
</p>
<p class="guidelines">Players may not be excluded from a squad simply because they communicate by typing instead of using voice communication, or because they have a limited ability to communicate.</p>
 
<p class="guidelines">
    <u>'''No exceptions.'''</u>
</p>
 
<p class="guidelines">
    There are systems in place on the server for bug fixing. Therefore, there is no reason for team killing in a “bug fixing” situation.
</p>
 
<p class="guidelines">
    '''Anyone teamkilling may be subject to reprimands.'''
</p>
 
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">Griefing and obstructive play will not be tolerated:</h3>
<h3 class="guidelines">13. HQ, Pilots, and UAV operators must be on TeamSpeak and able to hear. HQ must have a working microphone:</h3>
<p class="guidelines">
<p class="guidelines">Players occupying the HQ, Pilot, or UAV roles must be connected to the TeamSpeak channel corresponding to the server they are playing on (EU1, EU2, or EU3).</p>
    A player that is deliberately trying to annoy others and make anyone else's game experience on our servers less enjoyable is regarded to Griefing others.
<p class="guidelines">Players in these roles are required to use the same name both in-game and on TeamSpeak to ensure they can be easily identified.</p>
<br />
<p class="guidelines">HQ is required to have a functioning microphone to facilitate effective communication on both TeamSpeak and the server. HQ must also be able to communicate effectively in English, both verbally and in writing.</p>
Trolling behavior falls under the same rules as Griefing.
<p class="guidelines">Pilots and UAV operators are required to be able to hear TeamSpeak communications and communicate effectively with other players in-game.</p>
</p>
 
<p class="guidelines">
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.
</p>
 
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">Hacking and mission exploitation will not be tolerated:</h3>
<h3 class="guidelines">14. When there is no HQ, squad assignment becomes the responsibility of the Pilots and UAV operators:</h3>
<p class="guidelines">
<p class="guidelines">In the absence of HQ, Pilots and UAV operators assume certain HQ duties and responsibilities. These include upholding server rules and standards, maintaining smooth server flow, responding to artillery fire support requests, ensuring squads are distributed appropriately between objectives, assigning players to squads, and coordinating transport and resupply.</p>
    Any form of hacking/scripting/exploitation will not be tolerated.
<p class="guidelines">Players awaiting squad assignment are expected to follow the directions of the Pilots and UAV operators.</p>
</p>
 
<p class="guidelines">
Any mission file exploits/bug exploit giving players or teams advantages not intended by the server developers will be regarded as unlawful and are all subject to reprimands.
</p>
 
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">Excessive mic spamming, especially of Side and Global channels, will not be tolerated:</h3>
<h3 class="guidelines">15. Firing any weapon at the base is not permitted:</h3>
<p class="guidelines">
<p class="guidelines">Players may not fire any weapon while within the main base.</p>
    Mic spamming is not tolerated on any channel, this includes side and global channels but is not exclusive to those channels.
<p class="guidelines">The only exceptions are player-operated Anti-Air (AA) and Artillery systems when they are being used by HQ, Pilots, or UAV operators in the performance of their role.</p>
<br />
Any player abusing the VON system in any VON channel on the 77th-JSOC servers may be reprimanded.
</p>
 
<p class="guidelines">
Excessive mic spamming includes but is not limited to, making sounds predominantly used to annoy or disturb others.
<br />
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.
</p>
 
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">No lone wolfing (players must be in a squad):</h3>
<h3 class="guidelines">16. Support Assets may only engage direct threats when called in by an Infantry Squad Leader close to an Objective, except in cases of self-defense:</h3>
<p class="guidelines">
<p class="guidelines">Support Assets must not deliberately provoke enemy forces in order to create a situation that justifies self-defense. To minimise unnecessary asset losses, support assets should avoid flying or driving near marked objectives unless it is required to complete their mission.</p>
    To promote squad-based gameplay, all infantry players are required to be part of a squad when playing on our servers.
<p class="guidelines">Support Assets may only engage targets when requested by an Infantry Squad Leader to address a direct threat to their squad. A direct threat is a target that has been observed by the Squad Leader and has the potential to affect the squad’s survivability or its ability to complete the objective. Support Assets may also be requested to destroy a target that is preventing the objective from being completed when no other reasonable means are available.</p>
<br />
<p class="guidelines">All support requests must be communicated over the Command Channel.</p>
Any player deploying to the AO without a squad will be regarded as a lonewolf '''(This includes the UAV operator)'''.
<p class="guidelines">A valid support request must identify a specific target, the target type, and its location. Where possible, the request should also include the estimated number of targets and the type of support required, such as UAV, Close Air Support (CAS), Armour, or Artillery. Broad or vague requests, such as asking a Support Asset to clear a large area without identifying a valid target, are not permitted unless the conditions of this rule are otherwise satisfied.</p>
</p>
<p class="guidelines">Artillery fire missions may only be requested using a specific grid reference or map marker.</p>
 
<p class="guidelines">Under no circumstances may a fire mission be requested or executed if there is a risk of teamkilling.</p>
<p class="guidelines">
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.
</p>
 
<p class="guidelines">
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.
</p>
 
<p class="guidelines">
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.
</p>
 
<p class="guidelines">
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.
</p>
 
<p class="guidelines">
    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.
</p>
 
<p class="guidelines">
    HQs may not be part of a squad and will be regarded as lonewolfing if they leave the main base.
</p>
 
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">HQ, pilots and UAV need to be on Teamspeak (microphone not required for pilots and UAV):</h3>
<h3 class="guidelines">17. Only an active HQ may authorise the use of Reward Assets:</h3>
<p class="guidelines">
<p class="guidelines">The use of Reward Assets requires authorisation from an active HQ. Some Reward Assets are additionally classified as Restricted Reward Assets. Once HQ signs off, Restricted Reward Assets may no longer be used and must be handled as described below. Reward Assets that are not classified as Restricted Reward Assets may continue to be used after HQ has signed off.</p>
    Players in HQ/Pilot/UAV slots must be in the correct TeamSpeak channel for the server they are on.  
<p class="guidelines">If HQ signs off while a Restricted Reward Asset ground vehicle is already deployed at an objective, its crew or assigned squad may remain to complete their current objective. Once the objective has been completed, or earlier if they choose, the vehicle must return directly to the main base.</p>
<br />
<p class="guidelines">CAS helicopters must return to the main base immediately when HQ signs off. Likewise, any Restricted Reward Asset that is travelling to an objective when HQ signs off must immediately return to the main base.</p>
This means the HQ/Pilot/UAV channel for EU1, EU2 or EU3 respectively.
<p class="guidelines">For a complete list of Restricted Reward Assets, refer to the list below or visit the Asset List page.</p>
<br />
<p class="guidelines">Vehicles that spawn as part of Side Missions or Priority Objectives are exempt from this rule. As these vehicles are not classified as Reward Assets, they may be used by the squads assigned to those objectives.</p>
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.
</p>
 
<p class="guidelines">
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.
<br />  
Players failing to use the same name in-game and on TS may be removed from the server slot by an admin.
</p>
 
<p class="guidelines">
'''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.
</p>
 
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">When there is no HQ, pilots are to sort out the squads:</h3>
<h3 class="guidelines">18. An Armour crew must occupy all vehicle crew positions, use appropriate roles, and operate exclusively as a Support Asset:</h3>
<p class="guidelines">
<p class="guidelines">Armoured vehicles must be fully crewed by players occupying the appropriate vehicle crew roles. These vehicles are to be operated exclusively as Support Assets and must follow all rules governing Support Asset usage.</p>
    When no HQ is online the duties and responsibilities of HQ fall on the pilots, the pilots will have to follow the same set of guidelines that normally regulates HQ and his actions.  
<p class="guidelines">Armoured vehicles must be obtained from the Armoured vehicle category in the Reward menu. They may not be acquired through the Car vehicle category under any circumstances.</p>
<br />
To this end, it is a good practice for all pilots to read and understand the [http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Guides_/_Pilot_/_Pilot_Handbook#Pilot_third_function: Pilot handbook] about pilots third function as well as the [http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Guides_/_HQ/_HQ_Handbook HQ Handbook].
<br />
Pilots 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.
</p>
 
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">CAP/CAS/UAV/Artillery/Armor are not to take down any targets unless called in by squad leaders:</h3>
<h3 class="guidelines">19. Deliberate or unnecessary destruction of BLUFOR assets is prohibited:</h3>
<p class="guidelines">
<p class="guidelines">Intentionally crashing, abandoning, suiciding, or otherwise destroying any BLUFOR aircraft, vehicle, or equipment without a valid operational reason is considered unnecessary destruction of BLUFOR assets.</p>
    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 ([http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Guides Role Guides]).
<p class="guidelines">This rule also applies to assets that are damaged but still recoverable. Whenever practical, damaged or downed aircraft and vehicles should be recovered rather than destroyed. Destroying a recoverable asset should only be considered as a last resort.</p>
</p>
<p class="guidelines">In exceptional circumstances, HQ or Pilots may decide to destroy or abandon a recoverable aircraft or vehicle if doing so is necessary to maintain server flow. For example, this may be appropriate when pilots or transport assets are urgently required elsewhere and recovery is not practical.</p>
 
<p class="guidelines">
    Mortars are regarded as an artillery asset on our servers and must follow the same ROE as artillery.  
<br />
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.
</p>
 
<p class="guidelines">
    A fire mission/support request needs to follow a specific format and contain certain information to be a valid mission.  
<br />
For clarifications on the format for a valid fire mission/support mission please read section [http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Guides_/_SL_/_Squad_Leader_Handbook#Calling_in_support: 5.2.4 calling in support of the SL handbook].
<br />
If the support request does not follow the guidelines set in the [http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Guides_/_SL_/_Squad_Leader_Handbook SL handbook] it should be regarded as an invalid request and disregarded.
</p>
 
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">Recruitment & advertising is not allowed on our platforms:</h3>
<h3 class="guidelines">20. All server elements must select an appropriate callsign from the available drop-down menu:</h3>
<p class="guidelines">
<p class="guidelines">All players are required to use the appropriate callsign for their role by selecting it from the in-game drop-down menu.</p>
    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.
<p class="guidelines">Infantry squads must use callsigns from the NATO Phonetic Alphabet, ranging from Alpha through Hotel.</p>
</p>
<p class="guidelines">Armour squads must use one of the following designated callsigns: Rhino, Thunder, Hammer, Anvil, Bulldog, Fury, Ironside, or Saber.</p>
 
<p class="guidelines">
    Any type of attempt to advertise and/or recruit players from/on any of the 77th-JSOC platforms will see the offender removed.  
<br />
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.
</p>
 
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">An infantry squad consists of a bare minimum of 6 players and a maximum of 11 players:</h3>
<h3 class="guidelines">21. Play Your Role:</h3>
<p class="guidelines">
<p class="guidelines">Players are expected to perform the responsibilities of the role they have selected. You must carry and use a primary weapon, wear an appropriate uniform, and bring the equipment required for your role. For complete equipment requirements and role-specific information, see the role descriptions below or visit the relevant role page.</p>
    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.
<p class="guidelines">Wetsuits may only be used when they are specifically required to complete an objective.</p>
</p>
<p class="guidelines">Support Asset crew members must select roles that do not negatively affect the balance or effectiveness of infantry squads.</p>
 
<p class="guidelines">Respawning requires permission from HQ. Pilots should only respawn when necessary to maintain server flow or to carry out their responsibilities, such as providing transport or performing HQ duties in HQ’s absence. Respawning should always be considered a last resort.</p>
<p class="guidelines">
    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.
</p>
 
<p class="guidelines">
    HQs may not be part of a squad.
</p>
 
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">An armor crew must fill all the vehicle crew slots:</h3>
<h1 class="guidelines">Role details (extension of Rule 21)</h1>
<p class="guidelines">
    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.
</p>
 
<p class="guidelines">
    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.
</p>


[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]


<h3 class="guidelines">HQ:</h3>
<p class="guidelines">HQ is responsible for maintaining overall server flow and is expected to have a comprehensive understanding of the server, its rules, and its gameplay. HQ works closely with the Pilots to deploy squads to objectives and is responsible for assigning players waiting at the squad assignment sign to appropriate squads, whether at the main base or in the field. HQ should keep squads balanced where practical, organise squad composition after server restarts, and accommodate reasonable player requests whenever possible.</p>
<p class="guidelines">You must occupy the designated HQ slot.</p>


<h3 class="guidelines">No TS-only squads, if a squad has a teammate not on TS the squad is not allowed to exclude him:</h3>
<h3 class="guidelines">Pilot:</h3>
<p class="guidelines">
<p class="guidelines">Pilots are expected to operate aircraft safely and competently, maintain server flow, and comply with all Support Asset rules. When HQ is offline, Pilots are also responsible for carrying out HQ’s duties.</p>
    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.
<p class="guidelines">Pilots are expected to transport squads safely from the main base to landing zones (LZs) near objectives. They must assess the suitability of each LZ and, if necessary, choose an alternative location while coordinating any changes with the requesting Squad Leader.</p>
<br />
<p class="guidelines">When HQ authorises a CAS aircraft, Pilots may only operate it if they are competent to do so and must comply with all CAS-related rules. If the aircraft requires a gunner, the gunner must not occupy an HQ, Pilot, or UAV role and must be a member of the same support squad as the Pilot.</p>
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.
<p class="guidelines">The Pilot operating an armed Reward aircraft must act as the Squad Leader of the support crew and must be able to hear and communicate with other Squad Leaders over the Command Channel.</p>
<br />
<p class="guidelines">During periods of low population, Pilots may continue to fly provided they fulfil their Pilot responsibilities and do not disrupt server flow. Players occupying a Pilot slot may not participate as infantry.</p>
'''This rule is not exclusive to Teamspeak, any third-party communications software outside the game is applicable to this rule.'''
</p>


[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
<h3 class="guidelines">UAV:</h3>
<p class="guidelines">UAV operators are responsible for providing reconnaissance and intelligence to squads assigned to objectives. They are also expected to provide CAS using the Greyhawk where appropriate and must be able to operate all UAV assets competently from the main base.</p>
<p class="guidelines">When HQ is offline, UAV operators are also expected to perform HQ duties.</p>


<h3 class="guidelines">Squad Leader:</h3>
<p class="guidelines">Squad Leaders are one of the most important roles on the server. They coordinate with HQ and Pilots to transport their squad from the main base to objectives and work with UAV operators to gather intelligence before and during missions.</p>
<p class="guidelines">Squad Leaders are responsible for requesting fire support when required, including Artillery, UAV CAS, Armour, and CAS Pilots. They are expected to coordinate with other squads to complete objectives efficiently, assist new players within their squad, and communicate with HQ or Pilots when additional squad members are needed.</p>


<h3 class="guidelines">All server elements need to have an appropriate callsign, Squad names are allowed to be only within the Phonetic Alphabet:</h3>
<h3 class="guidelines">Medic:</h3>
<p class="guidelines">
<p class="guidelines">Medics are riflemen first and medics second. They must carry and use a primary rifle and appropriate ammunition while also being responsible for treating injured and incapacitated teammates.</p>
    All server elements need to have appropriate callsigns for their function, any inappropriate callsigns will be changed.
<p class="guidelines">Medics are required to carry a Medkit and multiple First Aid Kits (FAKs).</p>
<br />
The callsigns must reflect the function of the element and not come across as offensive or irrelevant.
</p>


<p class="guidelines">
<h3 class="guidelines">Anti-Air:</h3>
    '''Examples for HQ would be:''' HQ, Crossroad, CentCom
<p class="guidelines">Anti-Air soldiers must carry a Titan AA launcher and spare missiles. Their primary responsibility is to engage and destroy enemy air threats.</p>
</p>


<p class="guidelines">
<h3 class="guidelines">Heavy AT:</h3>
    '''Examples of pilots would be:''' Pilot 1, Pilot 2,  Vortex, Hawk, Raptor, Transport
<p class="guidelines">Heavy Anti-Tank soldiers must carry an appropriate anti-tank launcher and spare ammunition. They are responsible for engaging and destroying enemy armoured vehicles.</p>
</p>


<p class="guidelines">
<h3 class="guidelines">Light AT:</h3>
    '''Examples for UAV would be:''' UAV, Hawk
<p class="guidelines">Light Anti-Tank soldiers must carry an appropriate light anti-tank launcher and spare ammunition. They are responsible for engaging enemy vehicles.</p>
</p>


<p class="guidelines">
<h3 class="guidelines">Engineer:</h3>
    An armor unit should use an appropriate callsign for its function, any inappropriate callsign will be changed.
<p class="guidelines">Engineers are recommended to carry a Toolkit, a Mine Detector for clearing mines, and C4 charges for destroying enemy static assets. They are expected to bring the equipment necessary to complete mission objectives.</p>
<br />
'''Examples of Armour would be:''' Hammer, Kilo (Armour), Rhino, etc.  
</p>


<p class="guidelines">
<h3 class="guidelines">Heavy Gunner:</h3>
    All infantry-based squads must use a name out of the NATO phonetic alphabet.
<p class="guidelines">Heavy Gunners are expected to use their medium machine gun to provide sustained firepower against heavily equipped enemy infantry and, where appropriate, lightly armoured vehicles.</p>
<br />
They are not allowed to have any additions to their names. They should purely be the phonetic name, nothing more, nothing less.  
<br />
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.
<br />
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.
</p>


[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
<h3 class="guidelines">Autorifleman:</h3>
<p class="guidelines">Autoriflemen are expected to provide sustained suppressive fire using a light machine gun. They must carry the appropriate high-capacity magazines for their weapon, typically holding between 100 and 200 rounds.</p>


<h3 class="guidelines">Marksman:</h3>
<p class="guidelines">Marksmen provide accurate long-range fire support while remaining with their squad. They are not expected to operate independently or separate from the squad, even when accompanied by a Medic or additional teammates.</p>


<h3 class="guidelines">Unnecessary destruction of BLUFOR vehicles will not be tolerated:</h3>
<h3 class="guidelines">Grenadier:</h3>
<p class="guidelines">
<p class="guidelines">Grenadiers are expected to carry an under-barrel grenade launcher and support their squad with 40 mm smoke, 40 mm illumination, and 40 mm high-explosive grenades.</p>
    No BLUFOR vehicles are to be destroyed unnecessarily.
<br />
This includes destroying the vehicle for a chance to receive another type or to destroy vehicles that are damaged but recoverable.
<br />
This rule applies to all vehicles, for transport helicopters, there may be some exceptions.
<br />
For a detailed procedure when dealing with helicopters, see the Pilot handbook subsection: [http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Guides_/_Pilot_/_Pilot_Handbook#Damaged_helicopter:  4.2.1 Damaged helicopter].
</p>


<h3 class="guidelines">Rifleman:</h3>
<p class="guidelines">Riflemen are the backbone of every squad. In addition to carrying their rifle and ammunition, they may be asked to carry additional ammunition for teammates, including LAT, HAT, AA missiles, or small-arms ammunition. They may also carry extra FAKs to support the squad Medic.</p>
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">Side channel voice is reserved for admins and HQ only:</h3>
<h1 class="guidelines">Restricted Reward Assets:</h1>
<p class="guidelines">
<h3 class="guidelines">Armoured</h3>
     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.
<ul class="rules">
</p>
    <li>AFV-4 Gorgon</li>
 
    <li>AMV-7 Marshall</li>
    <li>BTR-K Kamysh</li>
    <li>FV-720 Mora</li>
    <li>IFV-6c Panther</li>
    <li>AWC 301</li>
    <li>AWC 302 Nyx (AA)</li>
    <li>AWC 303 Nyx (Recon)</li>
    <li>AWC 304 Nyx (Autocannon)</li>
</ul>
<h3 class="guidelines">Boats</h3>
<ul class="rules">
    <li>Assault Boat</li>
    <li>RHIB</li>
    <li>SDV</li>
    <li>Speedboat</li>
</ul>
<h3 class="guidelines">Cars</h3>
<ul class="rules">
    <li>MSE-3 Marid</li>
    <li>MSE-3 Marid (Unarmed)</li>
    <li>AMV-7 Marshall (Unarmed)</li>
    <li>Prowler</li>
    <li>Prowler (Armed)</li>
    <li>Prowler (Black)</li>
    <li>Prowler (Black) (Armed)</li>
    <li>Prowler (Sand)</li>
    <li>Prowler (Sand) (Armed)</li>
    <li>Prowler (CTRG)</li>
    <li>Prowler (CTRG) (Armed)</li>
    <li>Hunter</li>
    <li>Hunter HMG</li>
    <li>Hunter GMG</li>
    <li>Strider (BLUFOR)</li>
    <li>Strider (BLUFOR) (HMG)</li>
    <li>Strider (BLUFOR) (GMG)</li>
    <li>Qilin (Black)</li>
    <li>Qilin (Black) (Armed)</li>
</ul>
<h3 class="guidelines">Helicopters</h3>
<ul class="rules">
    <li>AH-99 Blackfoot (Stub Wings)</li>
    <li>Mi-48 Kajman (Black)</li>
    <li>AH-99 Blackfoot</li>
    <li>AH-9 Pawnee</li>
    <li>PO-30 Orca</li>
    <li>WY-55 Hellcat</li>
    <li>Ghosthawk (Armed)</li>
</ul>
<h3 class="guidelines">Trucks</h3>
<ul class="rules">
     <li>HEMTT Medical</li>
    <li>HEMTT Transport (Covered)</li>
</ul>
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]




<h3 class="guidelines">Firing a weapon at the base -- unless at an enemy -- Is not permitted:</h3>
<h1 class="guidelines">Reward Assets:</h1>
<p class="guidelines">
<h3 class="guidelines">Helicopters</h3>
     It is not permitted to fire any type of weapon at the base, place or detonate any kind of charges at the base.
<ul class="rules">
<br />
    <li>MH-9 Hummingbird</li>
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 defence purposes/fire support.
    <li>PO-30 Orca (Unarmed)</li>
</p>
    <li>V-44 X Blackfish (Infantry)</li>
    <li>WY-55 Hellcat (Unarmed)</li>
    <li>Ghosthawk</li>
    <li>Mohawk</li>
    <li>Huron</li>
    <li>Taru</li>
</ul>
<h3 class="guidelines">UAV</h3>
<ul class="rules">
     <li>Mk41 VLS (Destroyer)</li>
</ul>
<h3 class="guidelines">Base AA & Artillery</h3>
<ul class="rules">
    <li>AA full rearm</li>
    <li>1x Smoke</li>
    <li>1x HE</li>
    <li>1x Guided</li>
    <li>1x Laser Guided</li>
    <li>M5 Sandstorm MLRS (Swap arty)</li>
</ul>
<h3 class="guidelines">Containers</h3>
<ul class="rules">
    <li>Huron Medical Container</li>
    <li>Supply Box [NATO]</li>
    <li>Basic Ammo [NATO]</li>
    <li>Taru Medical Pod (Black)</li>
    <li>Taru Transport Pod (Black)</li>
    <li>Taru Bench Pod (Black)</li>
</ul>




[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]<br>
[http://www.77th-jsoc.com/wiki1/77th_JSOC_/_Public_Servers_/_Rules back to top]<br>

Latest revision as of 07:45, 30 June 2026

Previous

Rules

List of rules

  • 1. Do not disobey Admins or HQ (an Admin’s word is final).
  • 2. Follow the Chain of Command: PR Members → Admins → HQ → Pilots/UAV → Squad Leaders.
  • 3. Bullying and verbal or written abuse will not be tolerated on any of our platforms.
  • 4. Respect other players. If you are having issues with another player, contact an Admin.
  • 5. Intentional teamkilling is not allowed under any circumstances.
  • 6. Hacking and mission exploitation will not be tolerated.
  • 7. Griefing and obstructive behaviour will not be tolerated on any of our platforms.
  • 8. Excessive microphone spamming will not be tolerated on any of our platforms.
  • 9. Recruitment and advertising are not permitted on any of our platforms.
  • 10. Players must operate within a squad.
  • 11. An infantry squad must consist of a minimum of 6 players and a maximum of 11 players.
  • 12. A squad is not allowed to exclude any player without a valid reason.
  • 13. HQ, Pilots, and UAV operators must be on TeamSpeak and able to hear. HQ must have a working microphone.
  • 14. When there is no HQ, squad assignment becomes the responsibility of the Pilots and UAV operators.
  • 15. Firing any weapon at the base is not permitted.
  • 16. Support Assets may only engage direct threats when called in by an Infantry Squad Leader close to an Objective, except in cases of self-defense.
  • 17. Only an active HQ may authorise the use of Reward Assets.
  • 18. An Armour crew must occupy all vehicle crew positions, use appropriate roles, and operate exclusively as a Support Asset.
  • 19. Deliberate or unnecessary destruction of BLUFOR assets is prohibited.
  • 20. All server elements must select an appropriate callsign from the available drop-down menu.
  • 21. Play Your Role.

back to top

Rule clarifications


The following clarifications are not intended to be a comprehensive explanation of the rules or how they are applied. They are provided as guidelines to help players better understand the rules, but are not limited to the examples listed.

If a player believes a situation is unclear or feels they have been treated unfairly, they are encouraged to speak with a member of the Public Relations (PR) team on TeamSpeak and/or create a ticket on our Discord. Any ticket submitted through Discord will be reviewed by a staff member who was not involved in the situation, ensuring an objective and impartial response.


Rules and reasoning


1. Do not disobey Admins or HQ (an Admin’s word is final):

Admins are responsible for upholding server standards and ensuring that the 77th JSOC vision for the servers is maintained.

If you believe a situation could have been handled differently, you are welcome to discuss it with the Admin involved on TeamSpeak. Alternatively, you may speak with a member of the Public Relations (PR) team or create a ticket on our Discord, providing any evidence you have available.

The HQ is the highest-ranking public player on the server. Their role is to facilitate smooth server flow and uphold server standards. Follow their directions, provided they are consistent with the server rules.

back to top


2. Follow the Chain of Command: PR Members → Admins → HQ → Pilots/UAV → Squad Leaders:

The Chain of Command is the cornerstone of the 77th JSOC servers. We rely heavily on this command structure to ensure our servers operate smoothly and successfully. It exists so that all players understand who they are expected to follow and listen to. Individuals higher in the Chain of Command may direct players below them; however, no member of the Chain of Command may instruct another player to violate the server rules.

Public Relations (PR) Members:
The highest-ranking individuals on the server are 77th JSOC Private Members who are part of the Public Relations department. All players are expected to follow their guidance in matters involving public interactions and administrative actions.

Admins:
Admins, including Ambassadors, are the second-highest authority on the server. They are responsible for enforcing the server rules and maintaining server standards.

Headquarters (HQ):
HQ determines how the server operates within the 77th JSOC Rules and Guidelines. They are responsible for coordinating the overall mission and ensuring effective server flow.

Pilots/UAV:
When HQ is present, Pilots and UAV operators serve in a supporting role. In the absence of HQ, they assume HQ’s administrative duties and responsibilities.
A Pilot has full authority over the aircraft they are flying. They always have the final decision regarding the safety of the aircraft, the flight route, and the suitability of a landing zone (LZ). While Pilots should coordinate with the requesting Squad Leader whenever possible, they may refuse any landing zone they consider unsafe.

Squad Leaders (SL):
Squad Leaders are responsible for leading their squads while coordinating with the command structure to ensure the smooth operation of both the server and its squads. They are the direct superiors of their squad members and are expected to lead within the 77th JSOC Rules and Guidelines.

back to top


3. Bullying and verbal or written abuse will not be tolerated on any of our platforms:

All players are expected to treat others with respect when interacting on 77th JSOC platforms, including the game server, TeamSpeak, Discord, forums, and any other official community channels.

Harmful, threatening, abusive, defamatory, slanderous, hateful, racially, or ethnically offensive language directed at a player, whether communicated verbally or in writing, is not acceptable and may result in administrative action.

Remember, if any of this behaviour is presented towards you, do not reciprocate it.

back to top


4. Respect other players. If you are having issues with another player, contact an Admin:

If you have an issue with another player, speak with an Admin or a member of the Public Relations (PR) team on TeamSpeak, or create a ticket on our Discord, providing any evidence you have available. An Admin may observe the situation, intervene if necessary, or provide further guidance.

Keep in mind that we are a multinational community, and differences in culture may sometimes lead to misunderstandings or conflicts. Behaviours and manners can be interpreted differently across cultures, so always be mindful of how your actions and words may be perceived by others. Exercising courtesy and respect helps maintain a welcoming environment for everyone.

back to top


5. Intentional teamkilling is not allowed under any circumstances:

Any form of intentional teamkilling is strictly prohibited on the 77th JSOC servers.

This rule also applies to High Value Targets (HVTs), prisoners, and civilians where the actions are deemed deliberate or excessive.

There are no exceptions to this rule. If you encounter a bug or gameplay issue, do not attempt to resolve it by teamkilling. The server provides systems and procedures to address such situations, and most issues can be resolved by respawning or rejoining the server.

back to top


6. Hacking and mission exploitation will not be tolerated:

Any form of hacking, scripting, cheating, or exploitation is strictly prohibited.

This includes the use of mission file exploits, game bugs, or unintended mechanics to gain an advantage for yourself or your team beyond what was intended by the server developers. Any such behaviour will be considered a violation of the server rules and may result in administrative action.

back to top


7. Griefing and obstructive behaviour will not be tolerated on any of our platforms:

Griefing, trolling, or any deliberate attempt to annoy other players or reduce their enjoyment of our servers, TeamSpeak, Discord, or any other official 77th JSOC platform is strictly prohibited.

Obstructive behaviour is defined as any action or decision that unnecessarily disrupts server flow or interferes with the normal operation of the mission.

Reckless use of vehicles or aircraft that disrupts server flow, endangers players or equipment, or creates an unnecessary risk of asset loss may be considered obstructive behaviour. This includes, but is not limited to, unsafe flying near or over the base, landing aircraft or slinging vehicles or objects within the infantry spawn area, ramming targets or objectives, and any other misuse of vehicles that creates avoidable danger or disruption.

back to top


8. Excessive microphone spamming will not be tolerated on any of our platforms:

Microphone spamming is not permitted in any in-game voice channel or on any official 77th JSOC platform.

This rule is not limited to voice communication and also applies to the use of soundboards or any other devices that broadcast sound effects, audio clips, music, or other noises.

An exception is made for music played inside a vehicle at a reasonable volume, provided that everyone in the vehicle is comfortable with it and no one objects.

back to top


9. Recruitment and advertising are not permitted on any of our platforms:

The 77th JSOC considers all of its servers, services, and community platforms to be official 77th JSOC spaces. Advertising or recruiting for other communities, units, groups, or services is not permitted on any of these platforms.

Any player found advertising or recruiting through a 77th JSOC platform may be permanently removed from the community.

If a player is found to be recruiting or advertising on behalf of a specific unit or group, all members of that unit or group who are involved may also be removed from all 77th JSOC platforms.

back to top


10. Players must operate within a squad:

To promote teamwork and squad-based gameplay, all infantry players must join a squad before deploying to an objective.

Squad members are expected to remain within a reasonable distance of one another to provide effective support. Players who separate from their squad without a valid reason may be considered to be lonewolfing.

Players are expected to work together with their squad and follow the directions of their Squad Leader. However, a Squad Leader may not instruct a squad member to operate outside the squad’s effective support range.

Pilots may not be members of an infantry squad and are the only players permitted to leave the main base alone in order to perform their role.

HQ and UAV operators may not be members of a squad and are not permitted to leave the main base.

back to top


11. An infantry squad must consist of a minimum of 6 players and a maximum of 11 players:

To promote squad-based gameplay, infantry squads must have at least 6 players and no more than 11 players before they may be deployed to an objective.

If a deployed squad falls below the minimum size of 6 players, it should be reinforced where possible by HQ, Pilots, or UAV. Once the squad has completed its current objective, it may not be redeployed to another objective until it once again meets the minimum squad size requirement.

If a Squad Leader leaves during an objective and the squad becomes disorganised or unable to operate effectively, HQ or an Admin may instruct the squad to respawn at the main base so it can be reorganised.

back to top


12. A squad is not allowed to exclude any player without a valid reason:

Players may only be removed from a squad for a legitimate reason. For example, a player who is being disruptive, offensive, or is otherwise violating the server rules may be removed from the squad.

A valid reason for removing a player includes behaviour that negatively affects the squad or breaches the 77th JSOC Rules and Guidelines.

Players may not be excluded from a squad simply because they communicate by typing instead of using voice communication, or because they have a limited ability to communicate.

back to top


13. HQ, Pilots, and UAV operators must be on TeamSpeak and able to hear. HQ must have a working microphone:

Players occupying the HQ, Pilot, or UAV roles must be connected to the TeamSpeak channel corresponding to the server they are playing on (EU1, EU2, or EU3).

Players in these roles are required to use the same name both in-game and on TeamSpeak to ensure they can be easily identified.

HQ is required to have a functioning microphone to facilitate effective communication on both TeamSpeak and the server. HQ must also be able to communicate effectively in English, both verbally and in writing.

Pilots and UAV operators are required to be able to hear TeamSpeak communications and communicate effectively with other players in-game.

back to top


14. When there is no HQ, squad assignment becomes the responsibility of the Pilots and UAV operators:

In the absence of HQ, Pilots and UAV operators assume certain HQ duties and responsibilities. These include upholding server rules and standards, maintaining smooth server flow, responding to artillery fire support requests, ensuring squads are distributed appropriately between objectives, assigning players to squads, and coordinating transport and resupply.

Players awaiting squad assignment are expected to follow the directions of the Pilots and UAV operators.

back to top


15. Firing any weapon at the base is not permitted:

Players may not fire any weapon while within the main base.

The only exceptions are player-operated Anti-Air (AA) and Artillery systems when they are being used by HQ, Pilots, or UAV operators in the performance of their role.

back to top


16. Support Assets may only engage direct threats when called in by an Infantry Squad Leader close to an Objective, except in cases of self-defense:

Support Assets must not deliberately provoke enemy forces in order to create a situation that justifies self-defense. To minimise unnecessary asset losses, support assets should avoid flying or driving near marked objectives unless it is required to complete their mission.

Support Assets may only engage targets when requested by an Infantry Squad Leader to address a direct threat to their squad. A direct threat is a target that has been observed by the Squad Leader and has the potential to affect the squad’s survivability or its ability to complete the objective. Support Assets may also be requested to destroy a target that is preventing the objective from being completed when no other reasonable means are available.

All support requests must be communicated over the Command Channel.

A valid support request must identify a specific target, the target type, and its location. Where possible, the request should also include the estimated number of targets and the type of support required, such as UAV, Close Air Support (CAS), Armour, or Artillery. Broad or vague requests, such as asking a Support Asset to clear a large area without identifying a valid target, are not permitted unless the conditions of this rule are otherwise satisfied.

Artillery fire missions may only be requested using a specific grid reference or map marker.

Under no circumstances may a fire mission be requested or executed if there is a risk of teamkilling.

back to top


17. Only an active HQ may authorise the use of Reward Assets:

The use of Reward Assets requires authorisation from an active HQ. Some Reward Assets are additionally classified as Restricted Reward Assets. Once HQ signs off, Restricted Reward Assets may no longer be used and must be handled as described below. Reward Assets that are not classified as Restricted Reward Assets may continue to be used after HQ has signed off.

If HQ signs off while a Restricted Reward Asset ground vehicle is already deployed at an objective, its crew or assigned squad may remain to complete their current objective. Once the objective has been completed, or earlier if they choose, the vehicle must return directly to the main base.

CAS helicopters must return to the main base immediately when HQ signs off. Likewise, any Restricted Reward Asset that is travelling to an objective when HQ signs off must immediately return to the main base.

For a complete list of Restricted Reward Assets, refer to the list below or visit the Asset List page.

Vehicles that spawn as part of Side Missions or Priority Objectives are exempt from this rule. As these vehicles are not classified as Reward Assets, they may be used by the squads assigned to those objectives.

back to top


18. An Armour crew must occupy all vehicle crew positions, use appropriate roles, and operate exclusively as a Support Asset:

Armoured vehicles must be fully crewed by players occupying the appropriate vehicle crew roles. These vehicles are to be operated exclusively as Support Assets and must follow all rules governing Support Asset usage.

Armoured vehicles must be obtained from the Armoured vehicle category in the Reward menu. They may not be acquired through the Car vehicle category under any circumstances.

back to top


19. Deliberate or unnecessary destruction of BLUFOR assets is prohibited:

Intentionally crashing, abandoning, suiciding, or otherwise destroying any BLUFOR aircraft, vehicle, or equipment without a valid operational reason is considered unnecessary destruction of BLUFOR assets.

This rule also applies to assets that are damaged but still recoverable. Whenever practical, damaged or downed aircraft and vehicles should be recovered rather than destroyed. Destroying a recoverable asset should only be considered as a last resort.

In exceptional circumstances, HQ or Pilots may decide to destroy or abandon a recoverable aircraft or vehicle if doing so is necessary to maintain server flow. For example, this may be appropriate when pilots or transport assets are urgently required elsewhere and recovery is not practical.

back to top


20. All server elements must select an appropriate callsign from the available drop-down menu:

All players are required to use the appropriate callsign for their role by selecting it from the in-game drop-down menu.

Infantry squads must use callsigns from the NATO Phonetic Alphabet, ranging from Alpha through Hotel.

Armour squads must use one of the following designated callsigns: Rhino, Thunder, Hammer, Anvil, Bulldog, Fury, Ironside, or Saber.

back to top


21. Play Your Role:

Players are expected to perform the responsibilities of the role they have selected. You must carry and use a primary weapon, wear an appropriate uniform, and bring the equipment required for your role. For complete equipment requirements and role-specific information, see the role descriptions below or visit the relevant role page.

Wetsuits may only be used when they are specifically required to complete an objective.

Support Asset crew members must select roles that do not negatively affect the balance or effectiveness of infantry squads.

Respawning requires permission from HQ. Pilots should only respawn when necessary to maintain server flow or to carry out their responsibilities, such as providing transport or performing HQ duties in HQ’s absence. Respawning should always be considered a last resort.

back to top


Role details (extension of Rule 21)


HQ:

HQ is responsible for maintaining overall server flow and is expected to have a comprehensive understanding of the server, its rules, and its gameplay. HQ works closely with the Pilots to deploy squads to objectives and is responsible for assigning players waiting at the squad assignment sign to appropriate squads, whether at the main base or in the field. HQ should keep squads balanced where practical, organise squad composition after server restarts, and accommodate reasonable player requests whenever possible.

You must occupy the designated HQ slot.

Pilot:

Pilots are expected to operate aircraft safely and competently, maintain server flow, and comply with all Support Asset rules. When HQ is offline, Pilots are also responsible for carrying out HQ’s duties.

Pilots are expected to transport squads safely from the main base to landing zones (LZs) near objectives. They must assess the suitability of each LZ and, if necessary, choose an alternative location while coordinating any changes with the requesting Squad Leader.

When HQ authorises a CAS aircraft, Pilots may only operate it if they are competent to do so and must comply with all CAS-related rules. If the aircraft requires a gunner, the gunner must not occupy an HQ, Pilot, or UAV role and must be a member of the same support squad as the Pilot.

The Pilot operating an armed Reward aircraft must act as the Squad Leader of the support crew and must be able to hear and communicate with other Squad Leaders over the Command Channel.

During periods of low population, Pilots may continue to fly provided they fulfil their Pilot responsibilities and do not disrupt server flow. Players occupying a Pilot slot may not participate as infantry.

UAV:

UAV operators are responsible for providing reconnaissance and intelligence to squads assigned to objectives. They are also expected to provide CAS using the Greyhawk where appropriate and must be able to operate all UAV assets competently from the main base.

When HQ is offline, UAV operators are also expected to perform HQ duties.

Squad Leader:

Squad Leaders are one of the most important roles on the server. They coordinate with HQ and Pilots to transport their squad from the main base to objectives and work with UAV operators to gather intelligence before and during missions.

Squad Leaders are responsible for requesting fire support when required, including Artillery, UAV CAS, Armour, and CAS Pilots. They are expected to coordinate with other squads to complete objectives efficiently, assist new players within their squad, and communicate with HQ or Pilots when additional squad members are needed.

Medic:

Medics are riflemen first and medics second. They must carry and use a primary rifle and appropriate ammunition while also being responsible for treating injured and incapacitated teammates.

Medics are required to carry a Medkit and multiple First Aid Kits (FAKs).

Anti-Air:

Anti-Air soldiers must carry a Titan AA launcher and spare missiles. Their primary responsibility is to engage and destroy enemy air threats.

Heavy AT:

Heavy Anti-Tank soldiers must carry an appropriate anti-tank launcher and spare ammunition. They are responsible for engaging and destroying enemy armoured vehicles.

Light AT:

Light Anti-Tank soldiers must carry an appropriate light anti-tank launcher and spare ammunition. They are responsible for engaging enemy vehicles.

Engineer:

Engineers are recommended to carry a Toolkit, a Mine Detector for clearing mines, and C4 charges for destroying enemy static assets. They are expected to bring the equipment necessary to complete mission objectives.

Heavy Gunner:

Heavy Gunners are expected to use their medium machine gun to provide sustained firepower against heavily equipped enemy infantry and, where appropriate, lightly armoured vehicles.

Autorifleman:

Autoriflemen are expected to provide sustained suppressive fire using a light machine gun. They must carry the appropriate high-capacity magazines for their weapon, typically holding between 100 and 200 rounds.

Marksman:

Marksmen provide accurate long-range fire support while remaining with their squad. They are not expected to operate independently or separate from the squad, even when accompanied by a Medic or additional teammates.

Grenadier:

Grenadiers are expected to carry an under-barrel grenade launcher and support their squad with 40 mm smoke, 40 mm illumination, and 40 mm high-explosive grenades.

Rifleman:

Riflemen are the backbone of every squad. In addition to carrying their rifle and ammunition, they may be asked to carry additional ammunition for teammates, including LAT, HAT, AA missiles, or small-arms ammunition. They may also carry extra FAKs to support the squad Medic.

back to top


Restricted Reward Assets:

Armoured

  • AFV-4 Gorgon
  • AMV-7 Marshall
  • BTR-K Kamysh
  • FV-720 Mora
  • IFV-6c Panther
  • AWC 301
  • AWC 302 Nyx (AA)
  • AWC 303 Nyx (Recon)
  • AWC 304 Nyx (Autocannon)

Boats

  • Assault Boat
  • RHIB
  • SDV
  • Speedboat

Cars

  • MSE-3 Marid
  • MSE-3 Marid (Unarmed)
  • AMV-7 Marshall (Unarmed)
  • Prowler
  • Prowler (Armed)
  • Prowler (Black)
  • Prowler (Black) (Armed)
  • Prowler (Sand)
  • Prowler (Sand) (Armed)
  • Prowler (CTRG)
  • Prowler (CTRG) (Armed)
  • Hunter
  • Hunter HMG
  • Hunter GMG
  • Strider (BLUFOR)
  • Strider (BLUFOR) (HMG)
  • Strider (BLUFOR) (GMG)
  • Qilin (Black)
  • Qilin (Black) (Armed)

Helicopters

  • AH-99 Blackfoot (Stub Wings)
  • Mi-48 Kajman (Black)
  • AH-99 Blackfoot
  • AH-9 Pawnee
  • PO-30 Orca
  • WY-55 Hellcat
  • Ghosthawk (Armed)

Trucks

  • HEMTT Medical
  • HEMTT Transport (Covered)

back to top


Reward Assets:

Helicopters

  • MH-9 Hummingbird
  • PO-30 Orca (Unarmed)
  • V-44 X Blackfish (Infantry)
  • WY-55 Hellcat (Unarmed)
  • Ghosthawk
  • Mohawk
  • Huron
  • Taru

UAV

  • Mk41 VLS (Destroyer)

Base AA & Artillery

  • AA full rearm
  • 1x Smoke
  • 1x HE
  • 1x Guided
  • 1x Laser Guided
  • M5 Sandstorm MLRS (Swap arty)

Containers

  • Huron Medical Container
  • Supply Box [NATO]
  • Basic Ammo [NATO]
  • Taru Medical Pod (Black)
  • Taru Transport Pod (Black)
  • Taru Bench Pod (Black)


back to top