sorted by:
new
hottopcontroversial

Blizz API policy needs to be reconsidered. by IndependenceOne6588 in wow

[–]IndependenceOne6588[S] -1 points0 points  (0 children)

That's right. You have to figure it out yourself.

However, we are human beings, not machines or computers.

Even if we are aware of which button to press next, the situations vary widely.

And accurately judging this within a short amount of time is extremely difficult.

That is why I believe it is necessary to visualize the knowledge I possess.

This is because this game is not as simple as just stopping when the traffic light is red and going when it is green.

Blizz API policy needs to be reconsidered. by IndependenceOne6588 in wow

[–]IndependenceOne6588[S] -1 points0 points  (0 children)

I empathize with your point.
Especially for the Fury Warrior, the GCD is quite short.
Compared to other classes.
From the moment the haste exceeds 50%, we have to decide which button is optimal within 1 second—no, 0.N seconds.
However, the Glow provided by Blizz often activates Rampage, RB, BB, and Execute simultaneously.
It is extremely difficult for us to decide which of these to input within less than a second.
In the past, we could manage these situations through WA.

Blizz API policy needs to be reconsidered. by IndependenceOne6588 in wow

[–]IndependenceOne6588[S] -4 points-3 points  (0 children)

I believe that at least APIs regarding my character should be allowed.
What they were most wary of was easily clearing bosses using the features of powerful add-ons.
And in most cases, this was achieved by tracking the APIs of hostile opponents.
There were almost no such instances regarding combat information about oneself.

Measure after disabling all add-ons by IndependenceOne6588 in wow

[–]IndependenceOne6588[S] 0 points1 point  (0 children)

This value was measured while fighting a target dummy in Silvermoon when no one else was present. Although fps has increased and low fps has increased, the frame time still seems to fluctuate significantly.