Feedback talk:Game updates/20120222

From Guild Wars Wiki
Jump to navigationJump to search

Issues[edit]

Am I the only one having trouble logging back in? The client crashes upon loading. Zooey 02:13, 23 February 2012 (UTC)

I'm having the same problem. --99.231.170.36 07:33, 23 February 2012 (UTC)
Hi, could both of you provide me with more details on your situation (screenshots, details about your computer) so that we better understand the issue? Please use a private communication method, preferably a private message on the Support Forums or on one of the GW fansites? Thanks. --Stephane Lo Presti talk 21:02, 27 February 2012 (UTC)

My firewall keeps popping up, asking me why gw.exe wants to access 64.25.40.31, TCP:6600. My poor google skills had nothing on that, except "The IP address 64.25.40.0 was found near Austin, Texas located in United States. We found 0 companies nearby IP address 64.25.40.0 and 0 points of interest." 78.73.69.53 03:01, 23 February 2012 (UTC) Oh never mind, it's all NC Interactive. I'll take off my tin-foil hat now :D 78.73.69.53 03:17, 23 February 2012 (UTC)

I can't seem to get into the game, either... D: ~ 94.168.152.73 18:28, 23 February 2012 (UTC)
It's because the new security system was made a default feature with this update. People whose client automatically closes instead of loading the log-in screen can force the client to not use the new security system by using the "-oldauth" command line argument, which should cause the client to load the log-in screen. --Silver Edge 04:10, 24 February 2012 (UTC)
Hi 78.73.69.53, did you allow that port (6600) in your firewall? This should solve the issue but we'd like to know for sure. Thanks! --Stephane Lo Presti talk 21:02, 27 February 2012 (UTC)

Hi Stephane, yes, well I allowed all activities for gw.exe and it solved the issue. Thanks for caring! :) 78.73.69.53 23:21, 28 February 2012 (UTC)

Outpost Firewall actually has custom rules created for Guild Wars. THey should hvae poppped up. 71.241.142.9 16:03, 4 March 2012 (UTC)

Security[edit]

Does this new update have anything to do with the massive (Code 007) spree from last night? Just would like to know it won't happen again. Saga [DOJO] 03:06, 23 February 2012 (UTC)

More than likely, yes. Gaile apparently was dealing with questions about how many times it could "accidentally" happen before your account was permabanned. The people responsible have been sacked. FleshAndFaith 03:58, 23 February 2012 (UTC)
I think is because of this https://forum.guildwars.com/forum/forums/accounts/ArenaNet-needs-your-help-for-a-test 89.154.54.66 05:26, 23 February 2012 (UTC)