File Details
v2.1.1
- R
- Apr 15, 2026
- 155.22 KB
- 13
- 12.0.1+1
- Retail
File Name
PetBuddy2-v2.1.1.zip
Supported Versions
- 12.0.1
- 12.0.0
Changes
v2.1.1
- Added missing
avatar_url(pet logo) to all Discord release, beta, alpha, and failure notification embeds
v2.1.0
- Added a standalone PetBuddy2 minimap icon using the
logo.tgaasset. Left click toggles the PetBuddy2 frame, right click opens the options menu, and the icon can be dragged around the minimap edge. Saved position persists across sessions. - Added a "Show minimap icon" toggle to the options menu so the icon can be enabled or disabled without relying on external minimap-button managers.
- Implemented non-interfering PetTracker integration: when PetTracker is installed, PB2 defers to its live zone data and skips the native journal quality scan entirely, so it never mutates
C_PetJournalfilters or fires spuriousPET_JOURNAL_LIST_UPDATEevents that would thrash PetTracker's own listeners. - Cached the native zone quality map and invalidated it on
PET_JOURNAL_LIST_UPDATEso PetTracker-less users rebuild at most once per collection change instead of once per zone refresh. - Added PetTracker to
OptionalDepsfor deterministic load order when both addons are present.
v2.0.1
- Normalized non-documentation asset and UI file paths to lower case, including the
media/directory and XML layout filenames, while intentionally leaving documentation files and the addon manifest naming alone. - Updated in-repo asset references to match the lower-case path cleanup so TOC, XML, Lua media registration, and button/icon paths stay in sync.
- Hardened the release workflow Discord notification path so webhook responses are awaited and validated instead of failing silently.
- Added
workflow_dispatchsupport plus manual release inputs to the release workflow so Discord notifications and packager runs can be retried without cutting a new feature tag. - Updated release workflow notifications to include the CurseForge download link directly in Discord.
- Polished README / changelog / releasing docs so they reflect the current Rematch flow, rerun workflow, and post-release troubleshooting guidance more accurately.

