Guild Wars 2

SlippyCheeze.5483:

PS: when I say there is no reasonable way, what I mean is that it is not technically impossible for anet to determine what the code is doing by, eg, reverse engineering it, or capturing video of your screen, or whatever.

I’ll expand on that with info I know
If one day Anet decided to go on a witch-hunt for the non-ToS compliant “DPS meters” out there, they’d be able to figure out who’s running the proper ones and who’s not.

As far as I know, through interactions with the developer of Arcdps, Anet developers can pull information about the .dll files since each of these carry the ‘build info’ within it. The developers can match that info with the ones in each of the developer’s website and find out whether you’re in compliance or not.
_________________________________________________________________
Since there was such a large response and tension as a result of recent events, the best course of action would be to stay on the safe side: stay in compliance and strictly have the ToS compliant meters installed.

As SlippyCheeze said, we got the privilege of using them as tools, but Anet can simply turn around and reverse that decision in an instant if it becomes abused by many.

OGDeadHead.8326:

The health bars we’re talking about here are for healing purposes, as in seeing the health of allies ONLY, not to see the health bar of your enemies.

Yes, that’s one of the purposes that the health bars have. However, its purpose isn’t exclusive to that. As a matter of fact, these health bars can be used (and abused) in other content since you’re seeing beyond what was originally intended.

Keep this in mind: DPS meters were allowed as they provided combat metrics to the user on which they could act upon sometime down the future; modified health bars provide you an instant advantage over others that don’t use it as it’s giving you the opportunity to act upon something immediately.

Yup, you got most of the idea right. The exact part that actually breaks the whole thing is when you check the Roster tab. I used to run a guild and often enough checked the guild history tab to catch up on anything important I missed while offline.

From what I’ve found out by scouring past posts, the whisper bug seems to be caused by the presence of a separate server that caches contacts and guild information. Since it’s a separate server, the game client (which seems to operate on a different server) has to send a request to the other server. However, the process by which your game client sends and receives the information from the other server is slow, resulting in the whispers not working (as it requires contact information).

Interestingly, we see the interaction and presence of the two servers very often, but don’t pay much attention to it. Whenever you see the “………….” in the guild history roster tab, that’s the game client trying to retrieve the cached information from the other server. If you leave it for a while, it’ll finish loading. Also, there’s rare occasions when you see a lot of your contacts going ‘Offline’ and back ‘Online’ moments later, which, seems to be a loss of connection between the servers.

This is a known bug. It occurs when you check the guild history in the guild tab. Unfortunately, the only solution is to restart the game, or refrain from checking the history tab often (which I know it’s a challenge lol)

Gaile Gray.6029:

If there are other sound-related issues that you believe we should address, you may add them to this thread.

Yay, I get to express a minor issue with another Legendary that many may not be aware of (I promise, just a minor issue)

Chuka and Champawat, the tiger shortbow, sounds like a low-pitch pig and a high-pitch dog. Yea…

My proof! (Warning: Owners of Chuka, you won’t be able to unhear it past this point; you’ve been warned!)

If the “send crash report” message comes from the client and not the OS, (for Windows) go to C:/Users/<Username>/AppData/Roaming/Guild Wars 2. Open the Text Document called ArenaNet.log and scroll all the way to the bottom. Starting from the bottom, find the first line called —> Crash <— and paste it here

That should hopefully shed some light about the issue you’re having.

If that pastebin crash report was copied prior to the deletion of BGDM or ArcDPS, I can confirm that they are not the issue. If they were the cause of your crashes, a line saying Module: d3d9.dll would show up