WowAce

Released a new version to fix the .toc file typo that was causing the addon to fail on load for people if AceHook-3.0 wasn't loaded by another addon.

Correct. Once fixed, it should reappear in Titan panel. Also, as Maximus reported, if you install Ace3 as an Haddon in the meantime it will start working again.

Actually the package does include AceHook3.0 in the Libs folder; .pkgmeta was updated correctly.  What I screwed up was setting the path to it in the .toc file with a dumb copy paste error and so it can't find the lib to load it.  That's why if you have any other addon that gets that lib loaded for Ailo (like Ace3 as a standalone) you don't see the error.  I won't have repository access for a week or so; Starfox will have to make the fix for me
from: Libs\AceEvent-3.0\AceHook-3.0.xml
to: Libs\AceHook-3.0\AceHook-3.0.xml

I apologize for the inconvenience.

I'm not the author, so I can't address all your issues, but I'm familiar with some parts of how the addon works.

It does track weekly VP cap, its just not particularly clear that its doing it.  If you have Track 'Daily Heroic' checked, you'll get a column whose header is 140 and the VP icon. That's actually tracking your weekly VP cap in terms of the number of heroics it would take to get capped.  So, for example, I'm currently on a character sitting at 400 VP and the number is 4 (4x150 = 600 VP to cap me). For another character I have who hasn't collected any VP this week the number is at 7.  The problem is that the name in the options ui and the header in the tooltip still reflect the old days when it was tracking whether you'd gained the 140 VP for running a daily heroic and that needs to get updated and made clear as too what its tracking now.

I also have a character I haven't logged into this week and he still says 2 in that column so I'm also seeing the issue of old data only gets purged on a character by character basis. Would be nice if that got fixed.

As for LFR, I've just done some research and we can calculate the number of of bosses left to kill with the following:

4 - select(2, GetLFGDungeonNumEncounters(416))  -- The Siege of Wyrmrest Temple

4 - select(2, GetLFGDungeonNumEncounters(417))  -- Fall of Deathwing

If starfox doesn't get LFR support in soon, I'll probably take a crack at adding it in myself.

The recent updates should hopefully have addressed most of detvarjannik's concerns.  We're tracking the LFR raids and should be handling all of the weekly type resets better now (there's a dropdown letting EU users change the day of week from Tues to Wed but still I need to add some auto-detection for that). For weekly VP you still have to just see whether the count of heroic randoms you can run is 0 or not but I have plans for adding in the options to have VP and Conquest point totals shown (with the option to choose whether it shows amount gained this week or amount left to gain for cap).

Has the latest version fixed problems for you with regards to the daily random pvp reward? I don't pvp and so haven't really tried testing it.

Also, would it be useful tracking rewards related to the weekend battleground? I believe there's a conquest point bonus for winning that once, correct?  How does that work, can you only get the bonus once per BG weekend (so just treat it like a weekly quest/reset) or can you get it once per day during that weekend?

NOTE: this reply is supposed to be for comment #92, but curse's reply system is jacked up and insists on turning it into a reply to comment #90 instead.

Nyao - thanks for the catch with regards to line 789. That's definately a bug and I'll check in for a fix for it. I have to disagree though with what you said about GetRandomBGHonorCurrencyBonuses() always returning true. I used the chat prompt to run (without the quotes) "/run print(GetRandomBGHonorCurrencyBonuses())" and the results were "false 270 100 45 0".