Switching to a custom loadout without a base blizzard loadout results in weird behaviour
Numynum opened this issue ยท 1 comments
Reported in by strikkegenser
It looks like there's an issue in the logic when applying custom loadouts, at the very least when the base loadout has been deleted
TLM should either create a new loadout, or probably more preferably, just use the current loadout (if any) and set that as the base loadout
additionally, when retrieving loadouts, and checking for parent loadouts on the current character, the addon should check whether the parent loadout exists, and if it doesn't, then don't show it as a nested loadout (resulting in the order looking weird)