Guild Wars 2

MokahTGS.7850:

This is actually not a bug, it is working as intended. It is not optimal, but to save the names of all of your pets (read: all of everyone’s pets) would require another large name database that ANet did not create. Currently the pet name feature saves the name in the slot, not the pet, so changing out the pet type resets the slot name.

Perhaps someday they will change this, but it is not a bug.

This is pretty much exactly what’s going on.

Tl;dr: we may change this some day, but it’s not going to happen in the near future, and it’s not a bug.

We’re currently investigating this issue. Thank you for the details and screenshots, everyone!

Thank you for the reports, everyone.

We’ve been hearing about sporadic reports of lag leading to disconnects, but they’re all on different maps and different servers. If you can let us know which server you’re seeing this on, in addition to the map name (which most of you have included) it may help us track down the root cause.

Thanks again; we hope to get this nailed down soon!

We’re aware of and investigating this issue, but we don’t have an ETA on a fix yet. Thank you for your patience!

Please note that we have an existing thread for reporting issues with guilds. If you are still experiencing issues, please post there so our programmers are aware of it.

In the future, please do not bump old threads to report new issues. This thread will now be closed.

Nadeen.6371:

OK I just ran it again and it did not bug.

The only difference I did is that I did not keep clicking on the sickened Quaqaan at the end.

First time I ran it, I kept clicking on him during the dialog.

Second time I just clicked on him and waited for him to give his speech and then transform.

Hope that helps you guys.

Thank you for the additional details! I’ve added this information to our bug report.

Thank you for the reports, everyone! We should have a potential fix for this going in with our next content patch.

In order to prevent players from encountering this bug while we work on a fix, we’ve disabled the Ranger chest from being opened for the time being. You will still be able to purchase the chest, but you will not be able to open it (and get weapons that you can’t use).

As soon as we have a fix for this bug, we will make the chest accessible again. Thank you for your patience and understanding!

As an update, we are still investigating this issue. Thank you for your patience!

We’re taking another look at this issue to see if we can identify what could be causing it. Are you doing this story step solo or as a group?

Thanks for the info!

Thank you for the reports, everyone; the designers are working on a fix for this issue. In the meantime, if you’re planning on buying the laurel box, we’d recommend that you wait for now. Sorry for the bug!

Note: Thank you to everyone who has submitted art bugs in the past! In order to help keep these issues organized, each month we will be creating a new thread for these so that it does not grow to an unmanageable size. Please do not resubmit bugs if you have already posted about them in a previous art thread as we will have already seen them and added them to our bug database. Thank you!

Please post them in this thread if you come across any sort of bug that fits in the following categories:

- Armor/clothing art issues (textures, placement, clipping…)
- Weapon art issues (textures, placement, effects, clipping…)
- Character model issues (textures, effects…)

General Guidelines:
-Take a screenshot of the issue
-Take a screenshot of your equipment on the Hero Panel (H)
- List your Race, Sex and Class
- Be as descriptive as possible
-Take a screenshot

—If the issue relates to clothing/armor/weapons—
- List the names of every piece of armor/clothing/weapon equipped (this includes the level requirement) when you encountered the issue
- If you can, list where you acquired the item (which NPC, what map location, which dungeon, etc…)

Note on clipping issues: While we understand the desire to have all clipping issues resolved, the way our items are designed sometimes causes some small issues that cannot be fixed easily. We’re looking for severe clipping (like your shield is impaling you or your daggers are completely hidden by your coat.) Things like hair clipping or minor clipping of weapons into armor are sometimes unavoidable.

Please attach the screenshots to your forum post rather than hosting it elsewhere.
If you have a video of the issue, please upload those to YouTube (unlisted) and link that along with your other bug information here.

For more Bugging Best Practices, see this thread.

We appreciate everyone’s help with these issues. Thank you!

Note: Thank you to everyone who has submitted art bugs in the past! In order to help keep these issues organized, each month we will be creating a new thread for these so that it does not grow to an unmanageable size. Please do not resubmit bugs if you have already posted about them in a previous art thread as we will have already seen them and added them to our bug database. Thank you!

Please post them in this thread if you come across any sort of bug that fits in the following categories:

- Stuck in the terrain or a prop
- Textural/graphical issues with the environment or world props
- Terrain or world props disappearing/flickering
- Anything else that you feel might be an art bug

General Guidelines:
- Take a screenshot with your mouse hovering over the minimap while it’s zoomed all the way in so we can see the sector name. Make sure your screenshot has a clear view of the issue too!
- If you got stuck, please describe to us what you were doing before hand, along with a screenshot (this includes listing any skill you may have used upon being pushed inside the terrain).
- If you can, open up the screenshot in a picture editor (like MS Paint) and circle or point to the issue.
- If the world or large areas of land appear to “pop” in and out or “flicker,” please be sure that you are facing the appropriate direction in your screenshot and follow the screenshot directions.

Any other art issues:
- Be as descriptive as possible
- Take a screenshot

Please attach the screenshots to your forum post rather than hosting it elsewhere.
If you have a video of the issue, please upload those to YouTube (unlisted) and link that along with your other bug information here.

For more Bugging Best Practices, see this thread.

We appreciate everyone’s help with these issues. Thank you!

HeyMattyB.8732:

Where is the “refund” option when submitting a bug report?

Bug reports do not equal support tickets. Bug reports are just that: reports of bugs that devs can review (and fix); you will not get any kind of response to a bug report. Support tickets are filed by going to the Support website.

I hope this helps clarify things!

Thank you for the updates; we’re taking another look at the events that make the Cattlepult accessible and what might be breaking them.

So far, it looks like the account name>email address change is something that is only visible to you — other players can’t see it, so your account security shouldn’t be affected. That being said, we are aware of and tracking this issue.

Thank you for the reports, everyone!

Thank you for the reports! We will be investigating this issue.

The best way to report crashes is to fill out the crash report box that comes up as those reports are sent directly to our programmers so they can fix any bugs on our side (note: you will not get a response to these reports).

In this case, it sounds like your computer may be running out of memory (are you running less than 4GB of RAM?), but I’m guessing. If you want more assistance, you should post in the Tech Support forum as noted in the Bugging Best Practices thread.

As this issue has been resolved, this thread will now be closed.

The Frozen Bow and the Frozen Short Bow are actually two different skins, despite looking similar (the naming conventions are kind of weird). ^^;

Thanks for the details, everyone! We’ll be looking into this issue and examining how dragon chests are affected by DR.

Did any of you do another event prior to fighting dragon? It’s possible you’re hitting the DR if you completed another event beforehand.

We’re tracking this bug, but don’t have an ETA on a fix, yet. Thank you for your continued patience!

Thanks for the reports, everyone; we’re looking into this now.

Thank you for the reports! We’re working on this issue and hope to have a fix soon™!

Colin has posted a response on this issue here.

Tl;dr: buggy achievement is being removed.

Thank you for letting us know that this is still an issue; I’ve reactivated the bug for further investigation.

I apologize for the lack of the updates on this issue; I can assure you all that we are still working on this. We attempted a potential fix with the last patch, but after checking the crash reports, it looks like it didn’t solve the problem. While we will be continuing to work on a solution, you may encounter this less frequently in the meantime if you lower your sound quality.

Thank you for your continued patience while we work on this bug.

Thank you for your concerns, everyone.

While the decorations on this armor set may resemble swastikas, they are not intended to (note the unbroken rune lines connecting them to the rest of the runes on the armor). As the current design is also small and unobtrusive, we do not have plans to change it at this time.

As this issue has been resolved, I’ll be closing the thread.

This has turned out to be a more complicated issue than fixing the rest of the Ghastly weapons, but we’re still working on figuring out why the bows are losing their effects. Thank you for your patience, everyone!

Good news: we have a potential fix for this issue in the next full update! Thank you for your patience, everyone!

Thanks for the reports! We have a potential fix going in with the next full update, so please let us know if it’s still reoccurring afterwards.

I just want to add here that the FPS problem in Bandithaunt is because the barrels repeatedly spawn on top of each other; it is not a hardware problem.

If you see this bug in a specific area(s), please keep an eye out for any creatures or props that could be causing similar behavior. If you encounter the issue on a regular basis and it is not limited to a particular area, it may be hardware based.

As an update on this issue, we’re putting in another fix for this with our next full update that should fix it. Thank you for your patience!

Thank you for the reports!

Unfortunately, as noted in the Game Bug forum guidelines, lists of bugs aren’t very helpful to us because we’re frequently sending thread links to specific people from different disciplines who may not be able to address the other bugs you’re reporting.

While we’ve noted the issues that we were previously unaware of from your report, please make a separate thread for your future bug reports. This thread will now be closed.

We’re attempting another fix for this issue with our next full update. Thank you for the reports!

If you did not receive Tixx’s present, please make sure that you have enough space in your inbox to receive mail — if you delete some older items, the letter should arrive. If you are still not receiving the letter, you can contact support by visiting https://en.support.guildwars2.com/ and they may be able to investigate your situation.

As this issue has otherwise been resolved, this thread will now be closed.

I come bearing good news: we have a potential fix for this skill challenge with the next update! I think you’ll all be pleased with our solution for this problem.

Thank you for your patience!

I’m sorry to hear this happened! Can you provide any details on what your party did prior to this bug occurring? We haven’t been able to reproduce this issue or identify why it might be happening, so any additional background would help.

If you have any comments on the loot drop system, please feel free to share your findings in this thread.

This thread will now be closed.

If you’ve found an exploit, please report it to us via exploits(at)arena.net. Thank you!

This thread will now be closed.

While we are aware of this, it’s a lower-priority issue, so we don’t have an estimate on when it will be fixed yet. I realize this is a long-standing bug, so thank you for your patience!

Thanks for the reports — we’re aware of and investigating this issue!

Note: Thank you to everyone who has submitted art bugs in the past! In order to help keep these issues organized, each month we will be creating a new thread for these so that it does not grow to an unmanageable size. Please do not resubmit bugs if you have already posted about them in a previous art thread as we will have already seen them and added them to our bug database. Thank you!

Please post them in this thread if you come across any sort of bug that fits in the following categories:

- Stuck in the terrain or a prop
- Textural/graphical issues with the environment or world props
- Terrain or world props disappearing/flickering
- Anything else that you feel might be an art bug

General Guidelines:
- Take a screenshot with your mouse hovering over the minimap while it’s zoomed all the way in so we can see the sector name. Make sure your screenshot has a clear view of the issue too!
- If you got stuck, please describe to us what you were doing before hand, along with a screenshot (this includes listing any skill you may have used upon being pushed inside the terrain).
- If you can, open up the screenshot in a picture editor (like MS Paint) and circle or point to the issue.
- If the world or large areas of land appear to “pop” in and out or “flicker,” please be sure that you are facing the appropriate direction in your screenshot and follow the screenshot directions.

Any other art issues:
- Be as descriptive as possible
- Take a screenshot

Please attach the screenshots to your forum post rather than hosting it elsewhere.
If you have a video of the issue, please upload those to YouTube (unlisted) and link that along with your other bug information here.

For more Bugging Best Practices, see this thread.

We appreciate everyone’s help with these issues. Thank you!

We haven’t forgotten about this bug! We have a potential fix for this issue coming up with our next major update.

As everyone has noted, this issue should be resolved now. Unfortunately, you may have experienced a roll back due to this issue – our programmers are looking into this to prevent it from happening in the future.

We apologize for the inconvenience, and thank you for your understanding!

Thanks for the reports! We’re investigating this issue now.

I thought I had posted about this issue elsewhere, but seeing as how I can’t find it…

We’re aware of and tracking this bug; thank you the reports!

We’re tracking this issue, but getting it to consistently occur has been difficult, so we don’t have an ETA on a fix yet. Thank you for your patience!

Thank you for your feedback. Ultimately, this was a design decision made early on in game development and is not a bug. As such, this thread will now be closed.

If you would like to discuss this further or suggest changes to our combat system, please post in the GW2 Discussion or Suggestion forums.

Thanks for the reports! We tried a fix previously, but it looks like it didn’t work; I’ll pass this on for further investigation.