Two suggestions for Flash behavior

Hi Constructoids,

I think the following two conditions would make the Flash Behavior super-awesome:

1) Is flashing
2) Has flashing finished

Presumably, the runtime already knows this info, but we construct programmers can't check these conditions. Then we wouldn't need to use multiple additional events to count down a variable to keep track of when the player is no longer invulnerable etc.

Lastly,
I and many others would LOVE it if we could choose to flash either to invisible OR just a solid color... just by using the sprites current alpha channel and replacing all color data with a specified color.

Pretty please...... :)

Hi Ashley,

Thank you so much! This will really make temporary invunerability super easy to handle, less wasted events and variables. You rock!

for a fully animated platformer or fighting game player it would be a massive waste of vram and file space to have flashing versions of every animation etc...AH HA! How about flashing between two render modes! Like you can designate: appearance 1 and appearance 2 instead of just "visible" and "not", and each appearance could be set to either invisible or any of the current rendering modes (ink effects)

That would be incredible!

@Tokinsom,

The discussion about using frames of animation for flahing was specifically for solid color flashing, and NOT invisibility flashing.

The whole point of behaviors is to reduce the need for events. The whole point of Construct is to reduce production time and let people spend more time and energy being creative with the least programming grunt work.

I'm glad Ashley is making the already useful Flash behavior drastically more useful. Saving our time and effort so we can make better games faster ad with less events is never "entirely unnecessary"...in the same way that Construct is not "unnecessary" because we have C,Java, Action Script, Basic etc.

Brashmonkey wrote: @Tokinsom, The discussion about using frames of animation for flahing was specifically for solid color flashing, and NOT invisibility flashing. The whole point of behaviors is to reduce the need for events. The whole point of Construct is to reduce production time and let people spend more time and energy being creative with the least programming grunt work. I'm glad Ashley is making the already useful Flash behavior drastically more useful. Saving our time and effort so we can make better games faster ad with less events is never "entirely unnecessary"...in the same way that Construct is not "unnecessary" because we have C,Java, Action Script, Basic etc.

I know. I'm just saying that using extra solid-color frames is completely unnecessary as you will be able to do that with shaders and toggling a boolean variable. You also mentioned invincibility frames being difficult w/o the requested Flash Behavior features so I thought I'd chime in on that as well. Maybe I misunderstood what you said, if that's so then sorry.

Edited by Tokinsom - 26 Apr 2012 at 6:54pm