Yup. Like I said, just put much better. Can’t believe I forgot that this guide existied.
1 Like
Lifecycle:
Property (global) → Mark as changed on game start.
When property value changes…
4 Likes
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.
2 Likes
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
8 Likes
Can someone make a guide like this, but instead of the property setting, it’s the notification sending scope? It’s really helpful.
4 Likes
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?
2 Likes
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.
2 Likes
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.
1 Like
If you can’t or don’t want to, I could.
1 Like
This one, at the bottom of all options.
1 Like
Yeah, that’s sorta like scope. I’ll make it!
Guide or Devices?
Eh, I don’t care. It’s your guide.
1 Like
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
1 Like
