If I can only use a Tick event then I’m going going to be stuck with 100s of pins in my levels. Here’s an example of a simple wave spawner for 5 guys, with a wait for tick between each that uses the Tick Event and a Gate
Zoomed in:
Zoomed Out:
Now I do have a way of streamlining the spawning (which is why I didn’t want to get bogged down in my prototype methods) so that I only need 1 tick event per wave, but there will also be different wave variants depending on the difficulty setting and there will be alot of these per level.
It’s been suggested that I use a counter system, but as far as I can tell, such a system would be pointless because you’re always going to need a Recieve Tick event to drive the check or you’re stuck using time (and not frame based) delays to recheck the counter periodically.
And I cannot incorporate an Event Recieve Tick into a Macro either, so if I want to add Tick delay between checks in an array then I am also dependant on a tick event
The only way I can see to remove the dependancy on an excess amount of Sequence Node outputs coming off after a Event Recieve Tick is to have a Wait For New Tick / Wait For Tick To End node.
When it comes to AI, I won’t need as many pins, but then a Node would slot easier into arrays.