it registers a change and will trigger any wires when connected to the property when the game starts. In this way, it can also be used as a lifecycle device.
Yup. Like I said, just put much better. Can’t believe I forgot that this guide existied.
Lifecycle:
Property (global) → Mark as changed on game start.
When property value changes…
More clean:
Property change on game start. Wire that to a trigger 2 times. First time should be for game start, second time should deactivate. Saves a property.
Also only for game start life cycle.
bump because this is a very useful and underrated setting
people who don’t notice this might spend over 500 memory making a contraption that does the same thing (which i did once)
edit: ahhh @Haiasi stop liking my posts
Can someone make a guide like this, but instead of the property setting, it’s the notification sending scope? It’s really helpful.
I could try…
Wait, you mean like who it sends to?
Sure! Just to be sure, you know which setting I’m talking about, right?
You’re talking about the scope (who can see) of the notification, right?
Yeah, the sending scope option in all options. It saves a relay.
Okay, I’ll make it…
I’ll try…
No, scope is easy and well known about. I’ll post a picture in a couple minutes.
If you can’t or don’t want to, I could.
This one, at the bottom of all options.
Yeah, that’s sorta like scope. I’ll make it!
Guide or Devices?
Eh, I don’t care. It’s your guide.
hey, is that a different me over there
I don’t know if anyone mentioned this, but it could be used as a 30-memory efficient start game lifecycle
yes