Why WildStar's name reservations were screwed up

Eliot Lefebvre
E. Lefebvre|05.19.14

Sponsored Links

Why WildStar's name reservations were screwed up
En fuego!
So WildStar's name reservation system didn't work quite right. It's working now, but when it went live it wasn't working at all, and for a first-come-first-served thing that's kind of a catastrophic problem. Compensation has been announced, but why did everything go wrong? Carbine's director of operations posted in the forums about how things went from bad to worse and where the breakdowns in communication took place.

The short version is that it started when a big information drop introduced a lot of new assets to the site, causing even more load than was expected for the page when the name service went up. After that was handled, however, another problem surfaced with the site's feedback, leading to what is described as the server performing what amounts to a DDoS attack against itself. And once that was fixed, another problem surfaced. If you'd like to see the whole breakdown in detail to understand how everything got messed up, take a look at the full post on the official forums.
All products recommended by Engadget are selected by our editorial team, independent of our parent company. Some of our stories include affiliate links. If you buy something through one of these links, we may earn an affiliate commission.
Popular on Engadget