VaultPing 1.2.8

Fixed

• CRITICAL: Fixed activity classification - dungeons (type 1) were being misclassified as world content
• Fixed heroic dungeons not tracking correctly (now properly classified as "D" instead of "W")
• Fixed activities not updating properly after login/reload
• Fixed progress showing as 0/0/0 even after completing vault activities
• Fixed SafeGetActivities() parameter order (now tries without parameters first, which works on more clients)
• Fixed syntax error with goto statement (replaced with proper if check)

Optimized

• Reduced ticker attempts from 15 to 10
• Increased ticker interval from 1.5s to 2.0s (less frequent polling)
• Added early exit for ticker when data loads successfully (stops immediately instead of running all attempts)
• Added progress caching (2 second cache) to prevent redundant API calls on tooltip hover
• Added event throttling (max 1 refresh per second) to prevent spam
• Removed QUEST_LOG_UPDATE event (fired too frequently on every quest update)
• Removed UPDATE_INSTANCE_INFO event (not reliably helpful)
• Overall ~50% reduction in ticker iterations and ~90% fewer progress calculations

Technical Details

• Enhanced debug output (/vpd) with more detailed API function availability checks
• Added numeric type classification as primary method (most reliable):
  • Type 1 = Dungeons (heroic, mythic, M+)
  • Type 3 = Raids
  • Type 6 = World/Delves
• Improved ClassifyActivity() function with correct type mappings
• Added cache invalidation on button updates to ensure fresh data
• Better throttling and debouncing to reduce resource usage

Performance Impact

• Significantly reduced CPU usage from fewer API calls and event handling
• Reduced memory overhead from caching and early ticker termination
• Faster initial load while using fewer resources overall