Battlefield 6 Insider is leaking some important new details

Some new and great Battlefield 6 details were reportedly revealed by a prominent one Battlefield insider. Unfortunately, there is no word on a release date or a reveal date, but the report does reveal some interesting tidbits. For example, it claims the game will support cross-play between PS5, Xbox Series X and PC when released. While the report reveals this, it casts doubt on the game coming to PS4 and Xbox One, noting that if EA continues and releases the latest generation versions of the game, they will be included in this cross-play support. The report somehow doesn’t quite say whether the game is coming to PS4 and Xbox One, but the language used suggests that it hasn’t been finalized yet.

Aside from this, the report, which comes Tom Henderson’s way, Battlefield 6 takes “levolution” to the next level, or as Henderson puts it, it has levolution “on steroids.” This means that players can destroy most of the buildings in the game, as long as they don’t have targets in them. And this system is so advanced and complex that the building will fall in different directions depending on where it is compromised, making it sound like there will be some strategic element to destroy buildings.

Henderson further claims that squadrons return with four members and have the ability to create “units” by stacking squadrons. To that end, the Attack, Support, Reconnaissance, and Engineer classes are back.

Henderson claims the game will use a Battle Pass and Seasons structure, with the seasons scheduled for 8 to 10 weeks.

Finally, Henderson reveals that there will be a free-to-play element in the game, which will likely come in the form of a Battle Royale mode, or at least something similar to a Battle Royale mode.

Unfortunately, this is where the report ends. At this point, none of this has been verified or debunked by a comment from EA or Dice. Until this happens, take everything with a grain of salt as nothing is official here. Further, while the source is reliable, and while it is easy to assume that everything here is largely correct, it is also all subject to change.

.Source