aboutsummaryrefslogtreecommitdiff
path: root/communities
diff options
context:
space:
mode:
authorAlex Pooley (@zuedev) <zuedev@gmail.com>2026-05-26 07:58:57 +0100
committerAlex Pooley (@zuedev) <zuedev@gmail.com>2026-05-26 07:58:57 +0100
commit687932096a0728d3d0bb22c98f7b0285923b203f (patch)
tree15b6573735493da893b1348adc6e97d5b0c72a12 /communities
parenteeb21748a36b8d35b6edd374980f961ec4fc8628 (diff)
downloadunnamed-group-687932096a0728d3d0bb22c98f7b0285923b203f.tar
unnamed-group-687932096a0728d3d0bb22c98f7b0285923b203f.tar.gz
unnamed-group-687932096a0728d3d0bb22c98f7b0285923b203f.tar.bz2
unnamed-group-687932096a0728d3d0bb22c98f7b0285923b203f.tar.xz
unnamed-group-687932096a0728d3d0bb22c98f7b0285923b203f.zip
add Code of Conduct
Diffstat (limited to 'communities')
-rw-r--r--communities/174bg/handbook/public/index.html215
1 files changed, 215 insertions, 0 deletions
diff --git a/communities/174bg/handbook/public/index.html b/communities/174bg/handbook/public/index.html
index 25d7c5d..6be87cf 100644
--- a/communities/174bg/handbook/public/index.html
+++ b/communities/174bg/handbook/public/index.html
@@ -410,6 +410,221 @@
</section>
</article>
+ <article id="rules-of-engagement">
+ <h2>Rules of Engagement</h2>
+ <p>
+ The Rules of Engagement define when and how members of the 174th
+ Battle Group are authorised to use force. All members are expected to
+ know and follow these rules at all times. Failure to do so may result
+ in disciplinary action.
+ </p>
+
+ <section id="authorised-use-of-force">
+ <h3>Authorised Use of Force</h3>
+ <p>Force is authorised only under the following conditions:</p>
+ <ul>
+ <li>
+ <strong>Direct hostile action:</strong> A target has taken hostile
+ action against group members or assets.
+ </li>
+ <li>
+ <strong>Demonstrated hostile intent:</strong> A target has
+ displayed clear hostile intent, such as weapons charged and
+ directed at group personnel or an aggressive approach with no
+ communication.
+ </li>
+ <li>
+ <strong>Standing orders:</strong> Command has designated the
+ target hostile by standing order prior to the engagement.
+ </li>
+ <li>
+ <strong>Active contract or mission objective:</strong> The target
+ is identified as an objective within a sanctioned mission or
+ contract.
+ </li>
+ <li>
+ <strong>Defence of a neutral or civilian:</strong> A neutral or
+ civilian is under active attack and the group has the capacity to
+ intervene.
+ </li>
+ </ul>
+ </section>
+
+ <section id="escalation-and-warning">
+ <h3>Escalation and Warning</h3>
+ <p>
+ Unless a member or the group is under active fire, a warning must be
+ issued before engaging. Members must make a reasonable attempt to
+ communicate intent and allow the target an opportunity to stand
+ down. If the target does not respond or continues to advance, force
+ may be used under the applicable condition above.
+ </p>
+ <p>
+ Offensive engagements, where the group initiates contact against a
+ target not currently attacking, require explicit authorisation from
+ a Rank 4 or higher officer, or from the council. Individual members
+ may not initiate offensive action on their own authority.
+ </p>
+ </section>
+
+ <section id="civilians-and-neutrals">
+ <h3>Civilians and Neutrals</h3>
+ <p>
+ The default stance toward civilians and neutral parties is to avoid
+ interaction entirely. Members must not provoke, threaten, or engage
+ neutral parties without authorisation. If a neutral becomes a direct
+ threat, the escalation process applies before force may be used.
+ </p>
+ </section>
+
+ <section id="surrendered-and-fleeing-enemies">
+ <h3>Surrendered and Fleeing Enemies</h3>
+ <p>
+ Enemies who surrender or attempt to flee must be pursued and
+ captured where possible. Lethal force against a surrendered or
+ fleeing enemy is a last resort, permitted only when capture is not
+ feasible and the enemy remains an active threat. Rank 3 and above
+ may authorise the release of a captured enemy if operational
+ circumstances require it.
+ </p>
+ </section>
+
+ <section id="prohibited-actions">
+ <h3>Prohibited Actions</h3>
+ <p>
+ The following actions are prohibited at all times, regardless of
+ orders:
+ </p>
+ <ul>
+ <li>
+ <strong>Impairing medical vessels:</strong> Medical ships must not
+ be attacked, disabled, or obstructed unless the vessel is
+ confirmed hostile and the group has its own medical capacity
+ available.
+ </li>
+ <li>
+ <strong>Destroying escape pods:</strong> Escape pods must never be
+ destroyed. Members are expected to pursue and capture them where
+ possible.
+ </li>
+ <li>
+ <strong>Griefing:</strong> Harassment, repeated unprovoked
+ attacks, and any conduct intended to ruin the experience of other
+ players is strictly prohibited.
+ </li>
+ </ul>
+ </section>
+
+ <section id="friendly-fire">
+ <h3>Friendly Fire</h3>
+ <p>
+ All friendly fire incidents, accidental or otherwise, must be
+ reported to the commanding officer immediately and documented.
+ Members involved must stand down and await instruction before
+ continuing the engagement.
+ </p>
+ </section>
+
+ <section id="target-verification">
+ <h3>Target Verification</h3>
+ <p>
+ Before engaging any target, members must have visual confirmation of
+ hostile action or recognised hostile markings. Uncertainty is not
+ sufficient grounds to open fire. If a member cannot confirm a target
+ is hostile, they must hold fire and seek clarification from their
+ commanding officer.
+ </p>
+ </section>
+ </article>
+
+ <article id="code-of-conduct">
+ <h2>Code of Conduct</h2>
+ <p>
+ The Code of Conduct sets out the standards of behaviour expected of
+ all members of the 174th Battle Group. It applies across all group
+ platforms and activities: in-game, on Discord, on any other group
+ tools, and on external platforms when a member is visibly representing
+ the group. Membership is conditional on upholding these standards.
+ </p>
+
+ <section id="expected-behaviour">
+ <h3>Expected Behaviour</h3>
+ <p>All members are expected to:</p>
+ <ul>
+ <li>
+ Treat all members and non-members with respect at all times.
+ </li>
+ <li>
+ Refrain from harassment, hate speech, and discrimination in any
+ form.
+ </li>
+ <li>Follow the orders of ranking members during operations.</li>
+ <li>
+ Raise disputes through proper channels rather than through direct
+ confrontation.
+ </li>
+ <li>Be honest with leadership and fellow members.</li>
+ </ul>
+ </section>
+
+ <section id="disciplinary-process">
+ <h3>Disciplinary Process</h3>
+ <p>
+ Discipline is handled on a case by case basis. There are no fixed
+ tiers; the response is proportionate to the severity and context of
+ the conduct in question.
+ </p>
+ <ul>
+ <li>
+ <strong>Informal warning:</strong> Any Rank 3 or above may issue
+ an informal warning for minor conduct issues.
+ </li>
+ <li>
+ <strong>Formal warning:</strong> A Rank 4 officer or department
+ head may issue a formal warning for more serious or repeated
+ issues.
+ </li>
+ <li>
+ <strong>Removal:</strong> Removal from the group requires a vote
+ of the Rank 5 council. A majority is required to pass.
+ </li>
+ </ul>
+ <p>
+ Members subject to disciplinary action have the right to present
+ their account of events before a decision is reached. Inactivity is
+ not treated as a conduct issue and is governed separately.
+ </p>
+ </section>
+
+ <section id="grounds-for-immediate-removal">
+ <h3>Grounds for Immediate Removal</h3>
+ <p>
+ The following offences result in immediate removal from the group
+ without prior warning. The council may vote to make the removal
+ permanent.
+ </p>
+ <ul>
+ <li>Cheating or exploiting game mechanics.</li>
+ <li>
+ Doxxing or sharing personal information about another member
+ without their consent.
+ </li>
+ <li>Hate speech or discrimination of any kind.</li>
+ <li>Threatening or blackmailing members.</li>
+ </ul>
+ </section>
+
+ <section id="appeals">
+ <h3>Appeals</h3>
+ <p>
+ Any member who has received a formal warning or been removed from
+ the group may appeal the decision to the full Rank 5 council. The
+ council will review the appeal and reach a final decision by
+ majority vote. Appeal decisions are binding.
+ </p>
+ </section>
+ </article>
+
<article id="fleet-composition">
<h2>Fleet Composition</h2>