well i noticed a lot of crashing but after the last crash the account i was on wont relog... its been attempting to relog for over 6 hours or so i watched 2 movies on netflix ... i was thinking the server was down for big fix and wanted to test it so i logged onto my F2p account and it works fine... so yeah i guess its my client... but it wasnt doing this yesterday or this whole week even... but i havnt been able to play all day and its driving me batty...

my F2p plays fine but my P2p wont even connect to the server... it says:
"Failed to connect to Socket" i made a ticket havent heard anything from the smart people that know how to fix things... but im sure they will respond soon...

made the mistake of asking some of the players in game for help... all that did was piss me off and make me mark down names of people i want to share a little friendly revenge with...

hate trolls... in wow you couldnt punk their characters... thankyou star sonata for making justice hard core

the unable to connect to socket error, is usually related to router/modem not reseting the socket correctly after a crash, but the fact that you can log on your f2p is incredibly weird....

None the less, for people who had that issue in the past, rebooting the computer/reseting the modem/router pretty much always fixed it. Its unfortunatly a bug in the winsock api (that error is an error message directly from that). There are ways around it (namely, use another network library), But i havent had the time to actually do that yet.