Pick All / Create Bug

They do.

The logic is pick something, or somethings, and do something, or things to those objects.

Not and some other objects that weren't picked.

Picking at creation is a special case meant to make things easier, trying to exploit that even more is the issue.

It's not about exploiting anything, newt. It's about expecting some logic to work. If I want to pick everything that is created, I don't want to wait because it isn't fully available when I create it.

OK, ask Ashley if updating the sol every event, and sub event causes issues.

Ask him if he wants to add to add code to check if the sol needs to be updated every event.

He doesn't- he already state that.

There could be other ways though. Just because something is difficult to fix, doesn't mean it shouldn't be attempted.

And then when checking instance list, cycle through the would-be indices- if they are greater than the instance list length, then check the new object list instead?

This is also extra work that would add a great deal of complexity and degrade the performance of all projects, just for this corner case.

Ashley , How does the current method increase performance?

Is there some kind of code example you can show to help illustrate the issue? I'm just interested in understanding it.

It might break the project if changing the rules of SOL.

I used my instance group plugin to store the (picking) instances, no matter they are new created instances.

Designer might have similar functions by using official dictionary plugin, to store the UID of instances at the key, then using

"condition: for each key" (dictionary) + "condition pick by UID" to pick them in sub events.

That looks really useful rexrainbow , do the instance groups get updated automatically if an instance is destroyed?

Prominent

It will.

Ashley , How does the current method increase performance?

Because not doing work is always faster than doing work.

thanks rexrainbow , I just tried it and it works exactly how I want.