Fandom

Vega Conflict Wiki

Crossfire

414pages on
this wiki
Add New Page
Comments5 Share

NOTE: THIS EVENT HAS ENDED AS OF 11TH OF JULY.DEMON CORPS DIVISION FLEETS ARE NO LONGER LAUNCHED AND INTEL ARE NO LONGER OBTAINABLE.


Event OverviewEdit


Be Warned, the Demon Corps was born in blood.... they have one purpose, to see your ships burn......
  — General Geir 
C80uujikib73
CROSSFIRE -BEFORE EVENT

7/10/16

This is Keres VII, ally of the rebellion.

Commanders, my troops have detected movement along the sector perimeter. We believe it's the VEGA military that Bishop spoke of, but we can't be certain yet. I'm afraid we don't have conclusive information about their technology.
  — Keres VII 
CROSSFIRE -BEFORE EVENT

7/11/16

The Rebellion? No, I don't think I'll call you that. You only fight when it's convenient for you, with no greater purpose. You haven't earned the name Rebellion.

My Demon Corps could destroy you in an instant, but I'd rather watch you suffer - that's my purpose.
  — General Geir 
CROSSFIRE -BEFORE EVENT

7/12/16

This is Keres VII.

Commanders, my scouts have detected a vessel of unknown type. It has not answered our hails, so we must be prepared for the possibility of hostile action.

I have attached an image of the vessel for your analysis.
  — Keres VII 
CROSSFIRE -BEFORE EVENT

7/12/16

I expect we'll be seeing more of this so called "Demon Corps" soon. My scouts have determined that we'll be facing fleets with both military and Amber Army ships.

I don't like fighting my own company, but if that's what it takes.....
  — Keres VII 
CROSSFIRE -BEFORE EVENT

7/13/16

You're used to being given chances, aren't you? Surrender now or face the consequences?

Not anymore. the Demon Corps offers no mercy, takes no prisoners and we certainly don't discuss terms of surrender! Maybe you prefer it that way? I certainly do, and the Amber agrees with me. Let's see how deep your blood can run.
  — General Geir 
CROSSFIRE -DURING EVENT

7/15/16

Commanders, my scouts have reported weapons fire from the unknown vessel: a projectile weapon with a high rate of fire. Luckily my troops were able to escape unharmed.

The vessel clearly has hostile intent. We will continue to monitor.
  — Keres VII 
CROSSFIRE -DURING EVENT

7/16/16

Grave news, Commanders. Several of my scouts were intercepted and destroyed by additional hostile ships. We did a lot of damage with our new prototype explosive weapon, but the enemy outnumbered us.

We managed to capture an image of the weapon in action.
  — Keres VII 
CROSSFIRE -AFTER EVENT

7/19/16

Is that what you call a rebellion?

Pathetic. That's not nearly enough! The Amber hasn't been satisfied yet. My Demon Corps has not yet arrived in full, so consider this a glimpse of what's to come. Do not disappoint me again!
  — General Geir 

DescriptionEdit

Crossfire is the 22nd Major event to occur in Vega Conflict, and the first to feature VEGA's military division, the Demon Corps.

Event Information Edit

SCHEDULED EVENT DATES
START TIME 3:00 pm PDT
END TIME 3:00 pm PDT
START DATE Thursday, 14th of July, 2016.
END DATE Monday, 18th of July, 2016.
GENERAL EVENT INFORMATION
EVENT TYPE Attack+Defend Demon Corps Division (Attack)
Demon Corps Seige (Defend)
ANTAGONIST General Geir and the Demon Corps
DUERTAGONIST Rebels (Of Course)
DURATION OF EVENT 4 days Event Shop closes Tuesday, 19th of July, 2016

Event Prizes Edit

Returning Prizes Amount of Intel New Prizes Amount of Intel
Impulse Beam I Vector Torpedo I Bomber Squadron I Binary Thrusters I 25,000 Storm Driver I Bayonet Missile I Reinforced Rails I Volatile Fuel I 50,000
Impulse Beam II Vector Torpedo II Bomber Squadrons II Binary Thrusters II 125,000 Storm Driver II Bayonet Missile II Reinforced Rails II Volatile Fuel II 200,000
Impulse Beam III Vector Torpedo III Bomber Squadrons III Binary Thrusters III 375,000 Storm Driver III Bayonet Missile III Reinforced Rails III Volatile Fuel III 500,000
Freyja Carrier Vigilante Battleship 1,350,000
Covernant Cruiser 2,500,000


DEMON CORPS DIVISION

Fleet Level

Amount of Intel Received
27 740
30 920
33 1,280
35 1,650
37 2,170
40 3,300
45 7,200
50 16,390
53 27,190
55 38,300
60 55,000
63 85,000
65 110,000


DEMON CORPS SIEGE FLEETS

Base Level Amount of Intel Received
20 4,000
21 5,800
22 7,600
23 9,400
24 11,200
25 13,000
26 14,800
27 16,600
28 18,400
29 20,200
30 22,000
31 23,800
32 25,600
33 27,400
34 29,200
35 31,000
36 32,800
37 34,600
38 36,400
39 38,200
40 40,000
41 40,920
42 41,880
43 42,800
44 43,720
45 44,680
46 45,600
47 46,520
48 47,480
49 48,400
50 49,320

Fleet LayoutsEdit

Demon Corps Division: Demon Corps Division fleet collaborating with Iron Star Forces.

Demon Corps Siege: Demon Corps Siege fleet collaborating with Iron Star to Attack Rebel bases.

Trivia Edit

  • The Event introduced a new branch of the VEGA Corporation called Demon Corps.
  • The Event fleet was the first to contain a cutter ever since last year March.
  • The Event fleet was reused for the next event, Scorched Earth, because the original event fleet (Demon Corps Raiders) was too easy,
  • The Event contained the most number of prizes of any event, with the exception of the special event.
  • The Event video was designed differently from previous ones, and was the first video to feature Geir speaking to us as the villain.

Gallery Edit

Video Edit

VEGA Conflict- Crossfire01:01

VEGA Conflict- Crossfire


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

DevastationVengeanceResurrection


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.