WowAce

In reply to Selthi:

 Thanks for the heads up; kind of nice/surprising to know that anyone else actually uses this heh.  I'm having all sorts of trouble getting the packager to include that lib. The other option instead of commenting that line out is to find LibDataBroker-1.1 in another addons list of libs and copy it over into this addons libs folder.

Going to try to find help for this; if I can't get it fixed in a couple of days then I'll comment out the feature :(

@Pathbris

I've released a new build which fixes the issue of mythic dungeon choice no being saved by set all

@Pathbris

Thanks for the information. It was working in HFC for me after the prepatch so it seemed likely it was still working as intended. I'll look into it and figure out what's changed.

@Pathbris

I guess I forgot to bump the toc number so the game considers it an out of date addon, but as far as I know, it all still works. I'll bump the toc and release a new version.

What's the other addon? I set my button positions relative to the journal's last button; they're probably doing the same thing. I'll figure something out.

You know that Otis lets you set prefered loot spec per boss, right?  I <sniff> I can't believe you're seeing another loot spec addon behind my back <sob> how could you!?!

AutoLootSpec actually shifts their position down by a fixed number of pixels if they see that we are loaded. I've made a change so that if we see that they are loaded we'll disable all of our loot spec code. The arrows will then be higher and the auto loot spec button will be uncovered.

@Aisenfaire

Gah! my apologies. r14 definately had a big fat bug where we didn't clear the restore data after doing the restore and so we'd do it again and again at the start of every fight. But r15 was supposed to fix that and handle those cases better ...

I did, after taking another look at the code, find what could have been the bug - we should clear the restore data anytime the user manually changes their current active loot spec.

So, just to be clear about how Otis works, lets say you had specified a preference for feral for all of the SOO bosses in the dungeon journal but when you entered the dungeon your loot spec was either set to resto or was set Current Specialization which resto because you were actually running in that spec.

What should happen is that at the start of every fight (or in the case of galakras not until she actually shows up at the end of the fight) we would change your loot spec to feral. Once loot was finished, we'd shift you back to resto. On the next boss the process would repeat.

Things are more complicated when you die, especially because of world bosses. Anytime you die (or dc) the restore happens when you next enter combat. We'll restore and then try to identify the fight. So, trying a boss again after a wipe, you would enter the fight with feral as active loot spec, restore back to resto (clearing the restore data), then we'd identify the boss and set a restore point for resto and change the spec to feral again.

The bug I just found would manifest if, after a wipe, you manually changed your active loot spec (which Otis set to feral) to guardian. The next time you entered combat we'd restore to resto (before overriding again if it was a boss you had set a preference for).

That doesn't quite sound like the problem you're having (r14's failure to ever clear a restore meant that the version would always keep jamming you back to a specific spec no matter what you did).

Here's a couple of things you can try to help if you're getting weird behavior. On the chat line type: /run Otis:state()

If there are values printed for savedBoss and savedSpec that aren't nil then it means that Otis saved off savedSpec as a restore point when it changed your loot spec for savedBoss. If you think that restore point is or will cause you problems then you can clear it with: /run Otis.db.char.savedLoot = nil