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

Plater "Display Cooldown" re-enable itself after reload #397

Open
Sebastian1989101 opened this issue Oct 30, 2022 · 4 comments
Open

Plater "Display Cooldown" re-enable itself after reload #397

Sebastian1989101 opened this issue Oct 30, 2022 · 4 comments
Assignees
Labels

Comments

@Sebastian1989101
Copy link

Sebastian1989101 commented Oct 30, 2022

Give us a clear and concise description of the problem, and what you expect to happen

Disabling this option works but it re-enables itself after a reload.
Screenshots hosted on Imgur

Do you have any steps to reproduce this issue?

Disable "Display cooldown text" for Plater, then use /reload

Are you getting any error messages?

No

What version of OmniCC are you running?

10.0.1

What version of World of Warcraft are you on?

10.0.0.46366

What other addons are you running?

Plater, BigDebuffs and Details

@Tuller
Copy link
Member

Tuller commented Oct 31, 2022

I believe that you should be disabling within plater itself

@Sebastian1989101
Copy link
Author

I believe that you should be disabling within plater itself

Then this option should not exists. Because it makes no sense then. On the other hand, I already have a cooldown displayed from my Plater profile (Better Pixel Perfect) which I want to keep. So it's no option to disable it there. Just the OmniCC 2nd countdown is too much. Also this option works until I reload (which just re-enables this options). So the implementation is already there just the disabled state for this option is not properly stored / used.

@Tuller
Copy link
Member

Tuller commented Oct 31, 2022

Plater injects the rule into OmniCC in this case.

@Araldwenn
Copy link

Any chance to have this bug fixed ?

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

No branches or pull requests

3 participants