The Battlepack variant of the Battlefest from Battlefield 1 causes frustration among players. What are the reasons for this?
The Battlefest is a large event that the developers want to celebrate together with the players of Battlefield 1. In the highlights, they talk about weapon skins, Battlepacks, and additional experience points. The announcement of the Battlepacks gave many players hope for cool, exclusive skins during the event. However, the developers have other plans.
Battlefest Battlepacks already in Battlefield 1
In the Battlefest highlights, the developers mentioned that there would be special Battlepacks for the Battlefest. On the official Battlefield website, they write: “Thursday, November 17: Battlefest Battlepack Update: A new Battlefest version of the Battlepacks will be activated.” Many players eagerly awaited the new version of the Battlepacks. At 9:30 PM yesterday, this tweet from the official Battlefield account followed:
In the game, however, there were no unique, new Battlepack revisions, but still the Battlepack Revision 5. This caused confusion among some players. Many assumed that exclusive weapon skins would only be available during the Battlefest. When players inquired whether Revision 5 is the special Battlepack version, they received the following response:
It seems that the already released Revision 5 Battlepack is the special Battlepack the developers are talking about. This has disappointed some players on social media. Reddit user Gharvar writes: “Now that we know there will be no special Battlepacks, players are understandably upset. That was the only part (of the Battlefest) I was somehow looking forward to.”
In future events, the developers should consider creating exclusive skins and rewards for the players. That could make events special and would probably please many players.
By the way, further frustration was caused by the hardcore servers that have now been activated in Battlefield 1. Important settings, such as a ban function or an admin menu, were not added to these servers. In the meantime, the developers have addressed this issue.
Also interesting:
