# ProjectAzilroka

## [1.75-54-g0ec65cf](https://github.com/Azilroka/ProjectAzilroka/tree/0ec65cf279a0983c791835f62e79b03533d4a3c3) (2021-05-22)
[Full Changelog](https://github.com/Azilroka/ProjectAzilroka/compare/1.75...0ec65cf279a0983c791835f62e79b03533d4a3c3) [Previous Releases](https://github.com/Azilroka/ProjectAzilroka/releases)

- Update PA to ToC Parser  
- Remove PlayerChoicFrame from MovableFrames  
- Only cap the inverse values when inverting priest color.  
- Cap inverse to 0.35, 0.15 is too dark.  
- Untested: Also add a mover for Tukui for the tdBattlePetScript auto button.  
- Moving this to AddOnSkins.  
- Also grab breed info if the icon isn't available yet for some reason, saw that happen in Mechagon, restarting the fight made them appear so it appeared its some race issue.  
- Revert "Cache this."  
    This reverts commit 7599609c779b15c3f70e117a4e762e0d021fb37b  
- iFilger  
- Cache this.  
- Only call :GetBreedInfo() if we haven't already recorded it for this battle.  
- Add a caching mechanism to breed info to save us potentially hundreds of function calls over a battle.  
- Typo.  
- We don't need to create new tables here instead just pass the one that already has the necessary keys.  
- Noticed that when fighting a poor pet, PetTracker incorrectly identified it as B/B while BattlePetBreedID correctly identified it as P/P.  So now abusing the BattlePetBreedID options to get it to return the species number, which is then passed to PetTracker for the icon, rather than relying on PetTracker to report the species, as it can be wrong.  
- workflow  
- Typo  
- Add Wago AddOn Support  
- Fix pkgmeta  
- Make this an API too.  
- workflow  
- ToC Changes  
- Rename Big Buttons to Sunsong Ranch Farmer  
- ACH  
- Cutaway is an ElvUI specific oUF element.  
- NUI will now register EnhancedShadows to PA.ES so no longer needs to be  
    special cased.  
- Add an API to block healing in EPBUI.  
- Move the license and readme back to the root.  
- LibDataBroker  
- Ace3 Submodule  
- Remove Submodules  
- I wanna mess with Azil and shift this first.  
- Add new options for the trainer and wild health thresholds, again with the previously hardcoded values as defaults.  Also add a way for external addons to override the threshold for trainer battles.  
- 1.76  
- Add settings for the various oUF text fields in EPBUI with the previously hardcoded tags set as the default value instead.  
- Add pbuf:smartlevel that hides the level if a pet is max level and use that instead.  
- Create a ClipFrame for the cutaway health ala ElvUI for the same reason they do, to stop it from overflowing out of the side of the frame.  
- Merge branch 'XCreative-master-patch-15363' into 'master'  
    Fix: bump toc version for latest wow patch (90005)  
    See merge request Azilroka/ProjectAzilroka!16  
- fix: bump toc version for latest wow patch (90005)   
- ACH  
- Don't grab my InstanceDifficultyFrame.. bad Azil :badboi:  
- Swap the buff and debuff positions so they mirror the nameplates otherwise it looks very weird.  
- @lucky  
- Renamed myself again.  
- Hmm try this @Luckyone.  
- Only set colorSmooth when colorhealthbyvalue is enabled in ElvUI, enabling custom health colors to work.  When this is the case enemy pets will be colored with the oUF hostile reaction color.  
- Add support for the other ElvUI UF health backdrop options, though colorclass and colorbyhealthvalue remain the only supported health colors.  
- Add support for ElvUI UF color options (notably colorbyclass and colorbyhealthvalue) to EPBUI oUF frames when using ElvUI.  
- EPB Revive Bar update.  
- Torghast Buffs - Better Defaults  
- PetTracker switcher is no longer split so check their settings instead.  
- They all disappeared after I changed zones after my last change, this seems to fix it, stupid buggy minimap buttons, I dont blame you for dropping yours @Merathilis.  
- SquareMinimapButtons still fighting me only showing 4 buttons out of the 24 or so it should sometimes so trying something else.  
- Explicitly set SMBNumChildren to 0 because the Lua interpreter is apparently confused by the phrase x > (nil or 0)  
