ID:2908624
 
BYOND Version:514
Operating System:Windows 10 Home
Web Browser:Chrome 120.0.0.0
Applies to:Dream Maker
Status: Open

Issue hasn't been assigned a status value.
Descriptive Problem Summary: Flicking an icon state on an icon that doesnt have this icon will make the icon invisible but will not make the overlays invisible. this is not the functionality that use to exist where if you flick an icon state you dont have it it SHOULD default to the null frame

Numbered Steps to Reproduce Problem: https://discord.com/channels/725444629172060262/ 725458744711839873/1197037562922029056

Code Snippet (if applicable) to Reproduce Problem:
https://discord.com/channels/725444629172060262/ 725458744711839873/1197037562922029056

Expected Results: dont make the mobs icon invisible when flicking a state that doesnt exist. fall back to null state like before

Actual Results: mobs icon goes invisible

Does the problem occur:
Every time? Or how often?yes
In other games?yes
In other user accounts?yes
On other computers? yes

When does the problem NOT occur? never

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)

Workarounds:

I'm not sure this is a bug at all. If there's been a change of behavior, can you narrow down when it appeared?
how is this not a bug? the overlay does not go invisible but the icon itself does? definitely a change in behavior ill have to narrow that down somehow
If the overlay doesn't inherit the icon state, then it isn't expected to change. The main icon going invisible for lack of a matching state however is a potentially valid situation.
seems incredibly silly to make the icon go invisible, when it definitely did not in the past, for any period of time. and why is the flick even happening for a few seconds if the state doesnt exist
In response to Lummox JR
Lummox JR wrote:
If the overlay doesn't inherit the icon state, then it isn't expected to change. The main icon going invisible for lack of a matching state however is a potentially valid situation.

This isn't valid behavior because it's entirely inconsistent. For example, if Zagros' icon_state only had one direction when calling flick on an invalid icon_state, it would not disappear.

This also does not happen when an atom's default icon_state is not an empty string.
In response to Zagros5000
Zagros5000 wrote:
seems incredibly silly to make the icon go invisible, when it definitely did not in the past, for any period of time. and why is the flick even happening for a few seconds if the state doesnt exist

If it didn't do so in the past then I need to know when it changed. I don't recall it ever being different.
ah maybe it didn't happen in the past. I think my project is just convoluted enough now where this bug is noticeable now