Faster Bundle Inputs

I went over this with grazer a while ago, but he never seemed to go and fix it. You may of realized that if you send an always into a bundle input and into a nor gate, the nor gate still outputs. This is because according to grazer: Bundle inputs are meant to be triggers, which I think means that they can only trigger every 2 frames.

This would be a minor change but would be very nice for more complex logic and would let me make what I’ve been trying to make.

4 Likes

This is because the position inside the bundle is using the same positions outside the bundles (think of the behaviors inside the bundle as ghost behaviors outside the bundle).

It’s actually a complex thing to resolve because the behaviors are scanned in order based on position.

Bundle 1:

Bundle 2:

So with this information, you can already have faster inputs in a bundle; you just need to know where to put behaviors inside the bundles for the best performance.

3 Likes

I tried this, it doesn’t work for me. Does it need to be at the exact y pos of the other behaviour?

It’s not y, it’s x position because they need to flow from left to right.

Copy the input location and paste it into the bundle and you have to move the gate to the right of that.

Each always going into the bundle was copied individually to represent their location.

I can also show you if you have a link to your game.

I’d like to keep the idea secret, but I don’t know what else to do.

it’s in the One (3) Bundle

Alright, so I copy this always

image

When I paste it in the bundle, it’s here

image

I move everything to the right of this always (Not moving the Always) and straiten out the NOR gate.

And then it works.

1 Like