Call of Duty Wiki

Welcome to the Call of Duty Wiki! Create an account and join the community.


Learn why you should create an account today!

READ MORE

Call of Duty Wiki
Call of Duty Wiki
The subject of this article appears in Call of Duty: Modern Warfare III The subject of this article appeared in Zombies mode The subject of this article appears in Call of Duty: Warzone 2.0
For other uses, see Vortex (disambiguation).
"Enter the swirling flames of the Vortex. Earn XP to unlock cataclysmic rewards. Equip the War Horse skin from the Tracer Pack: Weapons of the Apocalypse: War's Vengeance Bundle for a boost."
— Event Description
Vortex War'sDomain Event Menu MWIII WZ2

Event menu.

Vortex: War's Domain was an event featured in Call of Duty: Modern Warfare III and Call of Duty: Warzone 2.0 available between January 3rd and January 17th, 2024.

Overview[]

Players had to play matches of Multiplayer, Zombies or Warzone to earn XP and progress through the rewards. By having the "War Horse" Operator skin for Swagger equipped, players would have an additional XP boost.

Rewards[]

Item Name Image XP
Weapon Sticker The Goat
9,500 XP
Consumable 30 Minutes
Double XP Token
21,500 XP
Decal Through The Smoke
36,900 XP
Consumable 45 Minutes
Double Weapon XP Token
56,350 XP
Weapon Charm Ghost Fire
81,100 XP
Decal Skull Fire
112,450 XP
Emblem Volcanic
152,300 XP
Calling Card A Little Rusty 202,950 XP
Consumable 1 Hour
Double Battle Pass XP Token
267,200 XP
Weapon Sticker Winged Fire
348,900 XP
Consumable 1 Hour
Double XP Token
452,550 XP
Calling Card Forged In Flames 584,250 XP
Weapon Sticker Putrid Skulls
751,500 XP
Consumable 1 Hour
Double Weapon XP Token
963,950 XP
Weapon Camouflage Magma
1,233,700 XP

Gallery[]

Trivia[]

  • The event descrption erroneously states that the War Horse operator skin is acquired from the Tracer Pack: Weapons of the Apocalypse: War's Vengeance Bundle. It is actually acquired from the Tracer Pack: Horsemen: War Ultra Skin bundle.
  • The XP targets shown in-game for each reward were originally inaccurate. This was later fixed via a hotfix.[1]

References[]