Spearhead Documentation
Spearhead S3
Spearhead S3
  • 🚀About
    • 📘Spearhead S3 SOP
  • Mission Development Docs
    • Mission Development Requirements
  • SHG Workshop Mods
    • [SHG] Dev Tools
    • [SHG] Player Configs
    • [SHG] JBAD RHS IED Compat
Powered by GitBook
On this page
  • Objective and Framework:
  • Directive:
  • Personnel:
  • GMs as players
  • GM restrictions
  • Media Restrictions
  • GM Whitelisted Restrictions
  • Reporter Role Restrictions
  • Assets:
  • Miscellaneous
  1. About

Spearhead S3 SOP

Callsign: Spearhead-3

Objective and Framework:

Spearhead HQ is tasked with Tactical Command and Operational Execution for the Spearhead Gaming MilSim community. Members will be hand selected based on the following criteria.

  • Displayed aptitude in Game Master mechanics, and fluent in their understanding of MilSim SOP, and able to maintain a professional composure while conducting MilSim Game Mastering.

  • Interest in providing MilSim CO and XO assistance with Mission Execution and Intelligence Support.

  • Interest in working behind the scenes of the community to develop an exceptional product, our MilSim deployments and events.

  • Interest in Direct Action as a tertiary objective.

  • Temperament and mindset capable of "hurry up and wait", potentially for long periods of time, and especially during operations.

  • Understanding how to develop a practical loadout that is functional, light, and complete. One that will allow you to complete the tasks assigned, and will also allow you to travel by foot up to and possibly beyond 10 Kilometers.

  • A deep seated love for running, walking, crouching, and crawling through the forest, desert, swamp, ocean, mountains, etc.

  • Ability to follow orders and not complain about the decisions made by HQ Command.

Radio Channel: 66.6

Directive:

S3 will serve to prepare objectives, storyline, and to provide intelligence for Unit Commanders to facilitate their ability to create tactical plans of action. S3 will work with Mission Developers to create compelling content, storyline, overall operation plans, objectives, and then will be foundational in the execution of those plans.

S3 will actively monitor the operations, AI, and player base for game breaking functions and blatant SOP violations. Those items will be relayed to the CO and XO for further measures.

Personnel:

Staff

Permanent members of S3 with all rights and responsibilities. Primarily responsible for mission development, releasing WARNOs, server maintenance, and fixing any necessary issues.

Active Mission Dev

Temporary member of S3, to assist with mission planning and execution on the current active mission. May or may not GM, as requested by S3. Must follow all GM guidelines and directives from staff. Does not get a Zeus module, only admin login.

GM Whitelisted

Trusted members of the community who may GM at the call of S3 or milsim HQ/leadership, or act as special characters during operations. Must listen to directions of S3/HQ staff when operating in this capacity. Does not get a Zeus module. May receive an admin login.

Mission Dev

Not technically a part of S3. Subject matter experts on specific Arma 3 mods or processes.

The following rulesets are established for transparency and for the ability to hold accountable any misconduct. Any GM found to be abusing the player base, or circumventing these standards will be removed immediately upon confirmation by Spearhead HQ.

GMs as players

  • Zeus should be figuratively invisible to everyone and help balance ALiVE in line with the ground commander's or mission maker's intent.

  • Zeus does not participate in active operations but can work in a support role behind the front line. IE logistics.

  • No revealing information that the players should not know.

  • HQ is not intended to be used as an engagement opener and will only engage combatants when it is in defense, necessary to complete their missions, or when needed by the Ground Forces Commander.

  • You are not allowed to use Zeus when out in the field (unless you have to fix something).

GM restrictions

Discretion is a key element to using zeus so that players can remain immersed and not be ruined by knowing a human element is going against them in order to not cause resentment, favoritism or nepotism. To this effect:

  • Never kill players. Direct engagement from a GM will only be distraction fire, suppression, or exaggerated pulled shots. Do not excessively use GLs, grenades, etc as AI would not do so either.

  • Fire against friendlies may only be for effect, disabling vehicles (i.e shooting out the engine block, tires, small arms fire against up-armored vics) is appropriate. Outright blowing up vehicles is not.

  • Appropriate forces (Check GM doc for factions) can be spawned to drive the narrative as long as it makes sense for battlefield conditions (i.e not spawning troops in places where spearhead has just cleared or spawning directly in defilade next to friendlies). Always have units/assets come from a realistic engagement range or follow likely enemy modus operandi.

  • When using Zeus, you are not allowed to use modules to troll players during patrols or operations. This includes but not limited to: Lighting Strike, dropping ordnance on top of players, spawning enemies very close to players, using the punishment module, etc.

  • When using Zeus, you are not to pass along intel to players in the field. You can give them a general location of an objective if one is created, but you cannot say that there are enemies close to you or give visual hints.

Media Restrictions

GMs may post media (video or photos) to the community media channel if they are in accordance with the following guidelines.

  1. No zeus interface (Pressing backspace to hide interface and using the cinematic camera is fine)

  2. No revealing Out-Of-Character information that the players should not know.

GM Whitelisted Restrictions

You are not a full member of S3, so keep these restrictions in mind on top of those above:

  • When logging into the Admin slot for Zeus, you are not allowed to change mission settings unless approved by HQ or S3 lead

  • When logging in with the intention of being a GM, you are to slot with your appropriate unit. IE. if you are a member of Aviation and you want to GM, you are to slot as Aviation, not a member of Spearhead/S3.

  • You may not leave base and GM, except to fix something quickly (IE weather)

Reporter Role Restrictions

Players listed for reporter roles include HQ,S3, GM whitelisted, and others if approved by S3 & HQ. The following restrictions will be in place while in this slot:

  • Reporters at no time may be armed or be involved in combat operations.

  • Must stay at least 20m back from any units active in the field unless invited closer. Reporters must stay behind the front line of friendly advance. At no time should the reporters put themselves within the line of fire or in a place that may become under fire in the near future.

  • Must not wander off on their own, ideally attached to an individual or team.

  • Do not bother players while they are engaged with the enemy or conducting a task. You should be a fly on the wall. Discuss with players at base, while on a drive, or at hold points, if allowed by the leadership and the situation is appropriate.

  • Do not bother leadership / ground force commander unless they have consented with you engaging with them, they are busy.

  • Should ride with players if there is a spot available. Will ride using their own vic if there is no space in player vehicles, or if the ground force commander prefers this.

Assets:

Assets will be specific to mission, but may consist of the standard uniform used by all friendly forces as the standard battle dress or a variant thereof, a group specific camouflage and/or plain drab uniforms. If you are out in the field, you must wear equipment fitting the unit that you are attached to. That is, if you are attached to 3ID you look like 3ID. If you are attached to DET7, you look like DET7. This applies to uniforms. No limitations if you are GM at base and do not plan to leave the wire, but do not dress like an idiot.

Miscellaneous

S3 Staff and GM assistants (if no S3 is on and the situation is dire) have the power to ban players in violation of Spearhead SOP from the milsim server & teamspeak for a maximum of (1) day. It is necessary to contact the unit leader of the individual before making this call, but extremely disruptive behavior such as team killing or asset destruction require only that the unit leaders be notified after the risk has been removed. At this point, HQ and/or unit leads can be petitioned to increase ban length.

PreviousAboutNextMission Development Requirements

Last updated 5 months ago

🚀
📘