You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are you running the latest release of Aurora? If you're using the Twitch updater, make sure the release type is set to "Release" unless told otherwise.
When using both Aurora and Classic Quest Log, the font is skinned but the background is not, resulting in the quest log being illegible (please see screenshot below). Would it be possible to either skin the background too or have an option to not skin its font at all? (Maybe an option to not skin quest log?)
Steps to Reproduce
Use Classic Quest Log addon and Aurora together
[Second Step]
[Other Steps...]
Expected behavior:
It used to be legible before. The font wasn't skinned.
Actual behavior:
The font is skinned but the background is not, making it illegible now.
-- If you recived an error, place it here.
-- Separate them if you have more than one.
Additional information
Problem started happening recently, didn't happen in an older version of Aurora: [Yes]
Problem can be reliably reproduced, doesn't happen randomly: [Yes]
Screenshots and GIFs
Installed AddOns:
Classic Quest Log
The text was updated successfully, but these errors were encountered:
Prerequisites
Description
When using both Aurora and Classic Quest Log, the font is skinned but the background is not, resulting in the quest log being illegible (please see screenshot below). Would it be possible to either skin the background too or have an option to not skin its font at all? (Maybe an option to not skin quest log?)
Steps to Reproduce
Expected behavior:
It used to be legible before. The font wasn't skinned.
Actual behavior:
The font is skinned but the background is not, making it illegible now.
-- If you recived an error, place it here.
-- Separate them if you have more than one.
Additional information
Screenshots and GIFs
Installed AddOns:
Classic Quest Log
The text was updated successfully, but these errors were encountered: