Jump to content
  • Sign Up

Branded Employee.5397

ArenaNet Staff
  • Posts

    11
  • Joined

  • Last visited

4 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Branded Employee.5397's Achievements

  1. After temporarily disabling it earlier to address a crash, we are now re-enabling the Wizards Vault. You should now see your current progress on objectives and be able to claim your rewards.
  2. Bug Fixes: Fixed a server crash. Fixed a client crash. Gliding has been reenabled in WvW.
  3. We are temporarily disabling the Wizards Vault while we address a crash. You can continue progress towards the current objectives, you will just not be able to see this progress it or claim the rewards until the Wizards Vault is re-enabled.
  4. This thread has been appropriately closed, and people who believe they were suspended or banned in error should contact Customer Support if they wish to appeal. That said, we'd like to provide a little more context. Most players using mounts or chairs to unlock waypoints are not caught in our automated bot reports. Even if they were, we do a manual review of such reports. Our team knows about this legitimate use of mounts and chairs, and we look at more contextual data to inform our review. We understand that the possibility for false positives exists regardless; that is why we encourage those who feel their suspension is unfounded to contact Customer Support. Thank you.
  5. Thank you all for reporting the issues with the Dragon Response Missions in the Dungeon Rush event. We're investigating it, but we're at a stage in our process for next Tuesday's Wintersday release that makes it very difficult for us to safely address this issue in the live game. We'll be able to fix this for future iterations of the event, but we aren't able to fix the DRM bug this week. We sincerely apologize for the trouble we know this is causing. The specific issue, as some people have rightly deduced, is that the instance owner is getting all credit for a DRM completion. Players can either solo the DRM or take turns in private groups to work around this issue.
  6. Bug Fix: Fixed an issue in the Treachery chapter of the Guild Wars 2: Secrets of the Obscure story that caused the player's UI to become permanently hidden during the encounter.
  7. Hello friends, I'm here with an update that the blog is coming on the 20th. As we said in Rubi's original post, it takes us time to lock text down and get it through our publishing pipeline. Please accept my apologies for the delay from our communicated schedule.
  8. Clarification: this will be available to everybody (including those who did get the rewards the first time around—grats on your extra bag slot!).
  9. We believe we've found (and fixed) the root cause of the game download issue. We have identified the mechanism that was causing corrupt files to be stored in our Content Delivery Network (CDN). That *should* mean that this problem is resolved. We're keeping an eye on it, but we think we're in the clear. Some of the edge servers for our CDN may have their own unique errors—we’ll only be able to fix those after we learn about them. For most players, there is no action to take for this to work—next time you open the launcher and start downloading files, it should work. For some players who modified their hosts file to work around the problem, our fix will have made it impossible to log in. This should only apply to players who specifically opened and modified their %windir%\system32\drivers\etc\hosts file (so if that sounds unfamiliar to you, you probably didn't do it). If you did modify your hosts file, you'll need to undo that change in order to continue logging in and playing the game. Once you've backed out any change you made, you should be able to download and play as expected. If, after modifying your hosts file to remove the change, you still get an error, we'd like to ask that you run the game with the "-log" argument to get a log for CS and our engineers to review. To do so: Open your Guild Wars 2 folder. Right-click on GW2.exe and select Create Shortcut. Right-click on GW2.exe - Shortcut and select Rename. Rename the shortcut to Guild Wars 2 Logging. Right-click on Guild Wars 2 Logging and select Properties. Locate the Target line and add -log after the existing text. Your target line should now look something like this: C:\Games\Guild Wars 2\GW2.exe -log Click OK to save your changes. Run the launcher, experience the download problem, and close the launcher again. Open an Explorer window. In the nav bar, type %appdata% and press Enter. You will now be in the AppData\Roaming folder Open the Guild Wars 2 folder. Find the gw2.log text document. ...then you'll want to submit a Tech Support ticket with everything you know about the problem. Within a few minutes, you'll receive an automated response email from support@guildwars2.com via zendesk.com; you can reply to that with your log file. Again, these steps are for folks who modified their hosts client and are still getting an error. We appreciate everyone's patience as we dug into this and got a fix in place.
×
×
  • Create New...