The Headstart period for Guild Wars 2 kicked off this weekend ahead of its general release, and is to be expected with any MMO, the influx of huge numbers of players brought a swathe of issues. European gamers in particular suffered serious problems connecting to servers, resulting in “error 42″ messages, but ArenaNet believes the issue is now resolved.
For more persistant errors, ArenaNet has some useful advice. Error 21 can be circumnavigated by switching off the option to remember your account details before restarting your client, and error 1038 may mean you’re using the wrong Guild Wars 1 account. Error 1032 takes a bit of patience, as transfer demand is causing delays, while error 122 means whoeveer sold you your game pulled a swiftie and you should apply for a refund. Other issues, such as Trading Post, guild services and in-game mail, are proving more difficult to resolve.
If you’re having trouble connecting, the most up to date progress reports on the various errors and issues will be found on the MMORPG’s Twitter feed, but the Guild Wars 2 Knowledge Base is being regularly updated and contains a list of known errors, proposed solutions and ETAs where available. Check it out before you throw a wobbly.