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

Disable the addon if logged in on the tournament realm to avoid live data being unintentionally modified #699

Open
Duckwhale opened this issue Feb 13, 2024 · 1 comment

Comments

@Duckwhale
Copy link
Member

Many times people have logged into the tournament realm and as a result have had items marked as collected on live realms afterwards. The result is usually confusion; the only way to get rid of the undesired settings is manually editing the saved variables - not ideal.

It seems that Blizzard provides a function to check whether the player is currently logged into the Tournament Realm:

  • IsOnTournamentRealm()

It would be prudent to completely disable the addon if this returns true, and print a message indicating why it's not working there.

@Duckwhale
Copy link
Member Author

Duckwhale commented Feb 13, 2024

Well, it seems that this API is not reliable at all:

it prints false for me on the tournament realm

Source: Discord

So much for that. Some other ideas:

  • Use the output of GetRealmName() and maintain a list of special tournament realms, e.g. AU Mythic Dungeons - not a fan
  • Finally implement the UI needed to help people remove those undesired entries - though they'd still need to check the FAQ
  • Report as a bug to Blizzard and hope they fix it before the advent of the next century - should probably do that regardless

That's all I can come up with right now. None of these options are particularly appealing, but maybe there's another way?

@Duckwhale Duckwhale moved this from It's finally happening! (WIP) to Soon™ in Timeline May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Soon™
Timeline
Soon™
Development

No branches or pull requests

1 participant