You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When first loading up PKHeX, if you try to import a set with ALM, it will behave as if UseCompetitiveMarkings is set to False. But then once you open the plugin settings (don't need to do anything other than open them) and you go import another set, it behaves as if UseCompetitiveMarkings is set to True (assuming it is in fact set to True)
To Reproduce
Steps to reproduce the behavior:
Import a set with ALM without opening the plugin settings first. Check the markings.
Open the plugin settings and close them.
Import the same set and look at the markings again.
Expected behavior
I expect that ALM respects the UseCompetitiveMarkings setting when it's set to True without having to open the plugin settings first.
Describe the bug
When first loading up PKHeX, if you try to import a set with ALM, it will behave as if UseCompetitiveMarkings is set to False. But then once you open the plugin settings (don't need to do anything other than open them) and you go import another set, it behaves as if UseCompetitiveMarkings is set to True (assuming it is in fact set to True)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect that ALM respects the UseCompetitiveMarkings setting when it's set to True without having to open the plugin settings first.
Screenshots
Video: https://github.com/architdate/PKHeX-Plugins/assets/6857825/befcc292-40e1-4a79-8188-23c15db56f24
Additional context
This was discussed in the PDP Discord on 10/4/2023.
The text was updated successfully, but these errors were encountered: