Rules and Regulation
Every BIA member has to abide by the following regulations. Violations can lead to permanent removal from this community. Headquarters, meaning the community founders and active managers have the right to judge in a pending case. You may initiate an investigation about a complaint against another member of this community at any time by contacting any member of management.
1: Community Regulations
1.1: Community Language
The official community is English. All communication in official community channels needs to be conducted in English.
1.1: Respect every member of BIA
Treat every member of BIA with respect. Do not insult or verbally abuse members. Friendly banter is allowed.
1.2: Respect BIA hierarchy
Do not argue with your superiors. Do not publicly challenge your superiors or decisions of leadership. Superiors are responsible and possibly liable for their subordinates in specific cases.
1.3: Represent BIA with integrity and professionalism
Professional members are held to a higher standard in abiding by all regulations. These members should always represent the community internally and externally with integrity and professionalism.
1.4: No political, religious or antagonising discussions
Do not discuss political or religious topics. Forbidden are also topics of discussion that extensively antagonise groups or individuals at BIA.
1.5: No doxing
Do not dox community members against their will. Do not reveal or distribute personal information of a member without their consent.
1.6: No spamming or distribution of harmful content
Do not spam in any community channel of communication. Do not distribute harmful content such as pornography, harmful software, phishing links and so forth.
1.7: No promoting of foreign communities
It is not allowed to use BIA as promoting grounds for other units and clans. This also applies to other games and genres that are aligned with our core interests as a community, i.e. ArmA Reforger.
1.9: No promoting of goods and services
It is not allowed to use BIA as promoting grounds for the sales of goods and services.
1.9: Discord terms of service and regulations apply
Do not violate Discord TOS and regulations within our community.
2: Pre-Event Regulations
2.1: Slotting
Members must pick an appropriate slot for their role and position on the BIA website for each event. When in doubt management or the according head of department should be contacted.
2.2: Vacant slots
Any slots that are vacant 10 minutes before the event are free for taking by any qualified member of the community as long as all other rules were respected.
2.3: Knowledge
Be educated about the event, it is mandatory to read the mission makers briefing prior to the event and is part of any professional members duties at BIA.
2.4: Timeliness
Members need to join Teamspeak and our gameserver at least 30 minutes before the beginning of an event. Members cannot attend an event if they arrive late.
2.5: Technical soundness
Professional members are specifically uphold to have their games and their mods in an up to date state to minimalize negative interference with the event.
2.6: Teamspeak
Members need to be undeafened 10 minutes before the start of the event. All talking must stop at this point as the mission maker and commander briefings will be held.
2.7: Attendence
Each members presence on our Servers is automatically registered and will be evaluated. Professional members need to attend at least 75% of monthly events to be eligbile for compensation. Disconnecting from our servers early before the event has conlcuded will also be registered and will lead to loss of attendence for the particular event. This also applies to members being AFK for a prolonged period of time.
3: Event Regulations
3.1: Enemy equipment
Do not take or use enemy equipment. This includes items such as uniforms and radios. This rule also extends to enemy vehicles.
3.2: Special rules
The mission maker reserves the right to enact special rules for his missions that have to be respected. The mission maker cannot change any other existing regulation in that manner.
3.3: Removal of players
The mission maker reserves the right to remove players from his mission for perceived intend of sabotaging his mission. This includes the violation of previously stated 'special rules'. His decision may be contested through a complaint after the event has concluded.
3.4: No lonewolfing
Do not intentionally lonewolf. Do not intentionally leave your element or position of responsibility.
3.5: Communication
Do not communicate through any other channel than Teamspeak during an event.
3.6: Chat
Do not use the in game chat. It is reserved for admin, commander and mission maker messages. This also applies to the event of a member experiencing technical problems as these should be directed towards the correct Discord channel.
3.7: OPFOR
A given member may only play once per month as part of OPFOR.
3.8: OPFOR ethos
All OPFOR members must respect their primary task and raison detre at all times.
3.9: Going AFK
Every professional player required to notify the next level of command verbally about going AFK and about his return. Sometimes it may not be possible to verbally inform the correct person when the player has to go. Therefore it is also allowed to inform the according person, including the head of their respective department, through DMs in Discord or through pinging them on Teamspeak. This should also be done when going AFK and when returning.
4: Role mission statements
4.1: Department Members
All department members are professional members that are compensated for being proficient in executing specific tasks during our events. Their duties also extend to putting the interest of the community as a whole over their personal preferences and desires whenever the two are in conflict.
4.2: Leaders
Leaders must organise and lead all men under their command in a professional and serious manner. Furthermore all leaders must ensure that the men under their command do not violate any of the regulations during an event that are within the powers of the leader to uphold. Large infractions are to be reported to management.
4.3: Commanders
Commanders must organise and lead all elements under their command in a professional and serious manner. Their plan of battle must be coordinated with the mission structure and all available information in mind. Missions are not individual challenges to the respective commander that are to be "gamed".
4.4: OPFOR
Members of OPFOR are used to enhance the experience of the main player force by providing real human opponents. OPFOR players carry a lot of responsibility as they can make or break an event. Events are not to be taken as a PvP challenge by any member of OPFOR.
5: DCS Regulations
5.1: Professional pilots
All squadron pilots are professional members that are compensated for being proficient in executing their tasks during our DCS events. They are to respect their superiors and all other fellow pilots. Their duties also extend to putting the interest of the community as a whole over their personal preferences and desires whenever the two are in conflict.
5.2: Department slots
The DCS squadron is limited to 16 professional pilots, with no new members permitted until a position becomes available. Each pilot is continually assessed by their superiors and may be dismissed from the squadron due to inactivity or subpar performance.
5.3: Pilot rank
Pilot candidates must complete 6 training flights to qualify for their wings and advance to the rank of pilot. Only then are they eligible to receive monetary compensation.
5.4: Attendance
Pilots must attend at least 80% of all monthly events and training sessions to qualify for monetary compensation. Trainings and events are held every Wednesday at 19:00 GMT.
5.5: Hardware and software requirements
All department members, regardless of rank, must own the F-15C module and a joystick. As the DCS department evolves, new modules and terrains will be added, with all associated costs being covered by BIA HQ.