Event banner #43

Closed
opened 2025-07-30 23:38:38 -04:00 by idoldange · 2 comments
idoldange commented 2025-07-30 23:38:38 -04:00 (Migrated from github.com)

result in ERROR when change id to 3557620 (Blue archive community)

result in ERROR when change id to 3557620 (Blue archive community)
Xenon257R commented 2025-07-31 09:16:05 -04:00 (Migrated from github.com)

From a cursory look, it seems like this error is occurring because Blue Archive on Steam has a default header image with a non-standard URL. If this analysis is correct, the EventBanner should function (after a refresh) as long as Blue Archive's most recent update has a unique header image and only break when it doesn't, i.e. the Skin tries to download their default header.

I will need time to figure out how to determine the correct banner image URL to download instead of assuming that every game follows a default URL scheme. An update will be provided when I am able to make progress, hopefully with a patch that resolves the issue.

From a cursory look, it seems like this error is occurring because *Blue Archive* on *Steam* has a default header image with a non-standard URL. If this analysis is correct, the EventBanner should function (after a refresh) as long as *Blue Archive*'s most recent update has a unique header image and only break when it doesn't, i.e. the Skin tries to download their default header. I will need time to figure out how to determine the correct banner image URL to download instead of assuming that every game follows a default URL scheme. An update will be provided when I am able to make progress, hopefully with a patch that resolves the issue.
Xenon257R commented 2025-08-10 22:55:38 -04:00 (Migrated from github.com)

I have just fixed the issue in the v.1.2.3 release. I believe this bugfix should prevent this type of issue from happening again. More importantly, this patch has new error handling that should in theory identify unknown errors with better details, which should make it easier to debug future issues.

Thank you for the bug report.

I have just fixed the issue in the [v.1.2.3 release](https://github.com/Xenon257R/blue-archive-rainmeter/releases/tag/v1.2.3). I believe this bugfix should prevent this type of issue from happening again. More importantly, this patch has new error handling that should in theory identify unknown errors with better details, which should make it easier to debug future issues. Thank you for the bug report.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Xenon257R/blue-archive-rainmeter#43
No description provided.