Guild Wars 2

As per link:
“We have no problems with players using a 3rd party tool whose scope is only to collect and visualize combat data gathered directly from the game client. Anything beyond that scope is still considered a violation of the User Agreement.” – Chris Cleary

“You are correct. Combat data is defined as any information that is created due to the usage of skills or impact on players due to skill usage (by the player/s or an outside source).
Edit/Update: These statements are particularly targeted at a “DPS Meter” or functionality built around the capture of combat data. Features outside of that most likely fall under “Quality of Life” changes and should be removed from DPS meters if they want to be considered compliant with our rules." – Chris Cleary

It’s an official response. Hope this topic doesn’t get locked, I’m just letting you guys know directly from the AMA opened by Mo.

Cheers.

@Edit
Chris Cleary opens up for memory-reading tool creators to contact him for further explanation about what is compliant with the rules, per link:
“We engaged in significant internal discussion about DPS meters even before we launched raids. Our discussions initially revolved around what we were going to do, but ultimately we wanted to see where the community was going.
We were not absolutely clear on our stance in relation to DPS meters because the ways they would be used (or potentially abused) was still evolving. In such a case, where we have not made a definitive statement yet are continuing to discuss internally, we did not want to take action against players until we have made our stance clear.
Now that we have set the bar and tool creators know what is acceptable, we are hoping that tool creators will make adjustments to their tools to make them compliant with our requirements and more accessible to a wider audience.
We will give our community plenty of time to make this adjustment before considering any action directly against tools or players that use them.
Edit: Tool creators, if you are unsure if a feature you have created or want to create is in violation of these guidelines, you can contact me directly.” – Chris Cleary

Gear checking is against ToS, per link:
“Yes. Player equipment (besides Sigils’s activating and the boons/damage associated with them) does not fall within the realm of combat data. Others have implemented a solution for this using the APIs we provide rather than client data, I would suggest using that instead.” – Chris Cleary

Logging has been discussed internally too, per link:
“This is a good question, and one that we have asked ourselves internally. There are a number of development/design challenges with this option which has made it difficult to move forward with (but not impossible). We want to see where the community goes after we have given it a clear direction before making any development choices.” – Chris Cleary

There are a number of development/design challenges with this option which has made it difficult to move forward with (but not impossible)

The combat log must be an absolute mess for him to say that, considering simple text logging should be trivial to implement. Considering the combat log doesn’t even list everything, it probably is, though he could have also been thinking about a party-wide combat log.

Yes yes yes yes.

TYsooooooVM, ANet devs! :o <3

Healix.5819:

The combat log must be an absolute mess for him to say that, considering simple text logging should be trivial to implement. Considering the combat log doesn’t even list everything, it probably is, though he could have also been thinking about a party-wide combat log.

I bet it’s some kind of async event-listener thing which providers data to the HTML-based UI components. But even then, the client itself should be able to dump the data out as it is passed through the internal event chain for processing, though maybe it is nontrivial to know what would be “combat log” and what isn’t.

WoW had COMBAT_LOG_EVENT_UNFILTERED, which was amazing for a modder, albeit dangerous in that you had to make sure your hooking code is super lean.

The skies have parted. An actual direct comment about a third party tool. A comment that doesn’t leave one wondering “what did they mean by that?” thought I would never the day.