Aspyr Media has issued a statement on the launch day issues plaguing Star Wars: Battlefront Classic Collection. The move saw the studio attribute the ongoing problems to some «critical errors» with its backend, which dispelled one popular fan theory about what went wrong with the Star Wars: Battlefront Classic Collection launch.
The combo of Star Wars: Battlefront and Battlefront 2 remasters was originally announced in late February, with Aspyr touting it as the optimal way to experience Pandemic Studios' iconic shooters. While both games offered single-player components, they largely owe their cult statuses to their hectic multiplayer modes. Since the official servers for the original titles had long shut down, the promise of once again experiencing classic Battlefront multiplayer has been the main selling point of the remaster bundle.
But the March 14 launch did not go smoothly, with many players taking to social media to complain about crashes, bugs, and a surprisingly small number of servers that were immediately overloaded with traffic, preventing most people from getting into a match. Star Wars: Battlefront Classic Collection consequently ended up being review-bombed, as underlined by the fact that it currently sits on over 3,500 «Overwhelmingly Negative» user impressions on Steam. While that backlash continues, Aspyr has now issued a statement reflecting on some of the bundle's day-one problems.
As far as the multiplayer issues are concerned, the developer blamed the disastrous launch on some «critical errors» affecting its network infrastructure. Although many fans lambasted it for severely underestimating day-one demand by offering just three 64-player servers at launch, the studio clarified that its backend was designed to have a much higher capacity. However, the aforementioned problem is said to have caused most servers not to appear. Aspyr stated that the high ping, crashes, and matchmaking errors that Star Wars: Battlefront Classic Collection players
Read more on gamerant.com