Campaign 3 Playtest: Difference between revisions

From Endurance Coalition
Jump to navigation Jump to search
← Older edit
VisualWikitext
No edit summary
reword
 
(21 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Construction}}
The '''Campaign 3 Playtest''' (26 March 2025 {{Emdash}} 9 April 2025) was an informal campaign designed to determine the efficacy of a massive rewrite of the war game rules from version 3 to version 4. The campaign was abandoned by Fleff due to the workload required on his end to resolve orders every round. Additionally, the Endurance Coalition server was fixed during this campaign, which made the Arma III server accessible again. As a result, interest in Arma III soon dwarfed that of the war game for Fleff and some participants.
 
The '''Campaign 3 Playtest''' (start 26 March 2025) is an informal campaign designed to determine the efficacy of a massive rewrite of the war game rules from version 3 to version 4.


{{Infobox military conflict
{{Infobox military conflict
Line 9: Line 7:
| place            = Planet Baolo, Ghoveo Island Chain
| place            = Planet Baolo, Ghoveo Island Chain
| conflict          =  
| conflict          =  
| status            = [[File:OOUI Talk icon - Working.svg|18px|link=]] '''Ongoing'''
| status            = [[File:Antu waiting.svg|18px|link=]] Abandoned
| combatants_header = Factions
| combatants_header = Factions
| combatant1        = {{Br separated entries
| combatant1        = {{Br separated entries
Line 33: Line 31:
|2 strike aircraft
|2 strike aircraft
|2 submarines}}
|2 submarines}}
| strength2        = To be determined
| strength2        = {{Br separated entries
|5 hydrofoil flotillas }}
<!-- Causalities should only include entire units. Individual FS being damaged but unit remains alive does not count! -->| casualties1      = {{Br separated entries
<!-- Causalities should only include entire units. Individual FS being damaged but unit remains alive does not count! -->| casualties1      = {{Br separated entries
|N/A}}
|{{Br separated entries
|N/A }}}}
| casualties2      = {{Br separated entries
| casualties2      = {{Br separated entries
|N/A}}
|{{Br separated entries
|3 hydrofoil flotillas }}}}
}}
}}


Line 52: Line 53:
Initial deployment was executed on 26 March.
Initial deployment was executed on 26 March.


== Element makeup ==
<!-- == Element makeup ==
{{Ambox|text=Unit and weapon information are not updated automatically; it's done manually on a semi-regular schedule. Editors are '''strongly encouraged''' to fix any issues spotted. '''Critical game decisions should be double checked against the spreadsheet'''.}}See footnotes for more information. Footnotes in the column headers explains how to read the relevant cells. Any number in the FS/HC, Armor, Speed, or View columns that is bolded and underlined (e.g '''<u>hello</u>''') means that the value has been modified by something the unit has (usually an upgrade).
{{Ambox|text=Unit and weapon information are not updated automatically; it's done manually on a semi-regular schedule. Editors are '''strongly encouraged''' to fix any issues spotted. '''Critical game decisions should be double checked against the spreadsheet'''.}}See footnotes for more information. Footnotes in the column headers explains how to read the relevant cells. Anything '''<u>bolded and underlined</u>''' means the value/keyword/command has been modified from what the base unit/refit is by something.


=== BBM_Ping ===
=== BBM_Ping ===
==== Unit Information ====
{| class="wikitable"
{| class="wikitable"
|+Unit Information
|+Unit Information
Line 153: Line 152:
* C-LandAircraft
* C-LandAircraft
|}
|}
==== Weapon Information ====
{| class="wikitable"
{| class="wikitable"
|+Weapon Information
|+Weapon Information
Line 192: Line 189:
|D4 / AP0 / RNG2 / A / CST1
|D4 / AP0 / RNG2 / A / CST1
|N/A
|N/A
|}
==== Relevant Keywords ====
{| class="wikitable"
|+Relevant Keywords
!Keyword
!Effect
|-
|Cargo-H X
|This unit may carry up to X of Supply, and/or non-naval units. Units may not be carrying their own cargo while embarked to avoid nesting dolls.
|-
|Deck Crew
|Automatically spends your munitions, if you have more than 2, on rearming and repairing units you're carrying costing 1 for repair and 1 for rearm of each unit. Units may not disembark the same turn they are repaired. Rearm is prioritized over repair.
|-
|Headquarters
|''This keyword has no content.''
|-
|Orbital
|This unit may start the game in orbit with limited functionality until they so choose to descend to an available landing zone, often anywhere on the map. Units with the Orbital tag may drop in with other units inside their cargo.
|-
|Well Dock
|This units Cargo-H keyword may also carry, load, and deploy Landing Craft Base Class units.
|-
|Emitter
|This unit emits radiation with a radar and thus may be targeted by anti-radiation (ARAD) weaponry.
|-
|Runway-HELO
|This runway may land only helicopter type units. Landed units are moved into cargo. There must be enough internal space for the occupants when landing.
|-
|Sonar
|When not moving apply a -1 modifier to naval stealth rolls in your sea view range.
|-
|WPN Priority
|This unit may define a primary weapon other than weapon 1 to be used before other weapons. Priority X or 0 will make the unit hold fire unless they are fired upon.
|-
|Bail Out!
|This unit, when killed, makes a D6 roll modified by circumstances of their death. On a 3+ the unit lives as a Regular Class 'Vehicle Crew' unit. On a 1-2 the unit is killed. Units that survive may obtain new vehicles for 1 Supply Crate.
|-
|FW-L (Fixed-Wing Light)
|Hold actions reduce attack rolls by 1 but orders with movement must go minimum 1 grid. This unit may only safely land on Runway-L and Runway-H. Cannot be rearmed or repaired while airborne. Takeoffs are performed at half speed.
|-
|Jump Gear-Orbital
|This unit is capable of performing orbital drops from Naval units still in orbit, cargo compartments may only have supply inside on drop.
|-
|Auto
|This weapon automatically deploys depending on it's role and circumstances. Auto deployed weapons do not consume your one attack for the turn.
|-
|CIWS (Close In Weapon System)
|This weapon can intercept incoming ordinance in its vicinity. A D6 is rolled, on a 1-2 it fails, a 2-4 reduces incoming damage by 2, on a 5-6 no damage is taken.
|-
|IF (Indirect Fire)
|This weapon is used indirectly ignoring line of sight.
|-
|Precise
|This weapon is fired on sub-grids instead of full grids.
|}
|}


Line 802: Line 744:
|
|
* Active Homing
* Active Homing
|}
|}-->
== Campaign chronology ==
== Campaign chronology ==


=== Round 1 ===
=== Round 1 ===
: [[File:OOUI Talk icon - Working.svg|18px|link=]] ''Orders opened 26 March. Awaiting resolution scheduled for 30 March.''
: [[File:Artículo bueno.svg|18px|link=]] ''Orders opened 26 March. Orders resolved 31 March.''
[[File:Playtest3 round1 battlemap.jpg|none|thumb|The battle map provided by command at the conclusion of round 1.]]
A combined force of air and sea {{Emdash}} comprised of units from SierraKomodo's, Comrade's, and Sticky's forces {{Emdash}} head towards the north east. They quickly engage three hydrofoil flotillas which are immediately destroyed on contact. Then, to the western perimeter of the island of ''Kula'', two more hydrofoil flotillas are seen heading south towards a grid with one of SierraKomodo's nuclear attack submarines. Nothing else of note occurs this round.
 
BBM_Ping instructs Sirdog's air units to continue heading east towards the air field on ''Sopau''. Sticky is instructed to ensure the patrol boats spotted off the western perimeter of ''Kula'' cannot threaten the rear of the carrier, but otherwise, Sticky's forces should maintain general direction with the fleet.
 
=== Round 2 ===
: [[File:Artículo bueno.svg|18px|link=]] ''Orders opened 31 March. Orders resolved 3 April.''
[[File:Playtest3 round2 battlemap.jpg|none|thumb|The battle map provided by command at the conclusion of round 2.]]
The battle for the ''Tabar Straight'' begins proper. The chunk of Sticky's battalion engage multiple destroyers, a cruiser and a battle cruiser right on the straight, with both sides getting direct hits on one another. As a stroke of bad luck, one of SirreaKomodo's submarines makes direct contact with an OPFOR submarine in YR-76, resulting in it being targeted by both destroyers, taking damage. Further to the north, a battleship under Sticky's direct command engages a battle cruiser at the ''Iron Bottom Sound'' with both units hitting the other. Even further north, SierraKomodo's strategic reconnaissance aircraft spots yet another destroyer and battle cruiser at the mouth between the islands of ''Karu'' and ''Ghoveo''.
 
To the west, a destroyer under SierraKomodo's command that was sent to the west of ''Kula'' at BBM_Ping's orders receives fire from the two hydrofoil flotillas spotted in the previous round, though they fail to meet their target. SierraKomodo's previously unspotted submarine in grid YL-76 engages one of the flotillas, failing to get a hit.
 
Sirdog's units make contact with the airfield on ''Sopau'' and, after getting the greenlight from BBM_Ping, begins bombing it, managing to do some damage. Sirdog's interceptor recieves contact from an OPFOR multi-role fighter and gets hit, with the interceptor responding and missing.


== Footnotes ==
Nothing else of note occurs this round. Surprisingly, no units in the operational area were destroyed.
{{Reflist}}
[[Category:Campaigns]]
[[Category:Campaigns]]

Latest revision as of 19:01, 9 April 2025

The Campaign 3 Playtest (26 March 2025 — 9 April 2025) was an informal campaign designed to determine the efficacy of a massive rewrite of the war game rules from version 3 to version 4. The campaign was abandoned by Fleff due to the workload required on his end to resolve orders every round. Additionally, the Endurance Coalition server was fixed during this campaign, which made the Arma III server accessible again. As a result, interest in Arma III soon dwarfed that of the war game for Fleff and some participants.

Campaign 3 Playtest

Photograph of a playtest of Crysis (2007) in Leipzig, Sachsen, Deutschland.
Location
Planet Baolo, Ghoveo Island Chain
Status Abandoned
Factions
BBM_Ping
Sticky
Sirdog
SierraKomodo
Comrade		 OPFOR
Strength
2 battlecruisers
1 battleship
1 bomber
1 cargo tender
2 cruisers
3 destroyers
1 fleet carrier
1 interceptor
1 multi-role fighter
1 sea warfare helicopter
1 stealth destroyer
1 strategic reconnaissance aircraft
2 strike aircraft
2 submarines		 5 hydrofoil flotillas
Casualties and losses
N/A 3 hydrofoil flotillas

Background

Map provided by command on 25 February 2025 of the Ghoveo Island Chain with markings of the deployment zone and the Tabar Straight.

The regiment, commanded by BBM_Ping, was advised that he would land to the southwest of the Ghoveo Island Chain. He was then ordered to secure the general area around the Tabar Straight for further operations in the area.

Pre-deployment planning

Map with writings by BBM_Ping of his general plan of action once deployment was underway.

The regiment was comprised of 2 battalions led by Sticky and Sirdog. After a meeting held on 3 March, it was determined that SierraKomodo and Comrade would fall underneath Sticky's command. In contrast, Sirdog was a single element by himself. The fleet makeup decided by BBM_Ping was that he would comprise the fleet carrier, Sirdog would be air operations, Sticky would be a screening fleet, Comrade would be a surface action group, and SierraKomodo would be reconnaissance.

BBM_Ping sent out a general order that the specifics of fleet composition, to be influenced by the aforementioned planning, was due on 9 March. After this was completed and approved by him, BBM_Ping confirmed to command that his regiment was ready to deploy.

Initial deployment was executed on 26 March.

Campaign chronology

Round 1

Orders opened 26 March. Orders resolved 31 March.
The battle map provided by command at the conclusion of round 1.

A combined force of air and sea — comprised of units from SierraKomodo's, Comrade's, and Sticky's forces — head towards the north east. They quickly engage three hydrofoil flotillas which are immediately destroyed on contact. Then, to the western perimeter of the island of Kula, two more hydrofoil flotillas are seen heading south towards a grid with one of SierraKomodo's nuclear attack submarines. Nothing else of note occurs this round.

BBM_Ping instructs Sirdog's air units to continue heading east towards the air field on Sopau. Sticky is instructed to ensure the patrol boats spotted off the western perimeter of Kula cannot threaten the rear of the carrier, but otherwise, Sticky's forces should maintain general direction with the fleet.

Round 2

Orders opened 31 March. Orders resolved 3 April.
The battle map provided by command at the conclusion of round 2.

The battle for the Tabar Straight begins proper. The chunk of Sticky's battalion engage multiple destroyers, a cruiser and a battle cruiser right on the straight, with both sides getting direct hits on one another. As a stroke of bad luck, one of SirreaKomodo's submarines makes direct contact with an OPFOR submarine in YR-76, resulting in it being targeted by both destroyers, taking damage. Further to the north, a battleship under Sticky's direct command engages a battle cruiser at the Iron Bottom Sound with both units hitting the other. Even further north, SierraKomodo's strategic reconnaissance aircraft spots yet another destroyer and battle cruiser at the mouth between the islands of Karu and Ghoveo.

To the west, a destroyer under SierraKomodo's command that was sent to the west of Kula at BBM_Ping's orders receives fire from the two hydrofoil flotillas spotted in the previous round, though they fail to meet their target. SierraKomodo's previously unspotted submarine in grid YL-76 engages one of the flotillas, failing to get a hit.

Sirdog's units make contact with the airfield on Sopau and, after getting the greenlight from BBM_Ping, begins bombing it, managing to do some damage. Sirdog's interceptor recieves contact from an OPFOR multi-role fighter and gets hit, with the interceptor responding and missing.

Nothing else of note occurs this round. Surprisingly, no units in the operational area were destroyed.

Retrieved from "https://wiki.edcgaming.org/index.php?title=Campaign_3_Playtest&oldid=2488"