How we play

Basic Requirements

• You must be at least 16 years old, and act it.<br>A 15-year-old who acts 30 is fine;<br>a 30-year-old who acts 15 is not.
• You must have a legal copy of Arma 3.
• You must be proficient in English.
• You need the TeamSpeak 3 client and a working microphone and speakers or headset. ACRE2 radios run through TeamSpeak. You need to hear us and we need to hear you. You will not be allowed to stay in game without TeamSpeak.

Member Status

• Recruit becomes Active after 2 ops, unless your team leader raises a problem.
• Status is set by staff and kept in TAC//PAC.
• Moving to Reserve is not a strike and not a punishment.

What Military Simulation Means to Us

The 1st JMSB is a military simulation unit. That word means different things across the Arma community, and units offer different levels of tactical realism and paperwork.

To us it means we use proper military tactics in game. We have rank, but it is there to define roles in the game. We do not expect salutes or to be called sir or ma'am.

We aim to be on mission from the start of the OPORD to the AAR. On mission means we take the game seriously, use proper tactics, keep communications discipline, follow the orders of the operation's leadership, and follow the ROE.

Our Play Style

• View is restricted to first person, except in vehicles.
• Medical is ACE medical, optionally with Advanced Combat Medicine.
• There is no respawn. A medic evacuates a fallen player and brings them back into the fight.
• Join in progress is handled by Zeus and the leaders. We will not leave you out of the op, and we will get you to your element after a crash.
• Gear comes from a restricted arsenal, available in mission at the deployment zones.
• Personal arsenals are not allowed under any circumstances.
• Some client-side mods are allowed in addition to the server mod list.
• In-game abilities are assigned based on the game knowledge you have shown. Your ROLE is the slot you take. Your SKILLS are what you are qualified for: Medic, Combat Lifesaver, Breacher/EOD, Engineer, JFO, ISR, UAV operator, Marksman, Sniper.
• Support such as artillery and CAS takes skill and training to use. Learn to read a map.

Mods

• Client-side mods: only those on the approved list. Ask before adding one.
• Load the current unit preset before op night. Fix mod problems before start, not during the OPORD.
• Unit mods are in development. Don't share dev builds outside the unit without permission.
• Found a bug? Report it with what you were doing and the RPT if you have it.

Communications

Radios are ACRE2:

• Short range: AN/PRC-148.
• Medium range: AN/PRC-152.
• Long range: AN/PRC-117F.

Nets:

• Company net (C2).
• Fires net: CAS, artillery and transport requests.
• Medical net: MIST reports and 9-line medevac requests.
• Engineer net.
• One net per team.

Keep communications discipline at all times while on mission.

Attendance

Answer every op post with yes, no or maybe at least 24 hours before start. That is the one hard rule.

Operation nights are announced on Discord. Training is as needed, and optional unless you are working toward a skill.

• Teams are small. One missing role changes the plan, so early notice matters more than a perfect record.
• Active members attend at least half of the main ops over any 8 weeks. Below that you move to Reserve, and back when your schedule allows.
• Team leaders give 48 hours notice when they can, so the slot can be covered.
• Be on the server and on TeamSpeak 15 minutes before start, mods loaded.
• Attendance is logged in TAC//PAC from the op start and stop.

Leave

Leave needs no approval and no reason. Post your dates and you are covered.

• Need longer? Post a new end date before the old one passes.
• An LOA that runs 14 days past its end date with no word moves you to Reserve.
• Leaders going on LOA name who covers for them.
• Back after 90 days or more: one refresher session on current mods and SOP before taking a fixed slot.
• Leave is for being away. If you are playing weekly somewhere else, move to Reserve or Friend instead.

The Basic Rules

Real Life First

If you cannot make an op or a training, tell us. Having a life is not a problem. Letting us expect you and then not showing up is.

No Drama

This is the catch-all rule. Issues come up from time to time. When leadership has to ask "what have they done now" every time they hear your name, that is a problem.

Our Reputation

The 1st JMSB wants to be known as a fun but serious milsim community. Avoid anything that would reflect badly on the unit.

No Racism or Hate Speech

If you do not understand this or have a problem with it, you will be removed.

Conduct

• No intentional team killing.
• No griefing or harassment.
• No verbal abuse.
• Limit lewd, obscene, vulgar or discriminatory language (except SGTs, who will be graded on their vulgar language utilization).
• No recruiting members away from the 1st JMSB (poaching).
• No cheating, hacking or scamming.
• Do not send links that can harm another user's computer, on Discord or TeamSpeak.
• No spamming.
• No broadcasting music in channel.

For Zeus

• Do not punish players in game as Zeus.
• Do not abuse players.
• Do not abuse your position.
• No selfish, abusive or disruptive behaviour.

For Leaders and Staff

• Do not abuse players.
• Do not abuse your position.
• No selfish, abusive or disruptive behaviour.
• Be honourable.
• Be respectful.
• Remember this is a game.

Usernames

Custom nicknames and callsigns are accepted, but must be exactly the same on TeamSpeak, Discord and in game, and must follow these guidelines:

• No ridiculous combinations of words. Example: "bigbaddaddy".
• No self-promotion of services. Example: "buymycampics.TV".
• Nothing stupid.
• If you use a first initial and last name, put a space after the period. Example: "J. Doe".
• The golden rule: we have to be able to say it without cursing or laughing.

Multi-Clanning

Multi-clanning is allowed, as long as you meet attendance here.

If you disrespect the 1st JMSB, try to poach members, or fail to follow the unit rules, you will be removed under the disciplinary policy.

Holding a leadership slot here and in another Arma unit at the same time needs staff's OK.

Whether something is objectionable is decided by command (the staff). This covers profile names, in-game chat, voice chat and any other public communication.

Privacy and Recording

• Private messages, applications, admin notes and personal details stay private.
• Steam IDs are used for the roster, the wiki and bans. Nothing else.
• No recording private channels without consent.
• Streaming and recording ops: TBD.
• When you leave you can ask staff to remove your player record. Ban records are kept.

Disciplinary Policy

Purpose

This policy sets out the guidelines for member conduct.

Responsibility of Leaders

Leaders are responsible for the conduct of their element's members while in game, and in game only.

Responsibility of Members

Every member of the 1st JMSB is responsible for knowing and following the unit's policies and rules.

Three Strikes

Unless stated otherwise, any breach of the 1st JMSB rules is handled with three strikes.

1. First offence: a verbal warning from your team leader.
2. Second offence: a verbal warning from your team leader and staff, and the warning in writing by private message on Discord.
3. Third offence: removal from the unit, a ban, and removal from the roster.

How Strikes Work

• Attendance is never a strike. It is handled by member status.
• A strike expires after 6 months with no new one.
• Strikes are logged in TAC//PAC admin notes. You can ask staff to see your own.
• Straight to removal, no strikes: racism or hate speech, poaching, cheating, and deliberately harming the server or another member's computer.
• Staff can suspend a member while they look into a serious report.
• Who reported it is not shared.
• Review: one request to the commanding officer within 7 days of a removal. (TBD)

1st JMSB staff reserve the right, at their sole and absolute discretion, to suspend or end your membership and your access to any 1st JMSB systems or services, and the right to final interpretation of these rules.

Skills and Rank

• A skill is granted after a check session with someone who already holds it. Staff then assign it in TAC//PAC.
• A skill unused for 90 days needs a short refresher before you take that slot again.
• Promotion looks at three things: the role you fill, your skills, and whether you show up.
• Awards and ribbons are recorded in TAC//PAC. Anyone can nominate anyone.
• Rank table: TBD.

Leaders and Zeus

• You can become a leader or officer, but not on day one. You need to prove yourself and earn the unit's trust.
• Leadership slots are assigned by staff and reviewed when the holder or the team asks.
• Stepping down from a leadership slot is normal and carries no mark.
• There is no dedicated Zeus slot or special Zeus rank. If you want to build a mission within our guidelines and run it, we can make it happen.

New Players and Training

There is no basic training course. If you are new to the game, show up 30 minutes early and someone will help you get kitted out. The rest you learn on the job.

Leaving and Returning

Leave whenever you want. Tell someone so the slot can be filled.

• Left in good standing and back within 6 months: rank and skills restored, one refresher session.
• Back after 6 months: rejoin as Recruit. Old skills are re-checked, not re-trained.
• Removed under the disciplinary policy: return is staff's decision.

Changes to This SOP

Changes are posted on Discord 7 days before they take effect.