Some games arrive with the quiet hope that their players will find old pleasures waiting for them, and Star Wars Battlefront: Classic met its returning fans on a night when the doors opened too narrowly for everyone to pass through. Its multiplayer servers went live in the late hours before March 14, and by one player's account roughly ten thousand people pressed against a gate with room for about two hundred. The disappointment that followed has settled into the game's public record, where most of its reviews on Steam now lean negative. Whether that record is a verdict or only the mark of a r
Star Wars Battlefront: Classic Launch Stalls Under Server Failures and a Wave of Negative Steam Reviews
Matches ended in under 210 seconds
Mark
Launch night was rough. What actually went wrong first?
Mimi
Servers. Multiplayer opened at 10pm Central, and only three servers were joinable. One player said that left about 200 slots for roughly 10,000 people trying to connect.
Luke
That 10,000 is one player's claim. The report doesn't say where it came from, and it isn't a publisher number. The scale of the crush is plausible but unconfirmed.
Mark
Did the server problem get fixed?
Mimi
Largely, yes. After a turbulent first couple of hours, enough dedicated servers were added, and players can now host their own non-dedicated ones too.
Mark
So why are reviews still so bad?
Mimi
Because the server shortage wasn't the only problem. Conquest matches on Kashyyyk ended in under 210 seconds. Players also report spawn glitches, crashes, unbalanced teams, broken achievements and confusing audio.
Luke
The match timing is Dot Esports' own test of one match, so it's one data point. The other issues are described as player reports, and the article doesn't say how widespread they are.
Mark
What do the reviews actually show?
Mimi
At the time of writing, 20 percent of 1,817 Steam reviews were positive, a mostly negative rating.
Luke
And that's a snapshot taken during the worst of launch. The article itself says reviewers might change their minds, and nothing yet shows whether they will.
Le Pouls
- Ten thousand players rushed a launch that opened only three joinable servers, leaving room for roughly two hundred.
- Frustration spilled onto Steam, where only about one in five of the 1,817 reviews is positive.
- Short Conquest matches ending in under 210 seconds, a spawning glitch, and unstable connections compound the anger.
- Dedicated servers have been added and players can host their own, but ticket counts, crashes, and balance still await fixes.
- The rating now hangs on whether Aspyr's patches arrive quickly enough to win back reviewers.
Some games arrive with the quiet hope that their players will find old pleasures waiting for them, and Star Wars Battlefront: Classic met its returning fans on a night when the doors opened too narrowly for everyone to pass through. Its multiplayer servers went live in the late hours before March 14, and by one player's account roughly ten thousand people pressed against a gate with room for about two hundred. The disappointment that followed has settled into the game's public record, where most of its reviews on Steam now lean negative. Whether that record is a verdict or only the mark of a rough beginning depends on what the developer, Aspyr, does with the time it has been given.
Star Wars Battlefront: Classic opened its multiplayer servers at 10pm Central Time on the night before March 14, and the first crowd arrived all at once. One player estimated that about 10,000 people tried to join, but only three servers were open, which by that account meant roughly 200 slots. The player was furious and urged others not to buy the Star Wars Battlefront Classic Collection. The 10,000 figure is that player's claim, not the publisher's.
The anger moved quickly to Steam. At the time of Dot Esports' reporting, only 20 percent of the 1,817 user reviews were positive, placing the game's overall rating at mostly negative. The server shortage eased after a turbulent first couple of hours, as more dedicated servers came online and players gained the option to create their own non-dedicated servers.
The servers were not the only problem. Ticket counts are low in most multiplayer modes, so matches end almost before they begin. A Conquest match on Kashyyyk that Dot Esports timed lasted under 210 seconds, with each team of 64 players starting with just 100 lives. Other complaints include a spawning glitch in Conquest and Hero Vs, crashes tied to unstable connections, unbalanced teams, achievements that fail to track, and audio that makes enemy gunfire hard to locate.
Reviewers may yet change their minds once the fixes land. For now, the rough start has left the game climbing out of a hole it dug on its own launch night. What to watch is whether Aspyr patches the ticket counts, the spawning glitch, and the crashes, and whether the Steam score responds.
Multiplayer servers for Star Wars Battlefront: Classic went live at 10pm Central Time on the night before March 14. By the account of one player, roughly 10,000 people tried to get in at once. Only three servers were joinable, which that player said cut the number of available slots to about 200.
The player's reaction was blunt. "Jesus Christ, I am so disappointed; this is robbery," they wrote, urging others not to buy the Star Wars Battlefront Classic Collection. The 10,000 figure is that player's claim, not a number from the publisher.
The frustration spilled onto Steam. At the time of Dot Esports' reporting, only 20 percent of the 1,817 user reviews for Star Wars Battlefront: Classic were positive, which put the game's overall rating at mostly negative.
The server shortage did not last. After a turbulent first couple of hours, the game added enough dedicated servers to support its player base. Players can also now create their own non-dedicated servers.
Servers were not the only complaint. Ticket counts are low in most multiplayer modes, so matches end almost as soon as they begin. Dot Esports timed a Conquest match on Kashyyyk and it ended in under three and a half minutes, under 210 seconds. The mode gives each of two teams of 64 players just 100 lives, which leaves little room for error.
The outlet describes the ticket problem as an easy one for developer Aspyr to fix, but the list continues. A glitch makes it hard to spawn properly in Conquest and Hero Vs. Unstable server connections cause frequent crashes. Teams are often unbalanced, achievements are not tracking properly, and audio problems make it hard to pinpoint where enemy gunfire is coming from.
Reviewers could still change their minds once the server issues are resolved. But as Dot Esports puts it, the game did itself no favors by starting from deep in a hole. What to watch is whether Aspyr patches the ticket counts, spawning glitch and crashes, and whether the Steam score moves in response.
Citations marquantes
I am so disappointed; this is robbery. Don't buy Star Wars Battlefront Classic Collection.— Irate Battlefront player, quoted by Dot Esports
Envie de l'histoire complète ?
Lire l'original sur Dot Esports ↗
Crime & Justice