Fandom

Vega Conflict Wiki

Arms Race

364pages on
this wiki
Add New Page
Comments9 Share

Event OverviewEdit


Gather Combat data, arm your fleets.
  — Sybil 
New Carrier
NEW TRANSMISSION RECEIVED

This is Larus, Rebels.

Your strategy of "acquiring" VEGA technology has worked so far, but there's nothing like a home-cooked meal.

My goal is to create a rebel carrier even more powerful than the Ragnarok. I've made a lot of progress already, but I need more combat data to finalize the design. That's where you come in...

I think we understand each other. I'll keep in touch
  — Larus 
NEW TRANSMISSION RECEIVED

Good to see you again, Rebels.

You fought well against VSec and their Ragnarok carriers, but they really can't take a hint. I hear they're already preparing another deployment. It's not all bad news though: this is a perfect opportunity for you to gather more data about the Ragnarok and help me complete my carrier design.

Good luck, Rebels.
  — Larus 

Event InformationEdit

SCHEDULED EVENT DATES
START TIME 3:00pm PST
END TIME 3:00 pm PST
START DATE Thursday, May 7th 2015
END DATE Monday, May 11st 2015
GENERAL EVENT INFORMATION
EVENT TYPE Attack VEGA Regiment Fleets
ANTAGONIST VEGA Corporation
DEUTERAGONIST Larus
DURATION OF EVENT 4 Days Event Shop Closes Tuesday May 12th 2015
  • All prizes excluding the Valhalla Carrier have three different levels and are unlocked in tiers based upon the number of points or other battle rewards that a player has. Picking 1 tier item makes the other item of the same tier unobtainable in this event.

Event PrizesEdit

Prize Name Amount of Data Cores
Wave Driver I Bomber Squadron I 50k Points (Tier I)
Wave Driver II Bomber Squadron II 250k Points (Tier II)
Wave Driver III Bomber Squadron III 750k Points (Tier III)
Valhalla Carrier 1.5M Points (Tier IV)

Description Edit


Vsec will fall.
  — Sybil 

Arms Race is the 8th feature event of VEGA Conflict.

This event is the first to feature ships in the event fleets with extended range, making battleships the only ones capable of outranging them.

Players found a way to earn easy event points by killing the 2 Corinthian cruisers and eagle frigate and then leaving the rest of the fleet, giving roughly 22k points if done on a 55.

This is the second event to feature the Ragnarok Carrier, and the first time both sides can use carriers to fight each other.

Fleet Layout Edit

Vsec Regiment 27-55

Vsec Regiment Fleet: Vsec Regiment fleet supported by a carrier.

Gallery Edit

VSec Regiments

VSec Regiment fleets in-game

Screen Shot 2015-05-11 at 2.25.35 PM

Completed event store

Video Edit

VEGA Conflict - Arms Race01:12

VEGA Conflict - Arms Race

Event Video

Trivia Edit

  • Arms Race is the 8th major event to occur in VEGA Conflict and the first to release a carrier-class ship as a reward.
  • This event is unique in that it is the first to feature ships with longer ranges then what is normally obtainable, making them near impossible to kite or out-range. This event was also the first to feature carriers with Squadrons that were near impossible to kill because their health was increased massively.
  • KIXEYE stated that the bug caused in Riot 5 (which angered many players) was because of a bug that caused the range extension to go into effect too early, making the Riot much harder than usual and causing outrage on the forums.

Contests

Search and DestroyUltimate VEGA ThreatBounty Weekend

Recurring Events

RiotCivil WarAlien MobilizationAlien DecimationSpecial Event

2014 Feature Events

UprisingRetributionDeceptionCrackdown

2015 Feature Events

EspionageJailbreakMartial LawArms RaceCountermeasuresFace OffReclamationEmergenceRevengeEvacuationWarfront

2016 Feature Events

BacklashShadow StrikeConspiracyBlood TrialsIron BloodZero HourCrossfireScorched EarthIncursionSearch and DestroyMaelstromNemesisRedemption

2017 Feature Events

DevastationVengeance


Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.