§ 1 General Rules

1.1 Conduct

1.1.1Respectful conduct is mandatory

1.1.2Usurpation of authority will not be tolerated

1.1.3Extremism of any kind is strictly prohibited

1.1.4Content not suitable for minors is prohibited

1.1.5No offensive, insulting or discriminatory names, messages or other content

1.1.6No misogyny or other things that are unpleasant towards women

1.1.7All content directed against persons on the basis of ethnicity, religion, political orientation, sexuality, gender, skin colour, etc. will not be tolerated

1.1.7If a situation that leads to a penalty occurs in RP, in an RP mission or event, it must be clearly communicated that this situation is being handled OOC or IC, or that there will be OOC or IC consequences.

1.1.8Any statements, photos, allusions, etc. that recall the era of the Nazi regime, National Socialism and similar will not be tolerated. For example, the song "Auf der Heide" must not be sung, read out or sent in chats.

1.2 Voice Rules

1.2.1Voice changers are prohibited, except for voice changers used for investigative purposes, authorised by the General/Owner/deputy General.

1.2.2Please suppress TikTok and music (background noise in general) as far as possible

1.2.3Recording conversations is prohibited unless all persons present have expressly consented to the recording. Exempt from this are recordings made solely to report or document a rule violation and used solely for that purpose.

1.2.4If a person is moved between talks, the person must be informed beforehand

1.3 Chat Rules

1.3.1Unnecessary pinging or tagging is prohibited

1.3.2Keep pings to a minimum

1.3.3@here and @everyone pings are only permitted for the General, General Staff and Owner

1.3.4Memes that violate the rules under § 1.1 f. are prohibited

1.3.5Memes may only be posted in a designated chat

1.4 Advertising

1.4.1Advertising for other Discord servers is prohibited

1.4.2Advertising for websites is prohibited

1.4.3Any other kinds of advertising are prohibited (by DM and in every server channel)

1.4.4If the Administration or the General promote something for our server, § 1.4.1–1.4.3 does not apply

1.4.5Permission for any kind of advertising can be obtained from the General

1.5 Miscellaneous

1.5.1If a gray area exists, it must be reported immediately. Exploiting such gray areas, even if reported afterwards, counts as not reported

1.5.2Exploiting gray areas is strictly prohibited

1.5.3Ignorance of the rules does not protect from punishment

1.5.4Exploiting rights and roles is always prohibited and leads to their removal

1.5.5All rules always apply on the entire Discord and on BRM5 servers (all servers (training, mission, event, RP))

1.5.6In the following, the term "General" also includes the General's deputy. Exceptions to this are named explicitly.

1.5.7In the event of a rule change, the rule is valid immediately after it is issued. Situations that began before and to which this rule would be relevant are not affected, and the rule has no effect on them.

1.5.8Self-support is prohibited. Exceptions are possible and must be decided with the Feldjäger leadership and/or the General or deputy General.

1.5.9The Discord account must have existed for at least 2 months before membership on our server is possible. Exceptions must be agreed with the General Staff, which must approve this by a simple majority.

1.6 Complaints and Compliance

1.6.1The Owner is the highest authority for all complaints. Complaints must generally be submitted to the General first. The Owner only decides if a resolution is not possible this way or if special circumstances require it.

1.6.2Members have the right to submit complaints about superiors, existing systems or an imposed penalty. Complaints about systems or regulations must be submitted via the suggestions area. Complaints about individual cases must be submitted via a General ticket.

1.6.3Complaints about systems or regulations are reviewed and discussed in the General Staff. Complaints about superiors or an imposed penalty are first reviewed by the Feldjäger chair. If a further decision is required, the case is handled by the General or the deputy. The General may delegate handling to a suitable person or body.

1.6.4Submitting a complaint does not create any entitlement to a change of the decision or of the facts. Complaints serve solely to review rule violations, procedural errors or inappropriate or unfair decisions.

§ 2 Server System

2.1 Groups

2.1.1 General

2.1.1.1The tasks of the server are divided into individual groups

2.1.1.2The General determines the number of groups and their areas of responsibility. This is done in consultation with the respective group leadership and must be recorded.

2.1.1.3Every group needs a person who leads the group and thereby also represents it in the General Staff.

2.1.1.4Every group needs a deputy from the group or from the General Staff. This person is to be defined in consultation with the General

2.1.1.5The leader of the respective group is responsible for structuring the group and distributing tasks within it.

2.1.1.6The group leader and the General agree on the number of staff working in the group. It can be increased or reduced at any time.

2.1.2 Naming of the Groups

2.1.2.1 Administration Group

2.1.2.1.1 Tasks

2.1.2.1.1.1Managing the points system

2.1.2.1.1.2Managing the servers, channels and bots

2.1.2.1.1.3Support and intervening in emergencies

2.1.2.1.2 Jobs

2.1.2.1.2.1Administration (also in a test or training capacity)

2.1.2.1.2.2Developer (also in a test or training capacity)

2.1.2.2 Operations Group

2.1.2.2.1 Tasks

2.1.2.2.1.1Organising events

2.1.2.2.1.2Maintaining partnerships with other servers

2.1.2.2.1.3Managing trainings, missions and training courses

2.1.2.2.2 Jobs

2.1.2.2.2.1Event leader (also in a test or training capacity)

2.1.2.3 Feldjäger Group

2.1.2.3.1 Tasks

2.1.2.3.1.1Support and enforcing the rules

2.1.2.3.1.2Taking on police duties in RP

2.1.2.3.2 Jobs

2.1.2.3.2.1RP Feldjäger

2.1.2.3.2.2DC Feldjäger

2.1.2.4 RolePlay Group

2.1.2.4.1 Tasks

2.1.2.4.1.1Leading RP

2.1.2.4.1.2Developing RP

2.1.2.4.1.3Managing RGE

2.1.2.4.2 Jobs

2.1.2.4.2.1RP leader (also in a test or training capacity)

2.1.2.4.2.2RP helper

2.1.2.4.2.3RGE builder (also in a test or training capacity)

2.1.2.5 General Group

2.1.2.5.1 Tasks

2.1.2.5.1.1Supporting the General

2.1.2.5.1.2Handling simple minor tasks

2.1.2.5.1.3Managing units, equipment, uniforms and permissions

2.1.2.5.2 Jobs

2.1.2.5.2.1Secretary

2.1.2.5.2.2Marketing and social media

2.1.2.5.2.3RGE builder

2.2 Roles

2.2.1 Server Owner

2.2.1.1The Server Owner generally stays out of everything, but is given insight into every meeting/group that is founded/opened in relation to the server. If this is not the case, the rank of the members involved may be revoked (at the Server Owner's discretion)

2.2.1.2In an extreme emergency, the Server Owner may immediately remove any player's positions.

2.2.1.3An emergency is a situation that significantly endangers the security or stability of the server (e.g. an imminent server outage).

2.2.1.4If a state of emergency occurs, the Server Owner decides alone. However, they may be supported in their decision.

2.2.1.4.1If, for whatever reasons, this joint approach is not possible within a reasonable time and scope, the Server Owner has the authority to decide alone.

2.2.1.5The Server Owner has a veto right over every decision that is made, provided the server is in danger.

2.2.1.6The Server Owner may independently appoint/replace additional positions for periods of up to 5 weeks (transitional government)

2.2.1.7If necessary, the Server Owner may temporarily take over tasks from other persons.

2.2.2 General

2.2.2.1There may only be one General. The General must be a member of a unit.

2.2.2.2In any case, the General has the last and decisive word at all times and is subordinate only to the Server Owner

2.2.2.3The General is elected by the community

2.2.2.4If the General is voted out, they are barred for one election cycle (at least 2 weeks). The same applies to the resignation of a General

2.2.2.5The General may adjust the rules and the server system at any time; ensuring that this does not harm the server is the General's responsibility.

2.2.2.6The General decides everything, at any time, within the reachable body.

2.2.2.7The General and their deputy are obliged to record in writing any major changes with an impact on the server. This is done, for example, through news posts, meeting minutes or comparable announcements.

2.2.2.8The removal of the General is governed by § 2.3.1.

2.2.2.9Deputy General

2.2.2.9.1There can only be one Deputy General. They must come from the General Staff. They must be defined early and, if necessary, be brought up to speed.

2.2.2.9.2The Deputy General has the same rights and duties as the regular General over all authorities that are under them. The General and the Server Owner are thus excluded from this empowerment.

2.2.2.9.3The authorisation as Deputy General is issued by the General in writing and is likewise withdrawn by them in writing

2.2.2.9.3The deputy General is appointed by the current General. If the General is voted out, their deputy also loses their office. Furthermore, the deputy General can be removed from office by the General or the Server Owner.

2.2.3 Administration

2.2.3.1The number of Administration members is determined by the General or their deputy. The Administration chair may request an increase or reduction in positions.

2.2.3.2The Administration is appointed by the General and the chair of the Administration

2.2.3.3The Administration can be voted out by the community or confirmed in office

2.2.3.4If the Administration is classified as inactive by the assessment of the General or the Owner, it can be removed from office immediately

2.2.3.5The Developer function is a branch of the Administration with the right to manage all bots and channels

2.2.4 Developer

2.2.4.1Developers are appointed and managed by the chair of the Administration group in consultation with the General.

2.2.4.2A Developer's rights may be used purely for DEV work and not for detective work or other gathering of information.

2.2.4.3Information found during the work must be kept strictly confidential.

2.2.5 Feldjäger

2.2.5.1They must likewise comply with the rules

2.2.5.2Feldjäger are managed by their own chair

2.2.5.3Feldjäger act as support and mods

2.2.5.4They also serve as military police during RP

2.2.6 RGE Builder

2.2.6.1They must show activity

2.2.6.2The chair of the RolePlay group manages them

2.2.6.3After a new RGE builder applies, the chair of the RolePlay group decides whether this person is accepted.

2.2.7 Chief of Staff

2.2.7.1The Chief of Staff acts as the official link between the Generals and the General Staff.

2.2.7.2The Chief of Staff supports the Generals with organisational and administrative tasks.

2.2.7.3The Chief of Staff promotes structured and respectful cooperation within the General Staff.

2.2.7.4The Chief of Staff advises both the Generals and the General Staff.

2.2.7.5In a leadership context, the Chief of Staff must take a neutral position. They act impartially and serve solely to support and coordinate the leadership parties.

2.2.7.6The Chief of Staff has no authority to issue instructions to the Generals.

2.2.7.7The General Staff remains directly subordinate to the Generals.

2.2.7.8The Chief of Staff acts in the interest of the server leadership and contributes to efficient communication between all leadership levels.

2.2.7.9The Chief of Staff supports the implementation of the Generals' decisions and ensures their coordinated execution.

2.2.7.10The Chief of Staff always acts in the interest of the community and actively works for the well-being and a positive coexistence of all members.

2.2.7.11The Chief of Staff is unaffected by new General elections. Regardless of these, they are appointed by the incumbent General and confirmed in office or replaced by them.

2.2.8 Loss of Roles

2.2.8.1When rejoining the server, there is no right to the old roles

2.2.8.2If someone is wrongfully banned or kicked from the server, there is a right to the old roles

2.2.8.3If someone loses their account through hacks or otherwise, there is also a right to the old roles (proof required)

2.2.8.4After a leave, a request to regain the previously held roles can be submitted to the General.

2.3 Meetings and Elections

2.3.1General elections are held by the Server Owner after they receive complaints about the current General.

2.3.1.1Only the General themselves can be voted on. They appoint staff members and deputies themselves, which rules out any risk of these being voted out due to their decision-making ability.

2.3.1.2Election Procedure

2.3.1.2.1In the initial vote, the General must have received at least 40% of the votes for the removal process to be aborted and the current General thus retained.

2.3.1.2.2If the General receives less than 40% of the votes, they have 7 days to convince the server and thereby change minds.

2.3.1.2.3After this period, voting takes place again, and this time the General must achieve at least 50% of the votes.

2.3.1.3Every election lasts 24 hours. Throughout the entire new election, the General is under strict observation by the Server Owner.

2.3.1.4If the General is voted out, the Deputy General takes over the server leadership in cooperation with the Server Owner.

2.3.1.5Throughout the entire new election, the General retains full decision-making power; nevertheless, every decision must be justified and documented by the General themselves.

2.3.1.6The Server Owner's right, which states that they may remove or replace any position with immediate effect, also applies here in a weakened form. The Server Owner is also entitled to shorten waiting periods and elections or let them lapse.

2.3.2Meetings

2.3.2.1There are the community meeting and the General Staff meeting

2.3.2.2The community meeting is generally held by the General or their deputy, unless by a person authorised by the General. At the meeting, at the least, the community's proposals are debated and voted on, along with updates from all areas of the server leadership (groups + top server leadership)

2.3.2.2.1The community meeting must be held within 4 weeks of the last community meeting. If this is not possible, it is the responsibility of the General and their deputy to find an alternative date within a maximum of 2 weeks after the deadline has passed.

2.3.2.3The General Staff meeting must take place about 1 week before the community meeting. It serves as preparation for the community meeting and as a joint leadership body. The following and their deputies (if any) may attend the General Staff meeting: General, Chair RolePlay, Chair Operations, Chair Feldjäger, Chair Administration, the Server Owner and the Generals' Secretary as a non-voting person.

2.4 Hierarchy

2.4.1 Hierarchy without Activity

2.4.1.1The general order of rank within the leadership, without active departmental activity, is as follows:

• Leadership (Server Owner, General, GeneralLeutnant, GeneralMajor)
• General Staff (chairs of Operations, Administration, Feldjäger and Roleplay)
• Extended General Staff (deputy chairs of Operations, Administration, Feldjäger and Roleplay)
• Staff

2.4.1.2Within the same hierarchy level there is no order of rank. Decisions are made in the respective area of responsibility or by joint agreement.

2.4.2 Hierarchy with RP Activity

2.4.2.1During an active roleplay situation, the following order of rank applies:

• Leadership
• General Staff – Chair Roleplay
• Extended General Staff – Deputy Roleplay
• General Staff of the other departments
• Extended General Staff of the other departments
• Staff

2.4.2.2During an active roleplay situation, the instructions of the roleplay leadership must be followed. This applies regardless of actual membership of another department.

2.4.3 Hierarchy with Operations Activity

2.4.3.1During an active operation or event, the following order of rank applies:

• Leadership
• General Staff – Chair Operations
• Extended General Staff – Deputy Operations
• General Staff of the other departments
• Extended General Staff of the other departments
• Staff

2.4.3.2During an active operation or event, the instructions of the responsible event leadership (e.g. operations personnel or RP leadership) must be followed. This applies regardless of actual membership of another department. For the duration of the event, the active event leadership ranks above the rest of the General Staff. Above the active event leadership, from top to bottom, stand exclusively the General, their deputy, the respective group leader (Chair Operations or Chair RP) and their deputy.

2.4.3.3Members of the leadership are generally authorised to issue instructions to all subordinate hierarchy levels. Members of the General Staff and of the Extended General Staff are generally only authorised to issue instructions within their respective area of responsibility, unless these rules provide otherwise.

2.5 Rights and Duties

2.5.1 General

2.5.1.1In appropriate situations, the General may and must override the respective leader

2.5.1.2If the opinion and conviction of the General and of the group leader are opposed in a critical situation, the General's word counts

2.5.1.2.1Immediately after the situation has been de-escalated, the General is obliged to find a joint solution with the group leader

2.5.1.3The General is obliged to pass on all relevant information appropriately and as quickly as possible

2.5.1.4If the General is unreachable for various reasons, their deputy temporarily takes over their role and thus also their rights and duties as defined in § 2.5.1

2.5.1.4.1In addition, the Deputy General has all rights and duties granted to them under § 2.2.9

2.5.2 Group Leaders

2.5.2.1Group leaders are required to give clear feedback and maintain a constant flow of information

2.5.2.2Group leaders are obliged to pass on all relevant information appropriately to the General or their deputy as quickly as possible

2.5.3 Rules for External Servers

2.5.3.1The Server Owner of all external servers that are subordinate to the Falcon Battalion must be @viper_arctic

2.5.3.2The Feldjäger group and the Administration group must be brought onto the server and equipped with the roles so that they can carry out their tasks under § 2.1.2

2.5.3.3The main user of the server (for example, the unit leader on unit servers) may have all rights

2.5.3.4Further regulations or exceptions can be agreed by contract between the main user and the General or their deputy

2.6 Police Duties

2.6.1 RP Situation

2.6.1.1Naming of persons and groups authorised to intervene

2.6.1.1.1Feldjäger

2.6.1.1.2RP leadership

2.6.1.1.3General Staff

2.6.1.1.4General and their deputy

2.6.1.2Each role should act according to its corresponding competences

2.6.2 Non-RP Situation

2.6.2.1Naming of persons and groups authorised to intervene

2.6.2.1.1Feldjäger under (§ 2.1.2.3.2.2)

2.6.2.1.2General and their deputy

2.6.2.1.3General Staff

2.6.3 Acute Situations

2.6.3.1If the acute situation takes place within RP, all actions must be agreed with the RP leader

2.6.3.2All persons with rights may use them for de-escalation

2.6.3.3Naming of persons and groups authorised to conclusively investigate the situation

2.6.3.3.1Feldjäger under (§ 2.1.2.3.2.2)

2.6.3.3.2General

2.6.3.3.3General Staff

2.6.4 Penalties, Investigations and Attribution of Guilt

2.6.4.1Feldjäger RP

2.6.4.1.1RP Feldjäger may issue orders to leave the premises

2.6.4.1.2RP Feldjäger may order detention

2.6.4.1.3RP Feldjäger may arrest persons

2.6.4.1.4RP Feldjäger may conduct investigations

2.6.4.2Feldjäger DC

2.6.4.2.1Discord Feldjäger may issue orders to leave the premises

2.6.4.2.2Discord Feldjäger may order detention

2.6.4.2.3Discord Feldjäger may arrest persons

2.6.4.2.4Discord Feldjäger may conduct investigations

2.6.4.2.5Discord Feldjäger may issue verbal warnings

2.6.4.2.6Discord Feldjäger may record warnings one and two

2.6.4.2.7Discord Feldjäger may hand out timeouts

2.6.4.2.8Discord Feldjäger may make entries in the penalty register

2.6.4.2.9Any penalty that endangers the server or parts of it must be reported to the General or their deputy.

2.6.4.3General Staff

2.6.4.3.1The General Staff may issue orders to leave the premises

2.6.4.3.2The General Staff may order detention

2.6.4.3.3The General Staff may arrest persons

2.6.4.3.4The General Staff may conduct investigations

2.6.4.3.5The General Staff may issue verbal warnings

2.6.4.3.6The General Staff may record warnings one and two

2.6.4.3.7The General Staff may issue timeouts with a maximum length of twelve hours

2.6.4.3.8The General Staff may make entries in the penalty register

2.6.4.3.9The General Staff may carry out bans and kicks in emergencies

2.6.4.3.10See 2.6.4.2.9

2.6.4.4General and their Deputy

2.6.4.4.1The General may issue orders to leave the premises

2.6.4.4.2The General may order detention

2.6.4.4.3The General may arrest persons

2.6.4.4.4The General may conduct investigations

2.6.4.4.5The General may issue verbal warnings

2.6.4.4.6The General may record warnings one and two

2.6.4.4.7The General may issue timeouts with a maximum length of 24 hours

2.6.4.4.8The General may make entries in the penalty register

2.6.4.4.9The General may carry out bans in emergencies

2.6.4.4.10The General may carry out kicks in situations where the server does not benefit from them

2.7 Units

2.7.1 Unit Leadership

2.7.1.1The unit leadership must announce at least 2 trainings every 2 weeks

2.7.1.1.1It does not matter here whether all trainings are held in one week or not.

2.7.1.1.2If the 2 trainings take place back to back, they count as one training

2.7.1.1.3Each unit leadership member must announce and/or conduct at least 3 trainings within 30 days.

2.7.1.1.3.1During an LOA this obligation is suspended and resumes after the LOA ends.

2.7.1.2The unit leadership must enforce the weapons and dress code

2.7.1.3The unit leadership must ensure discipline and operational readiness in the unit

2.7.1.4There may be 1 × leader, 1 × co-leader (3 × co-leaders in the infantry) and a maximum of 10% unit staff. (Sub-unit leaders excepted)

2.7.1.5STAFF does not receive a Lvl-3 unit leader, but may receive additional rights within the unit

2.7.2 Members

2.7.2.1The first unit is the recruit unit

2.7.2.2The unit may only be changed once every 7 days. Exempt from this is the transfer out of the recruit unit

2.7.2.3Members must comply with the respective weapons and dress code

2.7.2.4If there are problems in the unit or with the unit leadership, one may always contact the Feldjäger or the General, as well as their deputy

2.7.2.5Names

2.7.2.5.1Every server member who holds an AGA may bindingly have only one first name and one surname, which must not be abbreviated.

2.7.2.5.2No titles may be added to names. The exception is the rank abbreviation, which however does not appear in the display names on the main Discord. Designations such as Junior or Senior are also not approved. In addition, noble designations such as "von" are likewise not permitted.

2.7.2.5.3The name must not contain a hidden message.

2.7.2.5.4The name must not correspond to, or even closely resemble, that of a real well-known personality.

2.7.2.5.5The name must not contain numbers.

2.7.2.6The following rules apply to a change of (sub-)unit:

2.7.2.6.1Members must announce a change of (sub-)unit to the responsible (sub-)unit leadership at least one day in advance.

2.7.2.6.2Members of the unit staff must announce a change of (sub-)unit to the responsible unit leadership at least two days in advance.

2.7.2.6.3Members of the unit leadership may only change their (sub-)unit with prior approval from the General. If the General is unavailable or absent, approval can be granted by their deputy.

2.7.4 Unit Rules

2.7.4.1Every unit is entitled to issue supplementary unit-internal rules, provided they do not violate the general rules or other applicable regulations. These rules must be published within the respective unit and are binding for its members.

2.7.4.2Unit-internal rules may neither override nor contradict existing rules. In case of doubt, the general rules always take precedence.

2.7.4.3Particularly relevant rules that make sense across units can be proposed to the General for inclusion in the general rules. After their official inclusion, they apply server-wide and violations are punished under the regular sanction procedures.

2.7.4.4Violations of purely unit-internal rules are handled and disciplined by the respective unit leadership. The Feldjäger or other central bodies only intervene if the general rules were also violated or a corresponding instruction exists.

2.7.5 Unit-Specific Rules

2.7.5.1The protection of the identity of members of the Special Forces Command (KSK) applies exclusively to roleplay. The identity, names, image material or other information that allows conclusions about the in-game identity of a KSK member may only be disclosed or passed on to unauthorised persons with the express consent of the member concerned, the unit leadership or the General Staff.

2.7.5.2Further unit-specific rules must be announced by the respective unit leadership and are binding for all members of the unit.

2.8 Training Courses

2.8.1In principle, anyone may take any training course (prerequisites are filed under the channel Types, category Training Courses)

2.8.2If a training course is unit-related, it may only be run by the respective unit. If a member changes unit, the training course loses its validity and must be completed again.

2.8.3Every training course must be conducted both on the Discord server and on the Blackhawk server. Exempt from this are the RP-AGA and the radio training.

2.8.4Instructors must have held the role for at least 2 weeks and have trained at least 3 players before they may train new instructors.

2.8.4.1An instructor training course requires the presence of a candidate for the instructor role, a training instructor and a trainee. The trainee must still need the relevant training course under the applicable regulations and must not yet have successfully completed it.

2.8.5From rank 20, any training course can be completed. If restrictions exist that affect the full scope of a training course, this requirement does not lapse.

2.8.6If an instructor is without a unit for more than 1 week, all of their instructor permissions can be revoked.

2.8.7Using materials and equipment requires successful completion of the training course intended for it. In addition, only equipment released by the Operations department and for the respective unit may be used.

2.8.8Deliberately disrupting or impairing training courses and trainings is prohibited. The instructions of the responsible instructors must be followed during the session. Violations may be disciplined.

2.9 BRM5 Activities

2.9.1 Trainings

2.9.1.1May be started by unit leaders and regiment staff members, as well as by the General

2.9.1.2At least 4 participants must be present

2.9.1.3It must last at least 30 min

2.9.2 Missions

2.9.2.1May be started by anyone with the Mission Leader role

2.9.2.2At least 4 participants must be present

2.9.2.3Missions must last at least 15 min. Exempt are those that are completed in a shorter time

2.9.2.4Missions may only take place in the designated mission talks of the category "Einsätze" on the main server. Likewise, they may only take place on one of the official in-game servers of the Falcon Battalion, which are labelled "Farm Server X (Max Mustermann)". The channel names must also be visible in the screenshot.

2.9.2.5Nobody may be denied participation in a mission as long as that person does not commit rule violations or extremely disrupt the mission. Consequently, statuses such as "Do not disturb" or "Do not join, private" are prohibited.

2.9.2.6Pings for missions between 23:00 and 16:00 may in principle only be sent as silent pings. A bunker ping may only be sent once per run.

2.9.3 Events

2.9.3.1May primarily be started by Operations. Secondarily, they may also be started by the General, their deputy and the Staff

2.9.3.2At least 7 participants must be present

2.9.3.3It must last at least 1 h

2.9.4 RP Events

2.9.4.1May only be started by the RP group or by a person designated by the RP chair

2.9.4.2At least 6 participants must be present

2.9.4.3It must last at least 1 h

2.9.5 Rules for Activities

2.9.5.1The unit weapons and dress codes must be observed in all activities

2.9.5.2Civilians may not take part

2.9.5.3Recruits who do not have a unit role do not receive points