Ground Vehicle Battle

1. Scenario Detail

1.a. Purpose and Description of the Scenario

Two or more teams face off in a multiple round team elimination battle using only ground vehicles.

1.b. Intended Number and Size of Teams

  • Two or more teams.
  • Teams should be balanced so that there is an even number of participants per team in each round.

1.c. Scoring and Victory Conditions

  • The winner of each round is the last team with at least one surviving vehicle.
    • A vehicle is defined as “Surviving” if it has the ability to either shoot OR move, but does not need to do both.
    • If there are vehicles remaining from multiple teams that have been disabled to a point that they are not able to eliminate each other, then a draw will be called for that round.
    • Org leaders are permitted to call for a draw at any time, but it must be accepted by the opposing org leader.
  • The team that wins either the most rounds in the allotted time, or a best of 3, best of 5, or best of 7 rounds is declared the victor.

1.d. Variations

  • Tonk Battle – The only eligible vehicle is the Tumbril Nova tank.
  • Centurion Battle – The only eligible vehicle is the Anvil Centurion.
  • Cyclone Battle – The only eligible vehicle is the Tumbril Cyclone and its variants.
  • Hover Vehicles Only – The only eligible vehicles are the CNOU Hoverquad, Drake Dragonfly, and Aopoa Nox.
  • Any Other Vehicle-Specific variant.

1.e. Scenario-Specific Restrictions

  • The combat zone should be within 20km of an outpost with a Platinum Bay to facilitate rapid vehicle replenishment.
  • One or more respawn-capable ships (Carrack or 890j) should remain at the outpost to reduce wait times between rounds.
  • The combat zone should be approximately a 2km square for most vehicle variants, the area should contain at least one major line of sight blocker such as a plateau or hill, and the boundary of the zone should be marked clearly with abandoned ships provided by the participants.
  • Org leaders must define if the vehicles are to be operated solo, in 2-player teams, or at players discretion.

1.f. Resource Requirements

  • Three or more large ships to mark the perimeter of the combat zone OR a perimeter that’s clearly defined by existing terrain.

2. Defining The Event

2.a. Participants

The recommended minimum number of participants for this event is 4 per team.

2.b. Event Time

To be determined by event.

2.c. Event Duration

The expected time is between 2hrs and 4hrs depending on the number of rounds to achieve victory, or a fixed time may be declared ahead of time.

2.d. Event Broadcast URLs

Two broadcast URLs are required for sanctioned events, one for attack and one for defense.

3. Executing the Scenario

3.a. Preparation Phase

  • T-Minus 30 Minutes: Party Launch
    • All participants from form a single party and launch from menus. Once in game, the party is disbanded and each team assembles their own party.
    • Late arrivals join their respective parties in game.
    • Org leaders should rally their teams to the combat zone, which should be agreed upon before the scenario starts.
  • T-Minus 15 Minutes: Perimeters Defined, Respawn Check and Comms Blackout
    • Org leaders coordinate to establish a perimeter with abandoned ships and all participants to be briefed on the perimeter markings.
    • All team members should set their respawn locations to one of the respawn capable ships on site.
    • One crew is sent to disable the Comm Array to prevent accidental crime reporting during the event.

3.c. Action Phase

  • Round Start
    • Each team should assemble at a defined rally point at the beginning of each round.
    • One org leader will broadcast a 10 second countdown through global chat and voice chat.
  • Round End
    • The round ends once all enemy vehicles have been destroyed or the org leaders mutually agree on a draw.

3.d. Declaring Victory

If this is a timed event, the team with more rounds won when the time has expired will be declared the winner.

If the event is a best of 3, best of 5, or best of 7 contest, then the first team to meet the threshold of rounds won will be declared the winner.

3.e. The Revelry

The location of the Revelry should be at the outpost used for vehicle retrieval.

3.f. Recovering from Interruption

In the event of a server disconnect or other significant server interruption, the current round will be declared a draw, and all players should expect to start the next round 20 minutes after the party launches into game.

3.g. Balance Considerations

There are no current special considerations for balancing.

4. Change Log

  • 2023-01-01: Initial Revision