UOAF Codex - User contributions [en]

Getting Started Guide (Arma 3)

2019-01-17T04:51:30Z

ThePieSpy: /* Mission End/New Mission Selection */

This Getting Started Guide for ArmA 3 provides basic guidance on getting started with [[ArmA 3]] at [[United Operations]]. It covers the proper synchronization to our [[:Category:ArmA_3_Modpack|modpack]] using [http://steamcommunity.com/sharedfiles/filedetails/?id=851438999 Steam Workshop], how to connect to our servers, and the important things you need to know for your first play session at UO as well as further reading.

== Prerequisites ==
Before you start playing [[ArmA 3]] (with APEX DLC) with us you'll need to acquire a few prerequisites: [[Teamspeak 3]] for in-game and out-of-game communication and a [http://forums.unitedoperations.net/ Forum Account], <s>you will also need to link your Teamspeak 3 profile with your forum account</s>. For a walk through on installing and setting up our prerequisites see:
:[[Getting Started at UO]]

== Addon Synchronization - Steam Workshop ==
Before you can successfully connect to our ArmA 3 servers you need to download our [[:Category:ArmA 3 Modpack|modpack]].
If you do not already have any of our mods at all this can take a considerable amount of time as the mods you need to download are considerable in size. If you have played elsewhere with mods before coming to play with us there is a likelyhood you already have some of our mods, in that event we will simply re-use those mods and the download time will be smaller.

'''''Please launch the game at least once normally, through Steam, to ensure that all updates are processed fully. Do this before you continue with this guide or attempt to install any mods, and after all updates to ArmA 3.'''''
=== Required - Modpack Collection ===
Install the Modpack/Collection - [http://steamcommunity.com/sharedfiles/filedetails/?id=851438999 United Operations - Modpack Collection] 
 [[File:steam_a3_modpack_collection.png]]

Confirm that The following addons are selected in the ArmA 3 Launcher. 
Once Subscribed, the following mods should now appear in your ArmA 3 Launcher - Check-mark all of the following mods. 
If these addons are updated, Steam will automatically download these in the background, or when you are connected to Steam.
 
[[File:steam_a3_addons.png]] 

=== Optional - Bypassing BattlEye ===
Due to the development of content in our community, we frequently are running development versions of software. These updates may require BattlEye to be disabled to connect to the server. 
 
If the an update requires BattlEye to be disabled - The Server Channel in Teamspeak will be updated to reflect this requirement. 
 
Normal Server Name - "UnitedOperations.Net - SRV1 - ACE/ACRE2" 
Disabled BattlEye Server Name - "UnitedOperations.Net - SRV1 - BE OFF" 
 
To connect to the servers without BattlEye, select the Battleye Tab in the launcher and uncheck "Enable BattlEye anti-cheat software". 
 
[[File:steam_a3_disable_battleye.png]]

== Connecting to the Server - General Info ==
Server Passwords
In order to connect to our servers, you will need to obtain the Server Password - [http://forums.unitedoperations.net/index.php/page/ArmA3/servers Located Here].

=== Modpack Install - Updates ===
Upon the first install of the modpack and or upon updates to the ACRE2 modification. 

Close Teamspeak 3 
Launch ArmA 3 with the United Operations Moddpack Collection. 
ArmA 3 will then install any ACRE2 Updates to Teamspeak 3. 
 
[[File:a3_acre2_install.png]] 
 
After ACRE2 Updates are installed, you can then reopen Teamspeak 3 and Connect to the server. 

=== Teamspeak 3 - Connect to Server ===
Once you have the passwords from above, Open Teamspeak 3 and select the Connections Menu, then choose Connect.
Enter the following information.
:Server Address: ''ts3.unitedoperations.net''
:Nickname: ''Your Name Here''
:Server Password: ''[http://forums.unitedoperations.net/index.php/page/ArmA3/servers Server Password - Located Here]''
[[File:Ts3_connect.png]]

Feel free to bookmark the server to save this information.

=== ArmA 3 - Connect to Server ===
Once you have the password start ArmA 3, navigate to the Multiplayer server browser, click the tab labeled "Direct Connect" in the tom left-hand corner and enter the following information into the corresponding boxes:
:IP: ''arma3.unitedoperations.net''
:Port: ''2402''
Then click OK. Then enter the [http://forums.unitedoperations.net/index.php/page/ArmA3/servers password].
You will now be connected to the game server.

=== ArmA3 - Saving Favorite Servers ===
One result should appear, save this server as Favorite.
After you have played on the server once, it will appear in your recent servers, and you can favorite the server by enabling the gold star infront of the server name. This will cause the server to appear in the ArmA 3 Launcher.

=== Misc - Help ===
If the event you cannot find our server using the above method please contact a Regular on our Teamspeak for assistance.

== Your First ArmA 3 Session ==

=== Joining the Server ===
The "Primary" or UnitedOperations.Net - SRV1 - ACE/ACRE, is the main ArmA 3 server used for gameplay at United Operations. The server is up 24/7 (aside from occasional technical or administrative issues), and as long as there is room in the mission players are free to join (unless otherwise dictated by a pre-slotted event). For frequent play times please refer to the [[Arma_3_Average_Playtimes|average play times page]]. If you are disconnected while attempting to join, verify your mods are setup correctly according to the guide.

If the server is full, you may wish to join the waiting room channel in Teamspeak until a new mission is started, typically players will inform those in the waiting room that a new mission is starting.

[[File:A3 ts channels.jpg|frameless|918x918px]]

=== Choosing a Slot ===
If the admin has not pushed to the mission to the briefing or in-game, wait to slot until the current mission leader (usually the player Platoon or Company Commander slot) calls for slots to be filled. The current leader may call specific slots or groups they wish filled. In the case of a Team vs Team mission, the server administrator will typically inform each side how many players they are allotted (in order to maintain the mission maker's intended ratio).

For your first game, you should seek a easier role such as Rifleman, Grenadier, or Automatic Rifleman. This will allow you to become accustomed to our style of play and learn without being in a mission-critical role. The leader of a mission has the final say to any slots and who fills them, and will be enforced by the current admin by kicks/bans in necessary. If there is any confusion to what slot you should fill, feel free to ask.

If the game is already underway and you are joining-in-progress (JIP), choose a slot in a group that ideally has a leader and members, avoid slotting into an empty squad if possible.

'''Once slotted, ensure you note the player who is slotted into your groups leadership slot''' (usually a Squad/Section Leader, or Fire-Team Leader). This will be the player immediately in charge of you once in game.
[[File:Brief example.jpg|thumb|An example briefing screen with the plan marked up by the commander.]]

=== Briefing ===
The briefing phase is where each side's leader will decide which course of action they will take, and inform the player's on their side to the plan. If the mission is Team vs Team, there is separate teamspeak channels that each side will utilize in order to brief seperetly before joining the SRV1 channel once briefing is complete.

General talk is allowed between players via teamspeak and ingame chat before the leader is ready to brief, but keep in mind the [[Game Server SOPs|rules]] regarding conduct on the game server still apply. '''Once the leader is ready to brief, talking is not allowed unless the player is directly involved in the briefing (i.e. Squad Leaders, Pilots, etc)'''. This is enforced by the admin, and disruptive or uncooperative players will be kicked/banned.

=== Loading into Mission ===
Once briefing is complete, all players will move back up to the SRV1 teamspeak channel (if briefing multiple teams). Ensure you are in the correct channel, or ACRE will not function once ingame. Ensure that ArmA is not minimized before loading into game, often times tabbing back into ArmA once ingame will fire the player's weapon by accident.

Once in game, stay in the immediate spawn location in order to facilitate organization. Identify the player from the slotting screen who is your immediate leader (either Squad or Fire-Team Leader) and await their orders. Familiarize yourself with the other players in your group, as this is who you will look for if you become separated during gameplay.

If joining-in-progress, you may be able to teleport to your leader via the action menu (default: Scroll Wheel). If transport vehicles are slotted, await that vehicle to return to spawn to pick up players. Do not take vehicles or assets you are not slotted to operate. If unable to regroup with your group leader, find another group of friendlies to either direct you to your group, or temporarily join theirs.

Blatant disregard for leader's orders and pre-movement organization will be met with warnings or possible kick/ban from the admin. Regulars and players are aware of difficulties new players can have, don't be afraid to ask your leader or fellow group members for help.
=== Gameplay ===
Once movement from the initial spawn location has begun, concentrate on staying with your group and listening for orders. Several guides are available in the UOTC Codex section of the wiki where players can learn some of the skills that will be useful on the primary.

Some general etiquette that is helpful to new players includes:

# Use the ACRE volume control (default Tab + Scroll Wheel) to lower your talk volume when contact with enemy is expected. Limit talking to only when necessary to avoid giving away your position.
# Map marking beyond the briefing phase is not allowed on Global and Side channels. If creating marks on the map for your own reference, ensure you are on the Direct or Group channel before making marks.
# Ensure you are not moving in front of other player's lines of fire, and be aware of friendly unit's movements to avoid friendly fire.
# Ask if you are unsure of the current weapon status (Green, Yellow, Red). Ensure if you are "Weapons Yellow" you only engage if fired on first or in immediate danger, to avoid giving away your group's location.

=== Spectator ===
If you are killed, do not re-slot into a different slot in order to spawn again unless specifically directed by the admin or Game Moderator (usually due to mission-start mishaps, bugs, or administrative reasons). Those attempting to circumvent this will be subject to ban.

Most missions will put killed players into a spectator screen where they can view the remaining players in the mission. ACRE should automatically separate dead players from live ones and allow them to talk while the mission continues. Ensure that game server [[Game Server SOPs|rules]] are maintained, aggressive or immature behavior towards other players will result in removal from the server or possible ban.
=== Mission End/New Mission Selection ===
Once the mission is over, the admin will move to the mission selection screen, where players can request new missions at the appropriate player count be played. Mission requests are usually done via in-game chat to avoid players talking over one another. A short post-mission discussion may be allowed by the admin, but the admin may silence discussion in order to facilitate quick selection of the next mission.

It will likely take a few games for you learn the ropes of how we play here at [[United Operations]], keep in mind the server [[Game Server SOPs|rules]] and abide by the behavior expectations in the [[United Operations Charter]]. Please do not hesitate to ask for help or assistance, and have fun.

== Troubleshooting ==
Having issues installing our modpack? [http://forums.unitedoperations.net/index.php/forum/197-technical-support/ Hop on over to our forums] or [https://discord.gg/0WqRco0nennZY05d/ Discord] we'll be happy to help you out.

== Recommended Reading ==
* [http://forums.unitedoperations.net/index.php/page/index.html/_/required-reading/united-operations-charter-r49 United Operations Charter]
* [[Game Server SOPs|Game Server SOP]]
* [http://forums.unitedoperations.net/index.php/topic/7813-ban-formattingtimeframes-sops/#entry174288 Ban Guidelines]
* [https://www.youtube.com/watch?v=Pioba6xJ1Qw Familiarization Video]
* [http://forums.unitedoperations.net/index.php/topic/17220-uo-rules-and-etiquette-qa UO Rules and Etiquette Q&A]

[[Category: Arma 3 Guides]]

Getting Started Guide (Arma 3)

2019-01-01T16:44:18Z

ThePieSpy: /* Gameplay */

This Getting Started Guide for ArmA 3 provides basic guidance on getting started with [[ArmA 3]] at [[United Operations]]. It covers the proper synchronization to our [[:Category:ArmA_3_Modpack|modpack]] using [http://steamcommunity.com/sharedfiles/filedetails/?id=851438999 Steam Workshop], how to connect to our servers, and the important things you need to know for your first play session at UO as well as further reading.

== Prerequisites ==
Before you start playing [[ArmA 3]] (with APEX DLC) with us you'll need to acquire a few prerequisites: [[Teamspeak 3]] for in-game and out-of-game communication and a [http://forums.unitedoperations.net/ Forum Account], <s>you will also need to link your Teamspeak 3 profile with your forum account</s>. For a walk through on installing and setting up our prerequisites see:
:[[Getting Started at UO]]

== Addon Synchronization - Steam Workshop ==
Before you can successfully connect to our ArmA 3 servers you need to download our [[:Category:ArmA 3 Modpack|modpack]].
If you do not already have any of our mods at all this can take a considerable amount of time as the mods you need to download are considerable in size. If you have played elsewhere with mods before coming to play with us there is a likelyhood you already have some of our mods, in that event we will simply re-use those mods and the download time will be smaller.

'''''Please launch the game at least once normally, through Steam, to ensure that all updates are processed fully. Do this before you continue with this guide or attempt to install any mods, and after all updates to ArmA 3.'''''
=== Required - Modpack Collection ===
Install the Modpack/Collection - [http://steamcommunity.com/sharedfiles/filedetails/?id=851438999 United Operations - Modpack Collection] 
 [[File:steam_a3_modpack_collection.png]]

Confirm that The following addons are selected in the ArmA 3 Launcher. 
Once Subscribed, the following mods should now appear in your ArmA 3 Launcher - Check-mark all of the following mods. 
If these addons are updated, Steam will automatically download these in the background, or when you are connected to Steam.
 
[[File:steam_a3_addons.png]] 

=== Optional - Bypassing BattlEye ===
Due to the development of content in our community, we frequently are running development versions of software. These updates may require BattlEye to be disabled to connect to the server. 
 
If the an update requires BattlEye to be disabled - The Server Channel in Teamspeak will be updated to reflect this requirement. 
 
Normal Server Name - "UnitedOperations.Net - SRV1 - ACE/ACRE2" 
Disabled BattlEye Server Name - "UnitedOperations.Net - SRV1 - BE OFF" 
 
To connect to the servers without BattlEye, select the Battleye Tab in the launcher and uncheck "Enable BattlEye anti-cheat software". 
 
[[File:steam_a3_disable_battleye.png]]

== Connecting to the Server - General Info ==
Server Passwords
In order to connect to our servers, you will need to obtain the Server Password - [http://forums.unitedoperations.net/index.php/page/ArmA3/servers Located Here].

=== Modpack Install - Updates ===
Upon the first install of the modpack and or upon updates to the ACRE2 modification. 

Close Teamspeak 3 
Launch ArmA 3 with the United Operations Moddpack Collection. 
ArmA 3 will then install any ACRE2 Updates to Teamspeak 3. 
 
[[File:a3_acre2_install.png]] 
 
After ACRE2 Updates are installed, you can then reopen Teamspeak 3 and Connect to the server. 

=== Teamspeak 3 - Connect to Server ===
Once you have the passwords from above, Open Teamspeak 3 and select the Connections Menu, then choose Connect.
Enter the following information.
:Server Address: ''ts3.unitedoperations.net''
:Nickname: ''Your Name Here''
:Server Password: ''[http://forums.unitedoperations.net/index.php/page/ArmA3/servers Server Password - Located Here]''
[[File:Ts3_connect.png]]

Feel free to bookmark the server to save this information.

=== ArmA 3 - Connect to Server ===
Once you have the password start ArmA 3, navigate to the Multiplayer server browser, click the tab labeled "Direct Connect" in the tom left-hand corner and enter the following information into the corresponding boxes:
:IP: ''arma3.unitedoperations.net''
:Port: ''2402''
Then click OK. Then enter the [http://forums.unitedoperations.net/index.php/page/ArmA3/servers password].
You will now be connected to the game server.

=== ArmA3 - Saving Favorite Servers ===
One result should appear, save this server as Favorite.
After you have played on the server once, it will appear in your recent servers, and you can favorite the server by enabling the gold star infront of the server name. This will cause the server to appear in the ArmA 3 Launcher.

=== Misc - Help ===
If the event you cannot find our server using the above method please contact a Regular on our Teamspeak for assistance.

== Your First ArmA 3 Session ==

=== Joining the Server ===
The "Primary" or UnitedOperations.Net - SRV1 - ACE/ACRE, is the main ArmA 3 server used for gameplay at United Operations. The server is up 24/7 (aside from occasional technical or administrative issues), and as long as there is room in the mission players are free to join (unless otherwise dictated by a pre-slotted event). For frequent play times please refer to the [[Arma_3_Average_Playtimes|average play times page]]. If you are disconnected while attempting to join, verify your mods are setup correctly according to the guide.

If the server is full, you may wish to join the waiting room channel in Teamspeak until a new mission is started, typically players will inform those in the waiting room that a new mission is starting.

[[File:A3 ts channels.jpg|frameless|918x918px]]

=== Choosing a Slot ===
If the admin has not pushed to the mission to the briefing or in-game, wait to slot until the current mission leader (usually the player Platoon or Company Commander slot) calls for slots to be filled. The current leader may call specific slots or groups they wish filled. In the case of a Team vs Team mission, the server administrator will typically inform each side how many players they are allotted (in order to maintain the mission maker's intended ratio).

For your first game, you should seek a easier role such as Rifleman, Grenadier, or Automatic Rifleman. This will allow you to become accustomed to our style of play and learn without being in a mission-critical role. The leader of a mission has the final say to any slots and who fills them, and will be enforced by the current admin by kicks/bans in necessary. If there is any confusion to what slot you should fill, feel free to ask.

If the game is already underway and you are joining-in-progress (JIP), choose a slot in a group that ideally has a leader and members, avoid slotting into an empty squad if possible.

'''Once slotted, ensure you note the player who is slotted into your groups leadership slot''' (usually a Squad/Section Leader, or Fire-Team Leader). This will be the player immediately in charge of you once in game.
[[File:Brief example.jpg|thumb|An example briefing screen with the plan marked up by the commander.]]

=== Briefing ===
The briefing phase is where each side's leader will decide which course of action they will take, and inform the player's on their side to the plan. If the mission is Team vs Team, there is separate teamspeak channels that each side will utilize in order to brief seperetly before joining the SRV1 channel once briefing is complete.

General talk is allowed between players via teamspeak and ingame chat before the leader is ready to brief, but keep in mind the [[Game Server SOPs|rules]] regarding conduct on the game server still apply. '''Once the leader is ready to brief, talking is not allowed unless the player is directly involved in the briefing (i.e. Squad Leaders, Pilots, etc)'''. This is enforced by the admin, and disruptive or uncooperative players will be kicked/banned.

=== Loading into Mission ===
Once briefing is complete, all players will move back up to the SRV1 teamspeak channel (if briefing multiple teams). Ensure you are in the correct channel, or ACRE will not function once ingame. Ensure that ArmA is not minimized before loading into game, often times tabbing back into ArmA once ingame will fire the player's weapon by accident.

Once in game, stay in the immediate spawn location in order to facilitate organization. Identify the player from the slotting screen who is your immediate leader (either Squad or Fire-Team Leader) and await their orders. Familiarize yourself with the other players in your group, as this is who you will look for if you become separated during gameplay.

If joining-in-progress, you may be able to teleport to your leader via the action menu (default: Scroll Wheel). If transport vehicles are slotted, await that vehicle to return to spawn to pick up players. Do not take vehicles or assets you are not slotted to operate. If unable to regroup with your group leader, find another group of friendlies to either direct you to your group, or temporarily join theirs.

Blatant disregard for leader's orders and pre-movement organization will be met with warnings or possible kick/ban from the admin. Regulars and players are aware of difficulties new players can have, don't be afraid to ask your leader or fellow group members for help.
=== Gameplay ===
Once movement from the initial spawn location has begun, concentrate on staying with your group and listening for orders. Several guides are available in the UOTC Codex section of the wiki where players can learn some of the skills that will be useful on the primary.

Some general etiquette that is helpful to new players includes:

# Use the ACRE volume control (default Tab + Scroll Wheel) to lower your talk volume when contact with enemy is expected. Limit talking to only when necessary to avoid giving away your position.
# Map marking beyond the briefing phase is not allowed on Global and Side channels. If creating marks on the map for your own reference, ensure you are on the Direct or Group channel before making marks.
# Ensure you are not moving in front of other player's lines of fire, and be aware of friendly unit's movements to avoid friendly fire.
# Ask if you are unsure of the current weapon status (Green, Yellow, Red). Ensure if you are "Weapons Yellow" you only engage if fired on first or in immediate danger, to avoid giving away your group's location.

=== Spectator ===
If you are killed, do not re-slot into a different slot in order to spawn again unless specifically directed by the admin or Game Moderator (usually due to mission-start mishaps, bugs, or administrative reasons). Those attempting to circumvent this will be subject to ban.

Most missions will put killed players into a spectator screen where they can view the remaining players in the mission. ACRE should automatically separate dead players from live ones and allow them to talk while the mission continues. Ensure that game server [[Game Server SOPs|rules]] are maintained, aggressive or immature behavior towards other players will result in removal from the server or possible ban.
=== Mission End/New Mission Selection ===
Once the mission is over, the admin will move to the mission selection screen, where players can request new missions at the appropriate player count be played. Mission requests are usually done via in-game chat to avoid players talking over one another. A short post-mission discussion may be allowed by the admin, but the admin may silence discussion in order to facilitate quick selection of the next mission.

It will likely take a few games for you learn the ropes of how we play here at [[United Operations]], however, as long as you don't break any of our [[Game Server SOPs|rules]] and abide by the [[United Operations Charter]] you should be fine. Simply let your fireteam leader know you are new and most of the time they will be very happy to help you out.

== Troubleshooting ==
Having issues installing our modpack? [http://forums.unitedoperations.net/index.php/forum/197-technical-support/ Hop on over to our forums] or [https://discord.gg/0WqRco0nennZY05d/ Discord] we'll be happy to help you out.

== Recommended Reading ==
* [http://forums.unitedoperations.net/index.php/page/index.html/_/required-reading/united-operations-charter-r49 United Operations Charter]
* [[Game Server SOPs|Game Server SOP]]
* [http://forums.unitedoperations.net/index.php/topic/7813-ban-formattingtimeframes-sops/#entry174288 Ban Guidelines]
* [https://www.youtube.com/watch?v=Pioba6xJ1Qw Familiarization Video]
* [http://forums.unitedoperations.net/index.php/topic/17220-uo-rules-and-etiquette-qa UO Rules and Etiquette Q&A]

[[Category: Arma 3 Guides]]

Getting Started Guide (Arma 3)

2019-01-01T16:40:08Z

ThePieSpy: /* Your First ArmA 3 Session */

This Getting Started Guide for ArmA 3 provides basic guidance on getting started with [[ArmA 3]] at [[United Operations]]. It covers the proper synchronization to our [[:Category:ArmA_3_Modpack|modpack]] using [http://steamcommunity.com/sharedfiles/filedetails/?id=851438999 Steam Workshop], how to connect to our servers, and the important things you need to know for your first play session at UO as well as further reading.

== Prerequisites ==
Before you start playing [[ArmA 3]] (with APEX DLC) with us you'll need to acquire a few prerequisites: [[Teamspeak 3]] for in-game and out-of-game communication and a [http://forums.unitedoperations.net/ Forum Account], <s>you will also need to link your Teamspeak 3 profile with your forum account</s>. For a walk through on installing and setting up our prerequisites see:
:[[Getting Started at UO]]

== Addon Synchronization - Steam Workshop ==
Before you can successfully connect to our ArmA 3 servers you need to download our [[:Category:ArmA 3 Modpack|modpack]].
If you do not already have any of our mods at all this can take a considerable amount of time as the mods you need to download are considerable in size. If you have played elsewhere with mods before coming to play with us there is a likelyhood you already have some of our mods, in that event we will simply re-use those mods and the download time will be smaller.

'''''Please launch the game at least once normally, through Steam, to ensure that all updates are processed fully. Do this before you continue with this guide or attempt to install any mods, and after all updates to ArmA 3.'''''
=== Required - Modpack Collection ===
Install the Modpack/Collection - [http://steamcommunity.com/sharedfiles/filedetails/?id=851438999 United Operations - Modpack Collection] 
 [[File:steam_a3_modpack_collection.png]]

Confirm that The following addons are selected in the ArmA 3 Launcher. 
Once Subscribed, the following mods should now appear in your ArmA 3 Launcher - Check-mark all of the following mods. 
If these addons are updated, Steam will automatically download these in the background, or when you are connected to Steam.
 
[[File:steam_a3_addons.png]] 

=== Optional - Bypassing BattlEye ===
Due to the development of content in our community, we frequently are running development versions of software. These updates may require BattlEye to be disabled to connect to the server. 
 
If the an update requires BattlEye to be disabled - The Server Channel in Teamspeak will be updated to reflect this requirement. 
 
Normal Server Name - "UnitedOperations.Net - SRV1 - ACE/ACRE2" 
Disabled BattlEye Server Name - "UnitedOperations.Net - SRV1 - BE OFF" 
 
To connect to the servers without BattlEye, select the Battleye Tab in the launcher and uncheck "Enable BattlEye anti-cheat software". 
 
[[File:steam_a3_disable_battleye.png]]

== Connecting to the Server - General Info ==
Server Passwords
In order to connect to our servers, you will need to obtain the Server Password - [http://forums.unitedoperations.net/index.php/page/ArmA3/servers Located Here].

=== Modpack Install - Updates ===
Upon the first install of the modpack and or upon updates to the ACRE2 modification. 

Close Teamspeak 3 
Launch ArmA 3 with the United Operations Moddpack Collection. 
ArmA 3 will then install any ACRE2 Updates to Teamspeak 3. 
 
[[File:a3_acre2_install.png]] 
 
After ACRE2 Updates are installed, you can then reopen Teamspeak 3 and Connect to the server. 

=== Teamspeak 3 - Connect to Server ===
Once you have the passwords from above, Open Teamspeak 3 and select the Connections Menu, then choose Connect.
Enter the following information.
:Server Address: ''ts3.unitedoperations.net''
:Nickname: ''Your Name Here''
:Server Password: ''[http://forums.unitedoperations.net/index.php/page/ArmA3/servers Server Password - Located Here]''
[[File:Ts3_connect.png]]

Feel free to bookmark the server to save this information.

=== ArmA 3 - Connect to Server ===
Once you have the password start ArmA 3, navigate to the Multiplayer server browser, click the tab labeled "Direct Connect" in the tom left-hand corner and enter the following information into the corresponding boxes:
:IP: ''arma3.unitedoperations.net''
:Port: ''2402''
Then click OK. Then enter the [http://forums.unitedoperations.net/index.php/page/ArmA3/servers password].
You will now be connected to the game server.

=== ArmA3 - Saving Favorite Servers ===
One result should appear, save this server as Favorite.
After you have played on the server once, it will appear in your recent servers, and you can favorite the server by enabling the gold star infront of the server name. This will cause the server to appear in the ArmA 3 Launcher.

=== Misc - Help ===
If the event you cannot find our server using the above method please contact a Regular on our Teamspeak for assistance.

== Your First ArmA 3 Session ==

=== Joining the Server ===
The "Primary" or UnitedOperations.Net - SRV1 - ACE/ACRE, is the main ArmA 3 server used for gameplay at United Operations. The server is up 24/7 (aside from occasional technical or administrative issues), and as long as there is room in the mission players are free to join (unless otherwise dictated by a pre-slotted event). For frequent play times please refer to the [[Arma_3_Average_Playtimes|average play times page]]. If you are disconnected while attempting to join, verify your mods are setup correctly according to the guide.

If the server is full, you may wish to join the waiting room channel in Teamspeak until a new mission is started, typically players will inform those in the waiting room that a new mission is starting.

[[File:A3 ts channels.jpg|frameless|918x918px]]

=== Choosing a Slot ===
If the admin has not pushed to the mission to the briefing or in-game, wait to slot until the current mission leader (usually the player Platoon or Company Commander slot) calls for slots to be filled. The current leader may call specific slots or groups they wish filled. In the case of a Team vs Team mission, the server administrator will typically inform each side how many players they are allotted (in order to maintain the mission maker's intended ratio).

For your first game, you should seek a easier role such as Rifleman, Grenadier, or Automatic Rifleman. This will allow you to become accustomed to our style of play and learn without being in a mission-critical role. The leader of a mission has the final say to any slots and who fills them, and will be enforced by the current admin by kicks/bans in necessary. If there is any confusion to what slot you should fill, feel free to ask.

If the game is already underway and you are joining-in-progress (JIP), choose a slot in a group that ideally has a leader and members, avoid slotting into an empty squad if possible.

'''Once slotted, ensure you note the player who is slotted into your groups leadership slot''' (usually a Squad/Section Leader, or Fire-Team Leader). This will be the player immediately in charge of you once in game.
[[File:Brief example.jpg|thumb|An example briefing screen with the plan marked up by the commander.]]

=== Briefing ===
The briefing phase is where each side's leader will decide which course of action they will take, and inform the player's on their side to the plan. If the mission is Team vs Team, there is separate teamspeak channels that each side will utilize in order to brief seperetly before joining the SRV1 channel once briefing is complete.

General talk is allowed between players via teamspeak and ingame chat before the leader is ready to brief, but keep in mind the [[Game Server SOPs|rules]] regarding conduct on the game server still apply. '''Once the leader is ready to brief, talking is not allowed unless the player is directly involved in the briefing (i.e. Squad Leaders, Pilots, etc)'''. This is enforced by the admin, and disruptive or uncooperative players will be kicked/banned.

=== Loading into Mission ===
Once briefing is complete, all players will move back up to the SRV1 teamspeak channel (if briefing multiple teams). Ensure you are in the correct channel, or ACRE will not function once ingame. Ensure that ArmA is not minimized before loading into game, often times tabbing back into ArmA once ingame will fire the player's weapon by accident.

Once in game, stay in the immediate spawn location in order to facilitate organization. Identify the player from the slotting screen who is your immediate leader (either Squad or Fire-Team Leader) and await their orders. Familiarize yourself with the other players in your group, as this is who you will look for if you become separated during gameplay.

If joining-in-progress, you may be able to teleport to your leader via the action menu (default: Scroll Wheel). If transport vehicles are slotted, await that vehicle to return to spawn to pick up players. Do not take vehicles or assets you are not slotted to operate. If unable to regroup with your group leader, find another group of friendlies to either direct you to your group, or temporarily join theirs.

Blatant disregard for leader's orders and pre-movement organization will be met with warnings or possible kick/ban from the admin. Regulars and players are aware of difficulties new players can have, don't be afraid to ask your leader or fellow group members for help.
=== Gameplay ===
Once movement from the initial spawn location has begun, concentrate on staying with your group and listening for orders. Several guides are available in the UOTC Codex section of the wiki where players can learn some of the skills that will be useful on the primary.

Some general etiquette that is helpful to new players includes:

# Use the ACRE volume control (default LAlt + Scroll Wheel) to lower your talk volume when contact with enemy is expected. Limit talking to only when necessary to avoid giving away your position.
# Map marking beyond the briefing phase is not allowed on Global and Side channels. If creating marks on the map for your own reference, ensure you are on the Direct or Group channel before making marks.
# Ensure you are not moving in front of other player's lines of fire, and be aware of friendly unit's movements to avoid friendly fire.
# Ask if you are unsure of the current weapon status (Green, Yellow, Red). Ensure if you are "Weapons Yellow" you only engage if fired on first or in immediate danger, to avoid giving away your group's location.
=== Spectator ===
If you are killed, do not re-slot into a different slot in order to spawn again unless specifically directed by the admin or Game Moderator (usually due to mission-start mishaps, bugs, or administrative reasons). Those attempting to circumvent this will be subject to ban.

Most missions will put killed players into a spectator screen where they can view the remaining players in the mission. ACRE should automatically separate dead players from live ones and allow them to talk while the mission continues. Ensure that game server [[Game Server SOPs|rules]] are maintained, aggressive or immature behavior towards other players will result in removal from the server or possible ban.
=== Mission End/New Mission Selection ===
Once the mission is over, the admin will move to the mission selection screen, where players can request new missions at the appropriate player count be played. Mission requests are usually done via in-game chat to avoid players talking over one another. A short post-mission discussion may be allowed by the admin, but the admin may silence discussion in order to facilitate quick selection of the next mission.

It will likely take a few games for you learn the ropes of how we play here at [[United Operations]], however, as long as you don't break any of our [[Game Server SOPs|rules]] and abide by the [[United Operations Charter]] you should be fine. Simply let your fireteam leader know you are new and most of the time they will be very happy to help you out.

== Troubleshooting ==
Having issues installing our modpack? [http://forums.unitedoperations.net/index.php/forum/197-technical-support/ Hop on over to our forums] or [https://discord.gg/0WqRco0nennZY05d/ Discord] we'll be happy to help you out.

== Recommended Reading ==
* [http://forums.unitedoperations.net/index.php/page/index.html/_/required-reading/united-operations-charter-r49 United Operations Charter]
* [[Game Server SOPs|Game Server SOP]]
* [http://forums.unitedoperations.net/index.php/topic/7813-ban-formattingtimeframes-sops/#entry174288 Ban Guidelines]
* [https://www.youtube.com/watch?v=Pioba6xJ1Qw Familiarization Video]
* [http://forums.unitedoperations.net/index.php/topic/17220-uo-rules-and-etiquette-qa UO Rules and Etiquette Q&A]

[[Category: Arma 3 Guides]]

Getting Started Guide (Arma 3)

2019-01-01T16:32:21Z

ThePieSpy: /* frameless|918x918px */

This Getting Started Guide for ArmA 3 provides basic guidance on getting started with [[ArmA 3]] at [[United Operations]]. It covers the proper synchronization to our [[:Category:ArmA_3_Modpack|modpack]] using [http://steamcommunity.com/sharedfiles/filedetails/?id=851438999 Steam Workshop], how to connect to our servers, and the important things you need to know for your first play session at UO as well as further reading.

== Prerequisites ==
Before you start playing [[ArmA 3]] (with APEX DLC) with us you'll need to acquire a few prerequisites: [[Teamspeak 3]] for in-game and out-of-game communication and a [http://forums.unitedoperations.net/ Forum Account], <s>you will also need to link your Teamspeak 3 profile with your forum account</s>. For a walk through on installing and setting up our prerequisites see:
:[[Getting Started at UO]]

== Addon Synchronization - Steam Workshop ==
Before you can successfully connect to our ArmA 3 servers you need to download our [[:Category:ArmA 3 Modpack|modpack]].
If you do not already have any of our mods at all this can take a considerable amount of time as the mods you need to download are considerable in size. If you have played elsewhere with mods before coming to play with us there is a likelyhood you already have some of our mods, in that event we will simply re-use those mods and the download time will be smaller.

'''''Please launch the game at least once normally, through Steam, to ensure that all updates are processed fully. Do this before you continue with this guide or attempt to install any mods, and after all updates to ArmA 3.'''''
=== Required - Modpack Collection ===
Install the Modpack/Collection - [http://steamcommunity.com/sharedfiles/filedetails/?id=851438999 United Operations - Modpack Collection] 
 [[File:steam_a3_modpack_collection.png]]

Confirm that The following addons are selected in the ArmA 3 Launcher. 
Once Subscribed, the following mods should now appear in your ArmA 3 Launcher - Check-mark all of the following mods. 
If these addons are updated, Steam will automatically download these in the background, or when you are connected to Steam.
 
[[File:steam_a3_addons.png]] 

=== Optional - Bypassing BattlEye ===
Due to the development of content in our community, we frequently are running development versions of software. These updates may require BattlEye to be disabled to connect to the server. 
 
If the an update requires BattlEye to be disabled - The Server Channel in Teamspeak will be updated to reflect this requirement. 
 
Normal Server Name - "UnitedOperations.Net - SRV1 - ACE/ACRE2" 
Disabled BattlEye Server Name - "UnitedOperations.Net - SRV1 - BE OFF" 
 
To connect to the servers without BattlEye, select the Battleye Tab in the launcher and uncheck "Enable BattlEye anti-cheat software". 
 
[[File:steam_a3_disable_battleye.png]]

== Connecting to the Server - General Info ==
Server Passwords
In order to connect to our servers, you will need to obtain the Server Password - [http://forums.unitedoperations.net/index.php/page/ArmA3/servers Located Here].

=== Modpack Install - Updates ===
Upon the first install of the modpack and or upon updates to the ACRE2 modification. 

Close Teamspeak 3 
Launch ArmA 3 with the United Operations Moddpack Collection. 
ArmA 3 will then install any ACRE2 Updates to Teamspeak 3. 
 
[[File:a3_acre2_install.png]] 
 
After ACRE2 Updates are installed, you can then reopen Teamspeak 3 and Connect to the server. 

=== Teamspeak 3 - Connect to Server ===
Once you have the passwords from above, Open Teamspeak 3 and select the Connections Menu, then choose Connect.
Enter the following information.
:Server Address: ''ts3.unitedoperations.net''
:Nickname: ''Your Name Here''
:Server Password: ''[http://forums.unitedoperations.net/index.php/page/ArmA3/servers Server Password - Located Here]''
[[File:Ts3_connect.png]]

Feel free to bookmark the server to save this information.

=== ArmA 3 - Connect to Server ===
Once you have the password start ArmA 3, navigate to the Multiplayer server browser, click the tab labeled "Direct Connect" in the tom left-hand corner and enter the following information into the corresponding boxes:
:IP: ''arma3.unitedoperations.net''
:Port: ''2402''
Then click OK. Then enter the [http://forums.unitedoperations.net/index.php/page/ArmA3/servers password].
You will now be connected to the game server.

=== ArmA3 - Saving Favorite Servers ===
One result should appear, save this server as Favorite.
After you have played on the server once, it will appear in your recent servers, and you can favorite the server by enabling the gold star infront of the server name. This will cause the server to appear in the ArmA 3 Launcher.

=== Misc - Help ===
If the event you cannot find our server using the above method please contact a Regular on our Teamspeak for assistance.

== Your First ArmA 3 Session ==

=== Joining the Server ===
The "Primary" or UnitedOperations.Net - SRV1 - ACE/ACRE, is the main ArmA 3 server used for gameplay at United Operations. The server is up 24/7 (aside from occasional technical or administrative issues), and as long as there is room in the mission players are free to join (unless otherwise dictated by a pre-slotted event). For frequent play times please refer to the [[Arma_3_Average_Playtimes|average play times page]]. If you are disconnected while attempting to join, verify your mods are setup correctly according to the guide. If the server is full, you may wish to join the waiting room channel in Teamspeak until a new mission is started, typically players will inform those in the waiting room that a new mission is starting.

[[File:A3 ts channels.jpg|frameless|918x918px]]

=== Choosing a Slot ===
If the admin has not pushed to the mission to the briefing or in-game, wait to slot until the current mission leader (usually the player Platoon or Company Commander slot) calls for slots to be filled. The current leader may call specific slots or groups they wish filled. In the case of a Team vs Team mission, the server administrator will typically inform each side how many players they are allotted (in order to maintain the mission maker's intended ratio).

For your first game, you should seek a easier role such as Rifleman, Grenadier, or Automatic Rifleman. This will allow you to become accustomed to our style of play and learn without being in a mission-critical role. The leader of a mission has the final say to any slots and who fills them, and will be enforced by the current admin by kicks/bans in necessary. If there is any confusion to what slot you should fill, feel free to ask.

If the game is already underway and you are joining-in-progress (JIP), choose a slot in a group that ideally has a leader and members, avoid slotting into an empty squad if possible.

'''Once slotted, ensure you note the player who is slotted into your groups leadership slot''' (usually a Squad/Section Leader, or Fire-Team Leader). This will be the player immediately in charge of you once in game.
[[File:Brief example.jpg|thumb|An example briefing screen with the plan marked up by the commander.]]

=== Briefing ===
The briefing phase is where each side's leader will decide which course of action they will take, and inform the player's on their side to the plan. If the mission is Team vs Team, there is separate teamspeak channels that each side will utilize in order to brief seperetly before joining the SRV1 channel once briefing is complete.

General talk is allowed between players via teamspeak and ingame chat before the leader is ready to brief, but keep in mind the [[Game Server SOPs|rules]] regarding conduct on the game server still apply. '''Once the leader is ready to brief, talking is not allowed unless the player is directly involved in the briefing (i.e. Squad Leaders, Pilots, etc)'''. This is enforced by the admin, and disruptive or uncooperative players will be kicked/banned.

=== Loading into Mission ===
Once briefing is complete, all players will move back up to the SRV1 teamspeak channel (if briefing multiple teams). Ensure you are in the correct channel, or ACRE will not function once ingame. Ensure that ArmA is not minimized before loading into game, often times tabbing back into ArmA once ingame will fire the player's weapon by accident.

Once in game, stay in the immediate spawn location in order to facilitate organization. Identify the player from the slotting screen who is your immediate leader (either Squad or Fire-Team Leader) and await their orders. Familiarize yourself with the other players in your group, as this is who you will look for if you become separated during gameplay.

If joining-in-progress, you may be able to teleport to your leader via the action menu (default: Scroll Wheel). If transport vehicles are slotted, await that vehicle to return to spawn to pick up players. Do not take vehicles or assets you are not slotted to operate. If unable to regroup with your group leader, find another group of friendlies to either direct you to your group, or temporarily join theirs.

Blatant disregard for leader's orders and pre-movement organization will be met with warnings or possible kick/ban from the admin. Regulars and players are aware of difficulties new players can have, don't be afraid to ask your leader or fellow group members for help.
=== Gameplay ===
Once movement from the initial spawn location has begun, concentrate on staying with your group and listening for orders. Several guides are available in the UOTC Codex section of the wiki where players can learn some of the skills that will be useful on the primary.

Some general etiquette that is helpful to new players includes:

# Use the ACRE volume control (default LAlt + Scroll Wheel) to lower your talk volume when contact with enemy is expected. Limit talking to only when necessary to avoid giving away your position.
# Map marking beyond the briefing phase is not allowed on Global and Side channels. If creating marks on the map for your own reference, ensure you are on the Direct or Group channel before making marks.
# Ensure you are not moving in front of other player's lines of fire, and be aware of friendly unit's movements to avoid friendly fire.
# Ask if you are unsure of the current weapon status (Green, Yellow, Red). Ensure if you are "Weapons Yellow" you only engage if fired on first or in immediate danger, to avoid giving away your group's location.
=== Spectator ===
If you are killed, do not re-slot into a different slot in order to spawn again unless specifically directed by the admin or Game Moderator (usually due to mission-start mishaps, bugs, or administrative reasons). Those attempting to circumvent this will be subject to ban.

Most missions will put killed players into a spectator screen where they can view the remaining players in the mission. ACRE should automatically separate dead players from live ones and allow them to talk while the mission continues. Ensure that game server [[Game Server SOPs|rules]] are maintained, aggressive or immature behavior towards other players will result in removal from the server or possible ban.
=== Mission End/New Mission Selection ===
Once the mission is over, the admin will move to the mission selection screen, where players can request new missions at the appropriate player count be played. Mission requests are usually done via in-game chat to avoid players talking over one another. A short post-mission discussion may be allowed by the admin, but the admin may silence discussion in order to facilitate quick selection of the next mission.

It will likely take a few games for you learn the ropes of how we play here at [[United Operations]], however, as long as you don't break any of our [[Game Server SOPs|rules]] and abide by the [[United Operations Charter]] you should be fine. Simply let your fireteam leader know you are new and most of the time they will be very happy to help you out.

== Troubleshooting ==
Having issues installing our modpack? [http://forums.unitedoperations.net/index.php/forum/197-technical-support/ Hop on over to our forums] or [https://discord.gg/0WqRco0nennZY05d/ Discord] we'll be happy to help you out.

== Recommended Reading ==
* [http://forums.unitedoperations.net/index.php/page/index.html/_/required-reading/united-operations-charter-r49 United Operations Charter]
* [[Game Server SOPs|Game Server SOP]]
* [http://forums.unitedoperations.net/index.php/topic/7813-ban-formattingtimeframes-sops/#entry174288 Ban Guidelines]
* [https://www.youtube.com/watch?v=Pioba6xJ1Qw Familiarization Video]
* [http://forums.unitedoperations.net/index.php/topic/17220-uo-rules-and-etiquette-qa UO Rules and Etiquette Q&A]

[[Category: Arma 3 Guides]]

Getting Started Guide (Arma 3)

2019-01-01T16:32:07Z

ThePieSpy: /* Briefing */

This Getting Started Guide for ArmA 3 provides basic guidance on getting started with [[ArmA 3]] at [[United Operations]]. It covers the proper synchronization to our [[:Category:ArmA_3_Modpack|modpack]] using [http://steamcommunity.com/sharedfiles/filedetails/?id=851438999 Steam Workshop], how to connect to our servers, and the important things you need to know for your first play session at UO as well as further reading.

== Prerequisites ==
Before you start playing [[ArmA 3]] (with APEX DLC) with us you'll need to acquire a few prerequisites: [[Teamspeak 3]] for in-game and out-of-game communication and a [http://forums.unitedoperations.net/ Forum Account], <s>you will also need to link your Teamspeak 3 profile with your forum account</s>. For a walk through on installing and setting up our prerequisites see:
:[[Getting Started at UO]]

== Addon Synchronization - Steam Workshop ==
Before you can successfully connect to our ArmA 3 servers you need to download our [[:Category:ArmA 3 Modpack|modpack]].
If you do not already have any of our mods at all this can take a considerable amount of time as the mods you need to download are considerable in size. If you have played elsewhere with mods before coming to play with us there is a likelyhood you already have some of our mods, in that event we will simply re-use those mods and the download time will be smaller.

'''''Please launch the game at least once normally, through Steam, to ensure that all updates are processed fully. Do this before you continue with this guide or attempt to install any mods, and after all updates to ArmA 3.'''''
=== Required - Modpack Collection ===
Install the Modpack/Collection - [http://steamcommunity.com/sharedfiles/filedetails/?id=851438999 United Operations - Modpack Collection] 
 [[File:steam_a3_modpack_collection.png]]

Confirm that The following addons are selected in the ArmA 3 Launcher. 
Once Subscribed, the following mods should now appear in your ArmA 3 Launcher - Check-mark all of the following mods. 
If these addons are updated, Steam will automatically download these in the background, or when you are connected to Steam.
 
[[File:steam_a3_addons.png]] 

=== Optional - Bypassing BattlEye ===
Due to the development of content in our community, we frequently are running development versions of software. These updates may require BattlEye to be disabled to connect to the server. 
 
If the an update requires BattlEye to be disabled - The Server Channel in Teamspeak will be updated to reflect this requirement. 
 
Normal Server Name - "UnitedOperations.Net - SRV1 - ACE/ACRE2" 
Disabled BattlEye Server Name - "UnitedOperations.Net - SRV1 - BE OFF" 
 
To connect to the servers without BattlEye, select the Battleye Tab in the launcher and uncheck "Enable BattlEye anti-cheat software". 
 
[[File:steam_a3_disable_battleye.png]]

== Connecting to the Server - General Info ==
Server Passwords
In order to connect to our servers, you will need to obtain the Server Password - [http://forums.unitedoperations.net/index.php/page/ArmA3/servers Located Here].

=== Modpack Install - Updates ===
Upon the first install of the modpack and or upon updates to the ACRE2 modification. 

Close Teamspeak 3 
Launch ArmA 3 with the United Operations Moddpack Collection. 
ArmA 3 will then install any ACRE2 Updates to Teamspeak 3. 
 
[[File:a3_acre2_install.png]] 
 
After ACRE2 Updates are installed, you can then reopen Teamspeak 3 and Connect to the server. 

=== Teamspeak 3 - Connect to Server ===
Once you have the passwords from above, Open Teamspeak 3 and select the Connections Menu, then choose Connect.
Enter the following information.
:Server Address: ''ts3.unitedoperations.net''
:Nickname: ''Your Name Here''
:Server Password: ''[http://forums.unitedoperations.net/index.php/page/ArmA3/servers Server Password - Located Here]''
[[File:Ts3_connect.png]]

Feel free to bookmark the server to save this information.

=== ArmA 3 - Connect to Server ===
Once you have the password start ArmA 3, navigate to the Multiplayer server browser, click the tab labeled "Direct Connect" in the tom left-hand corner and enter the following information into the corresponding boxes:
:IP: ''arma3.unitedoperations.net''
:Port: ''2402''
Then click OK. Then enter the [http://forums.unitedoperations.net/index.php/page/ArmA3/servers password].
You will now be connected to the game server.

=== ArmA3 - Saving Favorite Servers ===
One result should appear, save this server as Favorite.
After you have played on the server once, it will appear in your recent servers, and you can favorite the server by enabling the gold star infront of the server name. This will cause the server to appear in the ArmA 3 Launcher.

=== Misc - Help ===
If the event you cannot find our server using the above method please contact a Regular on our Teamspeak for assistance.

== Your First ArmA 3 Session ==

=== Joining the Server ===
The "Primary" or UnitedOperations.Net - SRV1 - ACE/ACRE, is the main ArmA 3 server used for gameplay at United Operations. The server is up 24/7 (aside from occasional technical or administrative issues), and as long as there is room in the mission players are free to join (unless otherwise dictated by a pre-slotted event). For frequent play times please refer to the [[Arma_3_Average_Playtimes|average play times page]]. If you are disconnected while attempting to join, verify your mods are setup correctly according to the guide. If the server is full, you may wish to join the waiting room channel in Teamspeak until a new mission is started, typically players will inform those in the waiting room that a new mission is starting.

=== [[File:A3 ts channels.jpg|frameless|918x918px]] ===

=== Choosing a Slot ===
If the admin has not pushed to the mission to the briefing or in-game, wait to slot until the current mission leader (usually the player Platoon or Company Commander slot) calls for slots to be filled. The current leader may call specific slots or groups they wish filled. In the case of a Team vs Team mission, the server administrator will typically inform each side how many players they are allotted (in order to maintain the mission maker's intended ratio).

For your first game, you should seek a easier role such as Rifleman, Grenadier, or Automatic Rifleman. This will allow you to become accustomed to our style of play and learn without being in a mission-critical role. The leader of a mission has the final say to any slots and who fills them, and will be enforced by the current admin by kicks/bans in necessary. If there is any confusion to what slot you should fill, feel free to ask.

If the game is already underway and you are joining-in-progress (JIP), choose a slot in a group that ideally has a leader and members, avoid slotting into an empty squad if possible.

'''Once slotted, ensure you note the player who is slotted into your groups leadership slot''' (usually a Squad/Section Leader, or Fire-Team Leader). This will be the player immediately in charge of you once in game.
[[File:Brief example.jpg|thumb|An example briefing screen with the plan marked up by the commander.]]

=== Briefing ===
The briefing phase is where each side's leader will decide which course of action they will take, and inform the player's on their side to the plan. If the mission is Team vs Team, there is separate teamspeak channels that each side will utilize in order to brief seperetly before joining the SRV1 channel once briefing is complete.

General talk is allowed between players via teamspeak and ingame chat before the leader is ready to brief, but keep in mind the [[Game Server SOPs|rules]] regarding conduct on the game server still apply. '''Once the leader is ready to brief, talking is not allowed unless the player is directly involved in the briefing (i.e. Squad Leaders, Pilots, etc)'''. This is enforced by the admin, and disruptive or uncooperative players will be kicked/banned.

=== Loading into Mission ===
Once briefing is complete, all players will move back up to the SRV1 teamspeak channel (if briefing multiple teams). Ensure you are in the correct channel, or ACRE will not function once ingame. Ensure that ArmA is not minimized before loading into game, often times tabbing back into ArmA once ingame will fire the player's weapon by accident.

Once in game, stay in the immediate spawn location in order to facilitate organization. Identify the player from the slotting screen who is your immediate leader (either Squad or Fire-Team Leader) and await their orders. Familiarize yourself with the other players in your group, as this is who you will look for if you become separated during gameplay.

If joining-in-progress, you may be able to teleport to your leader via the action menu (default: Scroll Wheel). If transport vehicles are slotted, await that vehicle to return to spawn to pick up players. Do not take vehicles or assets you are not slotted to operate. If unable to regroup with your group leader, find another group of friendlies to either direct you to your group, or temporarily join theirs.

Blatant disregard for leader's orders and pre-movement organization will be met with warnings or possible kick/ban from the admin. Regulars and players are aware of difficulties new players can have, don't be afraid to ask your leader or fellow group members for help.
=== Gameplay ===
Once movement from the initial spawn location has begun, concentrate on staying with your group and listening for orders. Several guides are available in the UOTC Codex section of the wiki where players can learn some of the skills that will be useful on the primary.

Some general etiquette that is helpful to new players includes:

# Use the ACRE volume control (default LAlt + Scroll Wheel) to lower your talk volume when contact with enemy is expected. Limit talking to only when necessary to avoid giving away your position.
# Map marking beyond the briefing phase is not allowed on Global and Side channels. If creating marks on the map for your own reference, ensure you are on the Direct or Group channel before making marks.
# Ensure you are not moving in front of other player's lines of fire, and be aware of friendly unit's movements to avoid friendly fire.
# Ask if you are unsure of the current weapon status (Green, Yellow, Red). Ensure if you are "Weapons Yellow" you only engage if fired on first or in immediate danger, to avoid giving away your group's location.
=== Spectator ===
If you are killed, do not re-slot into a different slot in order to spawn again unless specifically directed by the admin or Game Moderator (usually due to mission-start mishaps, bugs, or administrative reasons). Those attempting to circumvent this will be subject to ban.

Most missions will put killed players into a spectator screen where they can view the remaining players in the mission. ACRE should automatically separate dead players from live ones and allow them to talk while the mission continues. Ensure that game server [[Game Server SOPs|rules]] are maintained, aggressive or immature behavior towards other players will result in removal from the server or possible ban.
=== Mission End/New Mission Selection ===
Once the mission is over, the admin will move to the mission selection screen, where players can request new missions at the appropriate player count be played. Mission requests are usually done via in-game chat to avoid players talking over one another. A short post-mission discussion may be allowed by the admin, but the admin may silence discussion in order to facilitate quick selection of the next mission.

It will likely take a few games for you learn the ropes of how we play here at [[United Operations]], however, as long as you don't break any of our [[Game Server SOPs|rules]] and abide by the [[United Operations Charter]] you should be fine. Simply let your fireteam leader know you are new and most of the time they will be very happy to help you out.

== Troubleshooting ==
Having issues installing our modpack? [http://forums.unitedoperations.net/index.php/forum/197-technical-support/ Hop on over to our forums] or [https://discord.gg/0WqRco0nennZY05d/ Discord] we'll be happy to help you out.

== Recommended Reading ==
* [http://forums.unitedoperations.net/index.php/page/index.html/_/required-reading/united-operations-charter-r49 United Operations Charter]
* [[Game Server SOPs|Game Server SOP]]
* [http://forums.unitedoperations.net/index.php/topic/7813-ban-formattingtimeframes-sops/#entry174288 Ban Guidelines]
* [https://www.youtube.com/watch?v=Pioba6xJ1Qw Familiarization Video]
* [http://forums.unitedoperations.net/index.php/topic/17220-uo-rules-and-etiquette-qa UO Rules and Etiquette Q&A]

[[Category: Arma 3 Guides]]

File:Brief example.jpg

2019-01-01T16:30:28Z

ThePieSpy:

Getting Started Guide (Arma 3)

2019-01-01T16:26:45Z

ThePieSpy: /* Briefing */

This Getting Started Guide for ArmA 3 provides basic guidance on getting started with [[ArmA 3]] at [[United Operations]]. It covers the proper synchronization to our [[:Category:ArmA_3_Modpack|modpack]] using [http://steamcommunity.com/sharedfiles/filedetails/?id=851438999 Steam Workshop], how to connect to our servers, and the important things you need to know for your first play session at UO as well as further reading.

== Prerequisites ==
Before you start playing [[ArmA 3]] (with APEX DLC) with us you'll need to acquire a few prerequisites: [[Teamspeak 3]] for in-game and out-of-game communication and a [http://forums.unitedoperations.net/ Forum Account], <s>you will also need to link your Teamspeak 3 profile with your forum account</s>. For a walk through on installing and setting up our prerequisites see:
:[[Getting Started at UO]]

== Addon Synchronization - Steam Workshop ==
Before you can successfully connect to our ArmA 3 servers you need to download our [[:Category:ArmA 3 Modpack|modpack]].
If you do not already have any of our mods at all this can take a considerable amount of time as the mods you need to download are considerable in size. If you have played elsewhere with mods before coming to play with us there is a likelyhood you already have some of our mods, in that event we will simply re-use those mods and the download time will be smaller.

'''''Please launch the game at least once normally, through Steam, to ensure that all updates are processed fully. Do this before you continue with this guide or attempt to install any mods, and after all updates to ArmA 3.'''''
=== Required - Modpack Collection ===
Install the Modpack/Collection - [http://steamcommunity.com/sharedfiles/filedetails/?id=851438999 United Operations - Modpack Collection] 
 [[File:steam_a3_modpack_collection.png]]

Confirm that The following addons are selected in the ArmA 3 Launcher. 
Once Subscribed, the following mods should now appear in your ArmA 3 Launcher - Check-mark all of the following mods. 
If these addons are updated, Steam will automatically download these in the background, or when you are connected to Steam.
 
[[File:steam_a3_addons.png]] 

=== Optional - Bypassing BattlEye ===
Due to the development of content in our community, we frequently are running development versions of software. These updates may require BattlEye to be disabled to connect to the server. 
 
If the an update requires BattlEye to be disabled - The Server Channel in Teamspeak will be updated to reflect this requirement. 
 
Normal Server Name - "UnitedOperations.Net - SRV1 - ACE/ACRE2" 
Disabled BattlEye Server Name - "UnitedOperations.Net - SRV1 - BE OFF" 
 
To connect to the servers without BattlEye, select the Battleye Tab in the launcher and uncheck "Enable BattlEye anti-cheat software". 
 
[[File:steam_a3_disable_battleye.png]]

== Connecting to the Server - General Info ==
Server Passwords
In order to connect to our servers, you will need to obtain the Server Password - [http://forums.unitedoperations.net/index.php/page/ArmA3/servers Located Here].

=== Modpack Install - Updates ===
Upon the first install of the modpack and or upon updates to the ACRE2 modification. 

Close Teamspeak 3 
Launch ArmA 3 with the United Operations Moddpack Collection. 
ArmA 3 will then install any ACRE2 Updates to Teamspeak 3. 
 
[[File:a3_acre2_install.png]] 
 
After ACRE2 Updates are installed, you can then reopen Teamspeak 3 and Connect to the server. 

=== Teamspeak 3 - Connect to Server ===
Once you have the passwords from above, Open Teamspeak 3 and select the Connections Menu, then choose Connect.
Enter the following information.
:Server Address: ''ts3.unitedoperations.net''
:Nickname: ''Your Name Here''
:Server Password: ''[http://forums.unitedoperations.net/index.php/page/ArmA3/servers Server Password - Located Here]''
[[File:Ts3_connect.png]]

Feel free to bookmark the server to save this information.

=== ArmA 3 - Connect to Server ===
Once you have the password start ArmA 3, navigate to the Multiplayer server browser, click the tab labeled "Direct Connect" in the tom left-hand corner and enter the following information into the corresponding boxes:
:IP: ''arma3.unitedoperations.net''
:Port: ''2402''
Then click OK. Then enter the [http://forums.unitedoperations.net/index.php/page/ArmA3/servers password].
You will now be connected to the game server.

=== ArmA3 - Saving Favorite Servers ===
One result should appear, save this server as Favorite.
After you have played on the server once, it will appear in your recent servers, and you can favorite the server by enabling the gold star infront of the server name. This will cause the server to appear in the ArmA 3 Launcher.

=== Misc - Help ===
If the event you cannot find our server using the above method please contact a Regular on our Teamspeak for assistance.

== Your First ArmA 3 Session ==

=== Joining the Server ===
The "Primary" or UnitedOperations.Net - SRV1 - ACE/ACRE, is the main ArmA 3 server used for gameplay at United Operations. The server is up 24/7 (aside from occasional technical or administrative issues), and as long as there is room in the mission players are free to join (unless otherwise dictated by a pre-slotted event). For frequent play times please refer to the [[Arma_3_Average_Playtimes|average play times page]]. If you are disconnected while attempting to join, verify your mods are setup correctly according to the guide. If the server is full, you may wish to join the waiting room channel in Teamspeak until a new mission is started, typically players will inform those in the waiting room that a new mission is starting.

=== Choosing a Slot ===
If the admin has not pushed to the mission to the briefing or in-game, wait to slot until the current mission leader (usually the player Platoon or Company Commander slot) calls for slots to be filled. The current leader may call specific slots or groups they wish filled. In the case of a Team vs Team mission, the server administrator will typically inform each side how many players they are allotted (in order to maintain the mission maker's intended ratio).

For your first game, you should seek a easier role such as Rifleman, Grenadier, or Automatic Rifleman. This will allow you to become accustomed to our style of play and learn without being in a mission-critical role. The leader of a mission has the final say to any slots and who fills them, and will be enforced by the current admin by kicks/bans in necessary. If there is any confusion to what slot you should fill, feel free to ask.

If the game is already underway and you are joining-in-progress (JIP), choose a slot in a group that ideally has a leader and members, avoid slotting into an empty squad if possible.

'''Once slotted, ensure you note the player who is slotted into your groups leadership slot''' (usually a Squad/Section Leader, or Fire-Team Leader). This will be the player immediately in charge of you once in game.

=== Briefing ===
The briefing phase is where each side's leader will decide which course of action they will take, and inform the player's on their side to the plan. If the mission is Team vs Team, there is separate teamspeak channels that each side will utilize in order to brief seperetly before joining the SRV1 channel once briefing is complete.

General talk is allowed between players via teamspeak and ingame chat before the leader is ready to brief, but keep in mind the [[Game Server SOPs|rules]] regarding conduct on the game server still apply. '''Once the leader is ready to brief, talking is not allowed unless the player is directly involved in the briefing (i.e. Squad Leaders, Pilots, etc)'''. This is enforced by the admin, and disruptive or uncooperative players will be kicked/banned.

[[File:A3 ts channels.jpg|frameless|918x918px]]

=== Loading into Mission ===
Once briefing is complete, all players will move back up to the SRV1 teamspeak channel (if briefing multiple teams). Ensure you are in the correct channel, or ACRE will not function once ingame. Ensure that ArmA is not minimized before loading into game, often times tabbing back into ArmA once ingame will fire the player's weapon by accident.

Once in game, stay in the immediate spawn location in order to facilitate organization. Identify the player from the slotting screen who is your immediate leader (either Squad or Fire-Team Leader) and await their orders. Familiarize yourself with the other players in your group, as this is who you will look for if you become separated during gameplay.

If joining-in-progress, you may be able to teleport to your leader via the action menu (default: Scroll Wheel). If transport vehicles are slotted, await that vehicle to return to spawn to pick up players. Do not take vehicles or assets you are not slotted to operate. If unable to regroup with your group leader, find another group of friendlies to either direct you to your group, or temporarily join theirs.

Blatant disregard for leader's orders and pre-movement organization will be met with warnings or possible kick/ban from the admin. Regulars and players are aware of difficulties new players can have, don't be afraid to ask your leader or fellow group members for help.
=== Gameplay ===
Once movement from the initial spawn location has begun, concentrate on staying with your group and listening for orders. Several guides are available in the UOTC Codex section of the wiki where players can learn some of the skills that will be useful on the primary.

Some general etiquette that is helpful to new players includes:

# Use the ACRE volume control (default LAlt + Scroll Wheel) to lower your talk volume when contact with enemy is expected. Limit talking to only when necessary to avoid giving away your position.
# Map marking beyond the briefing phase is not allowed on Global and Side channels. If creating marks on the map for your own reference, ensure you are on the Direct or Group channel before making marks.
# Ensure you are not moving in front of other player's lines of fire, and be aware of friendly unit's movements to avoid friendly fire.
# Ask if you are unsure of the current weapon status (Green, Yellow, Red). Ensure if you are "Weapons Yellow" you only engage if fired on first or in immediate danger, to avoid giving away your group's location.
=== Spectator ===
If you are killed, do not re-slot into a different slot in order to spawn again unless specifically directed by the admin or Game Moderator (usually due to mission-start mishaps, bugs, or administrative reasons). Those attempting to circumvent this will be subject to ban.

Most missions will put killed players into a spectator screen where they can view the remaining players in the mission. ACRE should automatically separate dead players from live ones and allow them to talk while the mission continues. Ensure that game server [[Game Server SOPs|rules]] are maintained, aggressive or immature behavior towards other players will result in removal from the server or possible ban.
=== Mission End/New Mission Selection ===
Once the mission is over, the admin will move to the mission selection screen, where players can request new missions at the appropriate player count be played. Mission requests are usually done via in-game chat to avoid players talking over one another. A short post-mission discussion may be allowed by the admin, but the admin may silence discussion in order to facilitate quick selection of the next mission.

It will likely take a few games for you learn the ropes of how we play here at [[United Operations]], however, as long as you don't break any of our [[Game Server SOPs|rules]] and abide by the [[United Operations Charter]] you should be fine. Simply let your fireteam leader know you are new and most of the time they will be very happy to help you out.

== Troubleshooting ==
Having issues installing our modpack? [http://forums.unitedoperations.net/index.php/forum/197-technical-support/ Hop on over to our forums] or [https://discord.gg/0WqRco0nennZY05d/ Discord] we'll be happy to help you out.

== Recommended Reading ==
* [http://forums.unitedoperations.net/index.php/page/index.html/_/required-reading/united-operations-charter-r49 United Operations Charter]
* [[Game Server SOPs|Game Server SOP]]
* [http://forums.unitedoperations.net/index.php/topic/7813-ban-formattingtimeframes-sops/#entry174288 Ban Guidelines]
* [https://www.youtube.com/watch?v=Pioba6xJ1Qw Familiarization Video]
* [http://forums.unitedoperations.net/index.php/topic/17220-uo-rules-and-etiquette-qa UO Rules and Etiquette Q&A]

[[Category: Arma 3 Guides]]

File:A3 ts channels.jpg

2019-01-01T16:25:29Z

ThePieSpy:

Getting Started Guide (Arma 3)

2018-12-31T20:12:38Z

ThePieSpy: /* Your First ArmA 3 Session */

This Getting Started Guide for ArmA 3 provides basic guidance on getting started with [[ArmA 3]] at [[United Operations]]. It covers the proper synchronization to our [[:Category:ArmA_3_Modpack|modpack]] using [http://steamcommunity.com/sharedfiles/filedetails/?id=851438999 Steam Workshop], how to connect to our servers, and the important things you need to know for your first play session at UO as well as further reading.

== Prerequisites ==
Before you start playing [[ArmA 3]] (with APEX DLC) with us you'll need to acquire a few prerequisites: [[Teamspeak 3]] for in-game and out-of-game communication and a [http://forums.unitedoperations.net/ Forum Account], <s>you will also need to link your Teamspeak 3 profile with your forum account</s>. For a walk through on installing and setting up our prerequisites see:
:[[Getting Started at UO]]

== Addon Synchronization - Steam Workshop ==
Before you can successfully connect to our ArmA 3 servers you need to download our [[:Category:ArmA 3 Modpack|modpack]].
If you do not already have any of our mods at all this can take a considerable amount of time as the mods you need to download are considerable in size. If you have played elsewhere with mods before coming to play with us there is a likelyhood you already have some of our mods, in that event we will simply re-use those mods and the download time will be smaller.

'''''Please launch the game at least once normally, through Steam, to ensure that all updates are processed fully. Do this before you continue with this guide or attempt to install any mods, and after all updates to ArmA 3.'''''
=== Required - Modpack Collection ===
Install the Modpack/Collection - [http://steamcommunity.com/sharedfiles/filedetails/?id=851438999 United Operations - Modpack Collection] 
 [[File:steam_a3_modpack_collection.png]]

Confirm that The following addons are selected in the ArmA 3 Launcher. 
Once Subscribed, the following mods should now appear in your ArmA 3 Launcher - Check-mark all of the following mods. 
If these addons are updated, Steam will automatically download these in the background, or when you are connected to Steam.
 
[[File:steam_a3_addons.png]] 

=== Optional - Bypassing BattlEye ===
Due to the development of content in our community, we frequently are running development versions of software. These updates may require BattlEye to be disabled to connect to the server. 
 
If the an update requires BattlEye to be disabled - The Server Channel in Teamspeak will be updated to reflect this requirement. 
 
Normal Server Name - "UnitedOperations.Net - SRV1 - ACE/ACRE2" 
Disabled BattlEye Server Name - "UnitedOperations.Net - SRV1 - BE OFF" 
 
To connect to the servers without BattlEye, select the Battleye Tab in the launcher and uncheck "Enable BattlEye anti-cheat software". 
 
[[File:steam_a3_disable_battleye.png]]

== Connecting to the Server - General Info ==
Server Passwords
In order to connect to our servers, you will need to obtain the Server Password - [http://forums.unitedoperations.net/index.php/page/ArmA3/servers Located Here].

=== Modpack Install - Updates ===
Upon the first install of the modpack and or upon updates to the ACRE2 modification. 

Close Teamspeak 3 
Launch ArmA 3 with the United Operations Moddpack Collection. 
ArmA 3 will then install any ACRE2 Updates to Teamspeak 3. 
 
[[File:a3_acre2_install.png]] 
 
After ACRE2 Updates are installed, you can then reopen Teamspeak 3 and Connect to the server. 

=== Teamspeak 3 - Connect to Server ===
Once you have the passwords from above, Open Teamspeak 3 and select the Connections Menu, then choose Connect.
Enter the following information.
:Server Address: ''ts3.unitedoperations.net''
:Nickname: ''Your Name Here''
:Server Password: ''[http://forums.unitedoperations.net/index.php/page/ArmA3/servers Server Password - Located Here]''
[[File:Ts3_connect.png]]

Feel free to bookmark the server to save this information.

=== ArmA 3 - Connect to Server ===
Once you have the password start ArmA 3, navigate to the Multiplayer server browser, click the tab labeled "Direct Connect" in the tom left-hand corner and enter the following information into the corresponding boxes:
:IP: ''arma3.unitedoperations.net''
:Port: ''2402''
Then click OK. Then enter the [http://forums.unitedoperations.net/index.php/page/ArmA3/servers password].
You will now be connected to the game server.

=== ArmA3 - Saving Favorite Servers ===
One result should appear, save this server as Favorite.
After you have played on the server once, it will appear in your recent servers, and you can favorite the server by enabling the gold star infront of the server name. This will cause the server to appear in the ArmA 3 Launcher.

=== Misc - Help ===
If the event you cannot find our server using the above method please contact a Regular on our Teamspeak for assistance.

== Your First ArmA 3 Session ==

=== Joining the Server ===
The "Primary" or UnitedOperations.Net - SRV1 - ACE/ACRE, is the main ArmA 3 server used for gameplay at United Operations. The server is up 24/7 (aside from occasional technical or administrative issues), and as long as there is room in the mission players are free to join (unless otherwise dictated by a pre-slotted event). For frequent play times please refer to the [[Arma_3_Average_Playtimes|average play times page]]. If you are disconnected while attempting to join, verify your mods are setup correctly according to the guide. If the server is full, you may wish to join the waiting room channel in Teamspeak until a new mission is started, typically players will inform those in the waiting room that a new mission is starting.

=== Choosing a Slot ===
If the admin has not pushed to the mission to the briefing or in-game, wait to slot until the current mission leader (usually the player Platoon or Company Commander slot) calls for slots to be filled. The current leader may call specific slots or groups they wish filled. In the case of a Team vs Team mission, the server administrator will typically inform each side how many players they are allotted (in order to maintain the mission maker's intended ratio).

For your first game, you should seek a easier role such as Rifleman, Grenadier, or Automatic Rifleman. This will allow you to become accustomed to our style of play and learn without being in a mission-critical role. The leader of a mission has the final say to any slots and who fills them, and will be enforced by the current admin by kicks/bans in necessary. If there is any confusion to what slot you should fill, feel free to ask.

If the game is already underway and you are joining-in-progress (JIP), choose a slot in a group that ideally has a leader and members, avoid slotting into an empty squad if possible.

'''Once slotted, ensure you note the player who is slotted into your groups leadership slot''' (usually a Squad/Section Leader, or Fire-Team Leader). This will be the player immediately in charge of you once in game.

=== Briefing ===
The briefing phase is where each side's leader will decide which course of action they will take, and inform the player's on their side to the plan. If the mission is Team vs Team, there is separate teamspeak channels that each side will utilize in order to brief seperetly before joining the SRV1 channel once briefing is complete.

General talk is allowed between players via teamspeak and ingame chat before the leader is ready to brief, but keep in mind the [[Game Server SOPs|rules]] regarding conduct on the game server still apply. '''Once the leader is ready to brief, talking is not allowed unless the player is directly involved in the briefing (i.e. Squad Leaders, Pilots, etc)'''. This is enforced by the admin, and disruptive or uncooperative players will be kicked/banned.
=== Loading into Mission ===
Once briefing is complete, all players will move back up to the SRV1 teamspeak channel (if briefing multiple teams). Ensure you are in the correct channel, or ACRE will not function once ingame. Ensure that ArmA is not minimized before loading into game, often times tabbing back into ArmA once ingame will fire the player's weapon by accident.

Once in game, stay in the immediate spawn location in order to facilitate organization. Identify the player from the slotting screen who is your immediate leader (either Squad or Fire-Team Leader) and await their orders. Familiarize yourself with the other players in your group, as this is who you will look for if you become separated during gameplay.

If joining-in-progress, you may be able to teleport to your leader via the action menu (default: Scroll Wheel). If transport vehicles are slotted, await that vehicle to return to spawn to pick up players. Do not take vehicles or assets you are not slotted to operate. If unable to regroup with your group leader, find another group of friendlies to either direct you to your group, or temporarily join theirs.

Blatant disregard for leader's orders and pre-movement organization will be met with warnings or possible kick/ban from the admin. Regulars and players are aware of difficulties new players can have, don't be afraid to ask your leader or fellow group members for help.
=== Gameplay ===
Once movement from the initial spawn location has begun, concentrate on staying with your group and listening for orders. Several guides are available in the UOTC Codex section of the wiki where players can learn some of the skills that will be useful on the primary.

Some general etiquette that is helpful to new players includes:

# Use the ACRE volume control (default LAlt + Scroll Wheel) to lower your talk volume when contact with enemy is expected. Limit talking to only when necessary to avoid giving away your position.
# Map marking beyond the briefing phase is not allowed on Global and Side channels. If creating marks on the map for your own reference, ensure you are on the Direct or Group channel before making marks.
# Ensure you are not moving in front of other player's lines of fire, and be aware of friendly unit's movements to avoid friendly fire.
# Ask if you are unsure of the current weapon status (Green, Yellow, Red). Ensure if you are "Weapons Yellow" you only engage if fired on first or in immediate danger, to avoid giving away your group's location.
=== Spectator ===
If you are killed, do not re-slot into a different slot in order to spawn again unless specifically directed by the admin or Game Moderator (usually due to mission-start mishaps, bugs, or administrative reasons). Those attempting to circumvent this will be subject to ban.

Most missions will put killed players into a spectator screen where they can view the remaining players in the mission. ACRE should automatically separate dead players from live ones and allow them to talk while the mission continues. Ensure that game server [[Game Server SOPs|rules]] are maintained, aggressive or immature behavior towards other players will result in removal from the server or possible ban.
=== Mission End/New Mission Selection ===
Once the mission is over, the admin will move to the mission selection screen, where players can request new missions at the appropriate player count be played. Mission requests are usually done via in-game chat to avoid players talking over one another. A short post-mission discussion may be allowed by the admin, but the admin may silence discussion in order to facilitate quick selection of the next mission.

It will likely take a few games for you learn the ropes of how we play here at [[United Operations]], however, as long as you don't break any of our [[Game Server SOPs|rules]] and abide by the [[United Operations Charter]] you should be fine. Simply let your fireteam leader know you are new and most of the time they will be very happy to help you out.

== Troubleshooting ==
Having issues installing our modpack? [http://forums.unitedoperations.net/index.php/forum/197-technical-support/ Hop on over to our forums] or [https://discord.gg/0WqRco0nennZY05d/ Discord] we'll be happy to help you out.

== Recommended Reading ==
* [http://forums.unitedoperations.net/index.php/page/index.html/_/required-reading/united-operations-charter-r49 United Operations Charter]
* [[Game Server SOPs|Game Server SOP]]
* [http://forums.unitedoperations.net/index.php/topic/7813-ban-formattingtimeframes-sops/#entry174288 Ban Guidelines]
* [https://www.youtube.com/watch?v=Pioba6xJ1Qw Familiarization Video]
* [http://forums.unitedoperations.net/index.php/topic/17220-uo-rules-and-etiquette-qa UO Rules and Etiquette Q&A]

[[Category: Arma 3 Guides]]

Getting Started Guide (Arma 3)

2018-12-31T18:40:00Z

ThePieSpy: /* Your First ArmA 3 Session */

File:Smokescreen.jpg

2018-12-15T16:32:47Z

ThePieSpy:

File:Tank urban.jpg

2018-12-15T05:10:21Z

ThePieSpy:

File:Tank forest.jpg

2018-12-15T05:07:20Z

ThePieSpy:

File:Tank bounding.JPG

2018-12-15T04:44:27Z

ThePieSpy:

File:Hull down tank diagram.png

2018-12-12T23:08:48Z

ThePieSpy:

File:Mbt.jpg

2018-12-12T04:06:28Z

ThePieSpy:

File:Ifv.jpg

2018-12-12T04:01:13Z

ThePieSpy:

File:Apc.jpg

2018-12-12T04:00:34Z

ThePieSpy:

File:Mrap.jpg

2018-12-12T04:00:00Z

ThePieSpy:

File:Tanks prot.jpg

2018-12-12T02:54:57Z

ThePieSpy:

Staff

2018-11-17T05:09:10Z

ThePieSpy: Condensed senior and junior UOTC instructors into just instructors

__NOTITLE__ __NOTOC__

<onlyinclude>{| class="wikitable" style="width: 80%; margin: 1em auto 1em auto;" align="left"

|- style="width: 50%;"
! colspan="1" style="width: 10%;" |
! colspan="1" style="width: 15%;" | [[UOTC|United Operations Training Center]]
! colspan="1" style="width: 15%;" | [[Web Service Office]]
! colspan="1" style="width: 15%;" | [[Mission Making Office]]
! colspan="1" style="width: 15%;" | [[Game Service Office]]
! colspan="1" style="width: 15%;" | [[Public Relations Office]]
! colspan="1" style="width: 15%;" | [[United Operations Air Force]]
|- style="vertical-align: top;" ! scope="row"
! '''Officers'''
|
* Azzwort
* ThePieSpy
|
* Marvin
* Impulse 9
* VPope
|
* Blackhawk
|
* Impulse 9
* VPope
|
* Azzwort
* Impulse 9
* Max (Hammer 5)
* Kingslayer
|
* Darkfiber
* Gusy
|- style="vertical-align: top;" ! scope="row"
! '''Delegates'''
| ''Instructors''
* Kail
* Dezel
* Pax'Jarome
* VPope
* S4dGuyInSn0
* Gusy (UOAF)
* DarkFib3r (UOAF)
* Force_Majeure (UOAF)

* Mixtrate
* Tripshot
* Graham1988
* Pill421
* ratlover232

| ''Application Developer''
* Verox
* Briland
''Forum Moderators''
*j0zh94
*kalohepirate
| ''[[Mission Submission Moderator | Mission Submission Moderators]]''
* Blue
* Darksidesix
* Nathan
* Perfk
* TinfoilHate
''Mission Review Team Leaders''
* N/A
''Mission Review Team - Volunteers''
*Sacher
*SgtDeadly12
| ''Game Moderators - Officers''
*Azzwort
*Blackhawk
*DarkFib3r
*Gusy
*Impulse 9
*Max (Hammer 5)
*Marvin
*VPope
* Kingslayer
''Game Moderators - Regulars''
*Blue
*Perfk
*SgtDeadly
*StarFox64
*James
|
| ''UOAF - Mission Frag Team''
*Abelian - DCS
* Brainling - BMS, DCS
*DarkFib3r - BMS
*Domestos - BMS
*Foxy - BMS, DCS
* Fumes - BMS
*Gusy - BMS
*Nebosja - BMS
*Neuro - BMS
*Nighthawk - BMS, DCS
* Oirien - BMS
*Wh1t3b0y - BMS

''UOAF - Training Team''
* Nebojsa
* Ghostdog
* Wh1t3b0y

</onlyinclude>
|}
<includeonly>
 
</includeonly>
__NOTOC__
__NOEDITSECTION__

Specialized Weapon Systems

2018-11-11T13:58:36Z

ThePieSpy: Reverted edits by James27 (talk) to last revision by ThePieSpy

{{NAV_UOTC_Side}}
{{wip}}
{{ucon}}
'''Disclaimer: '''
* The following document may not necessarily reflect the views and doctrine of the UOTC.

'''Intent Statement and scope:'''
* The intent of this guide is to familiarize players with the functionality of specialized weapon systems, particularly those employed outside the purview of a standard fireteam.
* The scope of this guide is the functionality of these weapon systems, and their common employment within a fighting force.
[[Specialized_Weapon_Systems#meme|''Crew Served Weapon'']]

 

== Crew Served Weapons ==

=== Heavy Machine Guns ===
Heavy Machine guns are machine guns typically above rifle-caliber but below cannon-caliber (12.7mm/.50 cal, 14.5mm). They are often mounted on vehicles or aircraft in addition to being deployed on tripods. When used by infantry they are most likely used in a defensive role due to their weight.

Examples you may find in-game include:
* M2/M2A1 ".50 Cal"
* DShK "Dishk"
* NSV
* Kord
* KPVT

=== Automatic Grenade Launchers ===
Automatic Grenade Launcher are belt-fed grenade launchers typically fired from vehicles or a tripod. They usually have high explosive power than automatic cannons, but lower velocity. The weight of the weapon and its makes man-packing it difficult over long distances.

Examples you may find in-game include:
* Mk-19
* HK GMG
* AGS-30

=== Recoiless-Rifle ===
Recoiless rifles are a hybrid between a cannon and rocket-launcher that can fire larger projectiles than cannons of similar weight, and often have rocket-assisted projectiles that have longer range than most unguided launchers. Can fire both anti-tank and anti-personnel/structure rounds.

Examples you may find in-game include:
* SPG-9

=== Anti-Tank Guided Missiles ===
Anti-Tank Guided Missiles, or ATGMs use some method of post-launch guidance to extend their range, and improve accuracy over unguided launchers. Usually tripod-mounted. They have large warheads designed to destroy even the heavier main battle tanks.

Examples you may find in-game include:
* BGM-71 TOW (SACLOS)
* 9M133 Kornet (SACLOS)
* 9K115-2 Metis-M (SACLOS)
* MILAN (SACLOS)

==<nowiki/>==
overview
===Unguided Launchers===

Examples you may find in-game include:
*
*
*
*
*
 

 

 
==hniper Rifleseader==
overview
===subheader===

Examples you may find in-game include:
*
*
*
*
*

===subheader===
text
Examples you may find in-game include:
*
*
*
===subheader===

text

Examples you may find in-game include:
*L129A1
*
*
*
*
 

{{NAV_UOTC_Side}}
[[Category:UOTC]]

Staff

2018-10-01T05:11:33Z

ThePieSpy:

__NOTITLE__ __NOTOC__

<onlyinclude>{| class="wikitable" style="width: 80%; margin: 1em auto 1em auto;" align="left"

|- style="width: 50%;"
! colspan="1" style="width: 10%;" |
! colspan="1" style="width: 15%;" | [[UOTC|United Operations Training Center]]
! colspan="1" style="width: 15%;" | [[Web Service Office]]
! colspan="1" style="width: 15%;" | [[Mission Making Office]]
! colspan="1" style="width: 15%;" | [[Game Service Office]]
! colspan="1" style="width: 15%;" | [[Public Relations Office]]
! colspan="1" style="width: 15%;" | [[United Operations Air Force]]
|- style="vertical-align: top;" ! scope="row"
! '''Officers'''
|
* Azzwort
* CathFawr
* ThePieSpy
|
* Marvin
* Impulse 9
|
* Blackhawk
|
* Impulse 9
* VPope
|
* Azzwort
* Impulse 9
* Max (Hammer 5)
* Kingslayer
|
* Darkfiber
* Gusy
|- style="vertical-align: top;" ! scope="row"
! '''Delegates'''
| ''Senior Instructors''
* Kail
* Dezel
* Pax'Jarome
* VPope
* S4dGuyInSn0
* Zumorc (advisory role)
* Gusy (UOAF)
* DarkFib3r (UOAF)
* Force_Majeure (UOAF)
''Junior Instructors''
* Mixtrate
* Tripshot
* Graham1988
* Pill421
* ratlover232

| ''Application Developer''
* Verox
* Briland
''Forum Moderators''
*j0zh94
*kalohepirate
| ''[[Mission Submission Moderator | Mission Submission Moderators]]''
* Blue
* Darksidesix
* Nathan
* Perfk
* TinfoilHate
''Mission Review Team Leaders''
* N/A
''Mission Review Team - Volunteers''
*Sacher
*SgtDeadly12
| ''Game Moderators - Officers''
*Azzwort
*Blackhawk
*DarkFib3r
*Gusy
*Impulse 9
*CathFawr
*Max (Hammer 5)
*Marvin
*VPope
* Kingslayer
''Game Moderators - Regulars''
*Blue
*Perfk
*SgtDeadly
*StarFox64
*James
|
| ''UOAF - Mission Frag Team''
*Brainling - BMS, DCS
*DarkFib3r - BMS
*Domestos - BMS
*Foxy - BMS, DCS
*Gusy - BMS
*Nebosja - BMS
*Neuro - BMS
*Nighthawk - BMS, DCS
*Scope - DCS
*Wh1t3b0y - BMS

''UOAF - Training Team''
* Nebojsa
* Ghostdog
* Wh1t3b0y

</onlyinclude>
|}
<includeonly>
 
</includeonly>
__NOTOC__
__NOEDITSECTION__

Staff

2018-10-01T05:10:39Z

ThePieSpy:

__NOTITLE__ __NOTOC__

<onlyinclude>{| class="wikitable" style="width: 80%; margin: 1em auto 1em auto;" align="left"

|- style="width: 50%;"
! colspan="1" style="width: 10%;" |
! colspan="1" style="width: 15%;" | [[UOTC|United Operations Training Center]]
! colspan="1" style="width: 15%;" | [[Web Service Office]]
! colspan="1" style="width: 15%;" | [[Mission Making Office]]
! colspan="1" style="width: 15%;" | [[Game Service Office]]
! colspan="1" style="width: 15%;" | [[Public Relations Office]]
! colspan="1" style="width: 15%;" | [[United Operations Air Force]]
|- style="vertical-align: top;" ! scope="row"
! '''Officers'''
|
* Azzwort
* CathFawr
* ThePieSpy
|
* Marvin
* Impulse 9
|
* Blackhawk
|
* Impulse 9
* VPope
|
* Azzwort
* Impulse 9
* Max (Hammer 5)
* Kingslayer
|
* Darkfiber
* Gusy
|- style="vertical-align: top;" ! scope="row"
! '''Delegates'''
| ''Senior Instructors''
* Kail
* Dezel
* Pax'Jarome
* VPope
* S4dGuyInSn0
* Zumorc (advisory roll)
* Gusy (UOAF)
* DarkFib3r (UOAF)
* Force_Majeure (UOAF)
''Junior Instructors''
* Mixtrate
* Tripshot
* Graham1988
* Pill421
* ratlover232

| ''Application Developer''
* Verox
* Briland
''Forum Moderators''
*j0zh94
*kalohepirate
| ''[[Mission Submission Moderator | Mission Submission Moderators]]''
* Blue
* Darksidesix
* Nathan
* Perfk
* TinfoilHate
''Mission Review Team Leaders''
* N/A
''Mission Review Team - Volunteers''
*Sacher
*SgtDeadly12
| ''Game Moderators - Officers''
*Azzwort
*Blackhawk
*DarkFib3r
*Gusy
*Impulse 9
*CathFawr
*Max (Hammer 5)
*Marvin
*VPope
* Kingslayer
''Game Moderators - Regulars''
*Blue
*Perfk
*SgtDeadly
*StarFox64
*James
|
| ''UOAF - Mission Frag Team''
*Brainling - BMS, DCS
*DarkFib3r - BMS
*Domestos - BMS
*Foxy - BMS, DCS
*Gusy - BMS
*Nebosja - BMS
*Neuro - BMS
*Nighthawk - BMS, DCS
*Scope - DCS
*Wh1t3b0y - BMS

''UOAF - Training Team''
* Nebojsa
* Ghostdog
* Wh1t3b0y

</onlyinclude>
|}
<includeonly>
 
</includeonly>
__NOTOC__
__NOEDITSECTION__

File:M2a2 symbology.jpg

2018-08-18T17:12:42Z

ThePieSpy: ThePieSpy uploaded a new version of File:M2a2 symbology.jpg

File:Machinegun direct.jpg

2018-07-22T17:25:01Z

ThePieSpy:

File:Bad spacing.jpg

2018-07-22T16:47:36Z

ThePieSpy:

File:Flare mark.jpg

2018-07-19T19:32:19Z

ThePieSpy: flare

flare

File:Urban mg.jpg

2018-07-19T18:41:43Z

ThePieSpy:

File:Urban firesup.jpg

2018-07-19T18:12:30Z

ThePieSpy:

File:Forest flank.jpg

2018-07-19T15:42:54Z

ThePieSpy:

File:Sec lead.jpg

2018-07-19T15:07:47Z

ThePieSpy: section leader

section leader

File:Ft bound.jpg

2018-07-16T19:10:13Z

ThePieSpy: ft_bound

ft_bound

File:Ft intro.jpg

2018-07-16T03:18:11Z

ThePieSpy: ft_intro

ft_intro

File:Ft dangerarea.jpg

2018-07-16T01:48:04Z

ThePieSpy: ft_dangerarea

ft_dangerarea

File:Ft stackup.jpg

2018-07-16T01:32:17Z

ThePieSpy: ft_stackup

ft_stackup

File:Fireteam security.jpg

2018-07-15T17:56:03Z

ThePieSpy: ThePieSpy uploaded a new version of File:Fireteam security.jpg

fireteam security

File:Fireteam security.jpg

2018-07-15T17:55:45Z

ThePieSpy: ThePieSpy uploaded a new version of File:Fireteam security.jpg

fireteam security

File:Fireteam security.jpg

2018-07-15T16:17:10Z

ThePieSpy: ThePieSpy uploaded a new version of File:Fireteam security.jpg

fireteam security

File:Fireteam security2.jpg

2018-07-07T00:34:28Z

ThePieSpy: fireteam_security2

fireteam_security2

File:Fireteam security.jpg

2018-07-07T00:13:28Z

ThePieSpy: fireteam security

fireteam security

File:Cas treat.png

2018-07-06T00:51:06Z

ThePieSpy:

File:Cover conceal.jpg

2018-07-06T00:34:08Z

ThePieSpy:

File:Clutter derender.jpg

2018-07-06T00:29:08Z

ThePieSpy: clutter de-render

clutter de-render

File:Usmc squad.jpg

2018-07-05T22:01:26Z

ThePieSpy: usmc squad

usmc squad

File:Vdv squad.jpg

2018-07-05T22:01:04Z

ThePieSpy: vdv squad

vdv squad

Specialized Weapon Systems

2018-07-02T15:52:08Z

ThePieSpy: /* Anti-Tank Guided Missiles */

Specialized Weapon Systems

2018-07-02T15:50:59Z

ThePieSpy: /* Anti-Tank Guided Missiles */

{{NAV_UOTC_Side}}
{{wip}}
{{ucon}}
'''Disclaimer: '''
* The following document may not necessarily reflect the views and doctrine of the UOTC.

'''Intent Statement and scope:'''
* The intent of this guide is to familiarize players with the functionality of specialized weapon systems, particularly those employed outside the purview of a standard fireteam.
* The scope of this guide is the functionality of these weapon systems, and their common employment within a fighting force.
[[Specialized_Weapon_Systems#meme|''Crew Served Weapon'']]

 

== Crew Served Weapons ==

=== Heavy Machine Guns ===
Heavy Machine guns are machine guns typically above rifle-caliber but below cannon-caliber (12.7mm/.50 cal, 14.5mm). They are often mounted on vehicles or aircraft in addition to being deployed on tripods. When used by infantry they are most likely used in a defensive role due to their weight.

Examples you may find in-game include:
* M2/M2A1 ".50 Cal"
* DShK "Dishk"
* NSV
* Kord
* KPVT

=== Automatic Grenade Launchers ===
Automatic Grenade Launcher are belt-fed grenade launchers typically fired from vehicles or a tripod. They usually have high explosive power than automatic cannons, but lower velocity. The weight of the weapon and its makes man-packing it difficult over long distances.

Examples you may find in-game include:
* Mk-19
* HK GMG
* AGS-30

=== Recoiless-Rifle ===
Recoiless rifles are a hybrid between a cannon and rocket-launcher that can fire larger projectiles than cannons of similar weight, and often have rocket-assisted projectiles that have longer range than most unguided launchers. Can fire both anti-tank and anti-personnel/structure rounds.

Examples you may find in-game include:
* SPG-9

=== Anti-Tank Guided Missiles ===
Anti-Tank Guided Missiles, or ATGMs use some method of post-launch guidance to extend their range, and improve accuracy over unguided launchers. Usually tripod-mounted. They have large warheads designed to destroy even the heavier main battle tanks.

Examples you may find in-game include:
* BGM-71 TOW (SACLOS)
* 9M133 Kornet (SACLOS)
* MILAN (SACLOS)

==<nowiki/>==
overview
===Unguided Launchers===

Examples you may find in-game include:
*
*
*
*
*
 

 

 
==hniper Rifleseader==
overview
===subheader===

Examples you may find in-game include:
*
*
*
*
*

===subheader===
text
Examples you may find in-game include:
*
*
*
===subheader===

text

Examples you may find in-game include:
*L129A1
*
*
*
*
 

{{NAV_UOTC_Side}}
[[Category:UOTC]]

File:Arty pic.jpg

2018-06-24T19:51:26Z

ThePieSpy: arty pic

arty pic

File:Bcs setup ace.jpg

2018-06-21T22:14:10Z

ThePieSpy: bcs setup ace

bcs setup ace