4*Black Widow - Lights Out [Fixed]

Noticed that the in game text popup for Black Widows ‘Lights Out’ power does not fit in the text balloon, font size needs to be reduced a little. (Steam version)

//Edited Title -Brigby

I think that’s the same issue reported in

https://forums.505go.com/discussion/72483/font-size-of-black-widows-lights-out-investigating

It is. And as I’ve previously noted, it’s kinda odd that it’s taken this long for what should be a minor, easy fix. @Brigby, any news on this?

With so many thousand stuffs to fix in the game, probably it is not in the top priority list yet. Afterall, It’s merely a visual change that affects probably less than 5% of the players.

Fixing font is easy and simple. But is it urgent and important?

Between fixing bugs, making improvement to MPQ and changing a visual font, changing visual font, to me, is way down at the priority list. Maybe when the devs can squeeze in some time for a bonus quick fix like this, they will do it.

Fair enough - it makes sense it wouldn’t be a high priority. And intellectually I know that bugs are triaged and prioritized and handled in a manner that (hopefully) deals with the worst ones first. But, I don’t know, still feels weird to me that this easy and simple issue hasn’t been fixed. I recognize that’s not necessarily fair, but there you go.

@mbaren
@HoundofShadow explains it pretty succinctly. We do prioritize fixes / changes based on urgency or importance, which means a visual change like font would probably rank lower on the to-do list.

Rest assured though, I’ve already passed along this issue to the team, and when bandwidth opens up, then hopefully this will be a quick and easy fix for them to add into a patch / build update.

Makes sense - thanks!

With the much appreciated fix to Okoye’s Spear blocking tiles, hopefully this will get looked at too.

That would be nice :slight_smile:

Bringing this up again, as the new 4* Bishop had the same issue and was fixed pretty quickly.

@Freelancer
Thanks for the reminder. I’ll bring it up again.

This appears to have been fixed.

@mbaren
Thanks for the heads up. After checking, I can confirm this is officially fixed.