Props to @Shdwy for this one. As is the custom with @Shdwy, I made the most clickbait title. So here’s a pseudo trigger:
Bu- but isn’t that a counter? Nope. From now on, its a trigger. Its a trigger and it’ll always be the the little brother with all the attention. Think of it: in really simple-complex systems, aka hardware, a trigger has 3 purposes: storing data, receiving on a channel, and broadcasting on a channel. So we get receiving on a channel by using the increment. We get the broadcast by setting the target to 1. We make it repeatable by resetting it each time it hits 1, and it stores data by… hm… Lets think about that.
The counter’s number already is the data stored, so we have to get creative. Gimkit Creative. So deactivation is if it can’t broadcast. Therefore, we use decrement to deactivate it and increment after that to reactivate it. Therefore, we are done. Or are we? We can’t deactivate it multiple times like we can with a trigger because then we have to activate it multiple times. What do we do? We call it a feature, not a bug.
Coming up on episode 2
Pseudo Pseudo Trigger Properties!
Pseudo Trigger Properties (Difficulty 6/10)
The sequel!
