Releases: sbaildon/sInterface
Releases · sbaildon/sInterface
v0.3.1
v0.3.0
Supports 8.1!
Features
- Action bars are now scalable
Changes
- Option to disable details skin
- Remove configuration option for the objective tracker position whilst in a raid
- Filters feature removed
- Use effective level (scaling) for difficulty colour
- Don't add cooldowns greater than 10minutes to the cooldown bar
- Nameplates now use the same health colours as unit frames for improved consistency
v0.21.0
Features
- Support for additional power bars: enhance shaman maelstrom/mana, balance druid solar/mana
- New Azerite progress bar
Changes
- New style of power bar. Power bars now appear to hover over the units health bar, and are not quite full width.
- Progress bars (honor, exp, rep, azerite) now use Blizzard's animated status bars
- Readded support for emulate player resource frame
- Target nameplates debuffs are now much closer to the nameplate itself
- Removed artifact weapon progress bar (it's really hard to test since they've been disabled in 8.0)
- Removed new voice chat buttons from the chat box
Bug Fixes
- Fix some 8.0 tooltip issues:
- Remove the new embedded tooltip's backdrop
- Fix blue background GAME_TOOLTIP
- Text tweaks
v0.20.1
v0.20.0
Changes
- Support for 8.0, Battle for Azeroth
- sInterface now inherits the Blizzard game fonts, instead of providing its own. To change UI fonts, you'll need to replace fonts in the
Fonts
directory inside ofC:/.../World of Warcraft
. This was done to improve consistency with peoples user interfaces - Option to show zone name on minimap,
zoneText
- Skin details window when the frame is toggled
Bug Fixes
- Resource bars now anchor to a parent element, instead of UIParent
- Don't call SetPoint on nameplates when in combat lockdown
- Remove references to old embeds
Caveats
emulatePersonalResourceDisplay
is intentionally being ignored, because when it is enabled, there are problems with text not displaying on the unit frames. Fix to come soon.- Artifact resource bar is currently disabled because of API changes I've not managed to update.