Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Queue Lock Threshold Applies To oGCDs #102

Open
ManagerWoW opened this issue Aug 12, 2023 · 0 comments
Open

[Bug] Queue Lock Threshold Applies To oGCDs #102

ManagerWoW opened this issue Aug 12, 2023 · 0 comments

Comments

@ManagerWoW
Copy link

The Queue Lock Threshold is currently bugged and allowing oGCDs to take priority and interrupt the queue. The Queue Lock Threshold should only apply to GCDs.

Ideally you would want to set the Queue Lock Threshold to 0.1 so you have the most amount of time to change your GCD at the last second if needed. However since it currently lets oGCDs take priority and interrupt the queue, this can cause major clipping issues. This is most apparent on Monk which spams an oGCD nonstop and relies on the Queue Threshold (usually 0.6-0.7) to prevent it from clipping.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant