Output Event - setProperties, saving you time!

[Syntho]

Good idea, but you can just use Disappear -1 and Disappear 0.

[Ad Bot]

[Healbadbad]

Good idea, but you can just use Disappear -1 and Disappear 0.

what if you want two to be unchecked on multiple bricks and not all three hmm?

[Mateo]

what if you want two to be unchecked on multiple bricks and not all three hmm?

This.

[Syntho]

Still stuff.

[Mateo]

Why is it stuff? This will save me a lot of time.

[Trinity Armory]

As I said earlier, it helps a lot with eventing multiple 'button makes area' events (scripts, events, does it matter? :p)

[jirue]

disappear  | -1 |

Then when you want it back

disappear  | 0  |

Oh well.

[Regulith]

Download get!

This is a good idea, no matter what people say.

[Syntho]

disappear  | -1 |

Then when you want it back

disappear  | 0  |

Oh well.

This is why it's stuff.

[Regulith]

This is why it's stuff.

This is where this comes in.

what if you want two to be unchecked on multiple bricks and not all three hmm?

[MtnDew]

<3

[NPCKiller]

Heart x2 I love IT

[M]

This is why it's stuff.

What if you need to keep raycasting for onActivate events?

onActivate Self disappear -1
onActivate Self setRaycasting 1

setProperties 1 0 0

2 events vs 1 event. You're saying it's stuff simply because it can already be done, but failing to see the reason it was made. No scroll-to-letter functionality on event lists means I often spend quite some time scrolling through the lists on servers bogged down with variables (v4*) and database events to find the events. * Future-proofing. You'll see.

[Healbadbad]

-snip-

pure ownage