Every since Fortnite and PlayerUnknown's Battlegrounds launched, gamers have been addicted to the battle royale genre. While Call of Duty: Black Ops 4 was the first major "AAA" game to feature the mode, Battlefield V isn't too far behind. Many months ago, EA announced that it's "Firestorm" battle royale experience would launch in early 2019.
With titles like Fortnite and Apex Legends dominating the shooter scene, Firestorm puts a last-man-standing spin on EA's realistic first-person shooter series. Today, the company announced that Firestorm should launch on March 25. That's not all though as we also received a new trailer.
Firestorm looks like a completely chaotic experience because it not only features insane on-foot combat, but also a variety of vehicles. In the trailer, you can see that a soldier kills an enemy with a tractor. There are also helicopters involved. We want wait to see what else Firestorm has in store for players on March 25 as a free update.
In our review, we said, "The lack of polish in some of the systems will get improved with patches, but the missed opportunities with the campaign content frustrate the full package. But ultimately, this is one of the best multiplayer shooters you will play this year, and maybe the best until the next Battlefield."
The fire rises
Get ready for all-out warfare
Battlefield V's multiplayer combat remains as grand as ever, with stunning visuals and explosive gameplay. And its free Firestorm battle royale update is just on the horizon.
Asher Madan handles gaming news for Windows Central. Before joining Windows Central in 2017, Asher worked for a number of different gaming outlets. He has a background in medical science and is passionate about all forms of entertainment, cooking, and antiquing.
I don’t know if people really care about this anymore. Seems like Battlefield V is a little late to the party. Even Call of Duty: Black Ops 4 “Blackout” failed to take off.
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.