Could you elaborate a bit on why a Dictionary might be closer to my needs? That would help my understanding of learning how to choose best between these two storage objects.

Well, I haven't analysed your code too much (unlike blackhornet ) but a dictionary stores a text/number pair, and that's what you're doing.. Take it with a grain of salt.

if we filter out the negative ones, then that's really just the definition of bias.

And yet you want to filter out negative comments relating to the OP?

If people are told to ignore a post, that's only self-serving, as only the people who agree with the OP will post... Also if the OP is slightly controversial, then how can you not respond with your opinions? It's just human nature.

Does the attached capx help at all?

Why don't you Set size to (tokencount( Anagrams, ","), 2, 1) instead of Set size to (1, 2, 1) in event 1? You don't even need that, if you use push. Also a Dictionary might be closer to what you need.

You can stop individual objects from pathfinding. Perhaps you're picking all of your characters instead of just the one you want to stop. Or am I misunderstanding?

Nah, I had several goes at it and was still getting the glitchy behaviour. Then I realised it must be a timing issue and moved the code into single sequences of actions and that did it. It's not easy to get your head around events, and the timing of them, and the fact that multiple things can be happening at once (and 60 times a second!). And I'm still learning to let C2 do a lot of the hard work for me As seen by OddConfection 's first solution, there's always a simpler way.

Can you post a capx that demonstrates the issue? I'm not sure what you're missing as it looks like it should work from what you've shown. See the capx attached and compare it to yours.

Who says you can't make a cute game without any artistic ability?

We should totally put both of our lack of artistic ability together and make the next 'piano tiles' type hit

I've made an alternate example using the Timer behaviour:

Yea I was going to suggest for the Enemy to have its own timer. Except your guys stand facing the wall while they're waiting

Have a variable BulletsFired that you add 1 to after each bullet is fired. Have a condition that checks the variable, and if it's 10, reload and reset the variable. If you want to keep the count, have the condition check (BulletsFired % 10) = 0

OddConfection gave an elegant solution. I've learned from it and I think you should too. Yours doesn't work because of inherent timing issues. Hint: the System:Wait does not stop other events from running. Every tick.

Also you have some misconceptions. You do not need System:Pick All Enemy followed by System:For each Enemy You can remove these entirely and the logic is the same.

And I find any time I've used System:Wait I've introduced subtle timing issues, so I'd be careful of that technique.

If you're wanting to see how your type of approach might work, I've attached a capx. The basic approach is still yours, but it's greatly simplified.

[attachment=0:pbe087bp][/attachment:pbe087bp]

Cute

Does the trick and no pinning required