Guild Wars 2

When players open the in-game “bug report” form, they should become invisible to any creature that is not already attacking them.

Arena Net asks us to “report the bugs as close to their source as possible”, but with the insane spawn rates in some places (some mobs respawn in less than 10 seconds), it’s simply not practical to do this, so we end up having to find a different location to write the bug report.

To make it easier to report bugs at their exact location, players could simply become invisible to the AI creatures when they open the bug report form. Obviously, they should not able to use this to avoid dying (i.e., creatures who are already attacking them shouldn’t suddenly ignore them). That way we wouldn’t have to worry about respawns / roaming creatures / other players using us as their involuntary tanks while we write the report.

I am not sure this would work. In PvE it would simply mean you are then stuck in the middle of all the respawned mobs, or in PvP it means you have given every class stealth!

I am sure ArenaNet won’t mind if you are not stood on the exact spot the issue occurred.

Erin.7521:

I am not sure this would work. In PvE it would simply mean you are then stuck in the middle of all the respawned mobs,

So? Then it’s up to you to fight your way out of there or run away. But at least you can write a proper bug report.

Erin.7521:

or in PvP it means you have given every class stealth!

I said “invisible to the AI mobs”, not invisible to other players.

Erin.7521:

I am sure ArenaNet won’t mind if you are not stood on the exact spot the issue occurred.

As I understand it, when you open a bug report window, ANET get information about your location sent with the report. If you move somewhere else and then open the window, they will get info about a different location. In ‘some’ cases this will be less helpful. You also might not be able to include useful screen shots when reporting from somewhere else

What I’ve been doing as a workaround is open the bug report form as close as possible to the correct location, then run / fight my way out of there (with the bug report window open, covering half my screen), so I can write the report somewhere quiet, and hope that when I press “submit” it sends the location and data from where it was opened. But it’s an awkward work-around that might not even work.

Sorry I miss-read this sentance:

Account.9832:

That way we wouldn’t have to worry about respawns / roaming creatures / other players using us as their involuntary tanks while we write the report.

I got the idea it would apply to PVP as well as I didn’t understand the ‘involuntary tanks’ part. So thank you for explaining this is not what you meant.

Account.9832:

What I’ve been doing as a workaround is open the bug report form as close as possible to the correct location, then run / fight my way out of there (with the bug report window open, covering half my screen), so I can write the report somewhere quiet, and hope that when I press “submit” it sends the location and data from where it was opened. But it’s an awkward work-around that might not even work.

It could well have changed since the BWE’s, but during the temporary opening of these forums during one of the BWE’s, I recall reading a thread asking about whether location was sent with the report. The official response was that the location data was taken when the report window was opened (as you hoped) rather than when the form is submitted. It could have changed though, although that would be odd.

Erin.7521:

I didn’t understand the ‘involuntary tanks’ part.

I mean when another player pulls some creatures to you and basically gets them to attack you instead of him (something which is far too easy to do and seems to go against GW2’s “anti-griefing” philosophy).

I’ve been reporting that “involuntary aggro transfer” exploit since BWE1 but apparently Arena Net thinks it makes sense to make creatures attack some player who is AFK, talking to some NPC or managing his inventory (or trying to write a bug report) even though that player never actually aggroed the creature…