Coroutine does not work properly

[Kurt-Dekker]

Definitely a solution NOT WELL suited to coroutines!!

Here’s a solution for moving in a grid:

kurtdekker/proximity_buttons/blob/master/proximity_buttons/Assets/DemoMoveGridCell/DemoMoveGridCell.cs

Full project and demo scene at that same location, or just take the script and drop it in, hook it up per the instructions.

Coroutines are NOT always an appropriate solution: know when to use them!

Things to check before starting a coroutine?

The main thing to check before calling / making a coroutine is to ask yourself, “Does this even need to be a coroutine?” Generally, if your design requires you to call StopCoroutine(), then don’t make it a coroutine. If you just need something to happen a bit later, this is a more-robust approach: https://gist.github.com/kurtdekker/0da9a9721c15bd3af1d2ced0a367e24e If you’re flipping from one value to another, such as fading in, fading out, changing speeds slowly, etc., coroutines are an AW…

Heartbeat courutine fx

There’s never a need. As @PraetorBlue pointed out in a recent post of his, nobody NEEDS coroutines. They do solve a certain class of problem nicely however, primarily problems of sequencing a set of data or events to happen. Coroutines CAN be interrupted and restarted but doing so exponentially increases your chance of a bug, negating a lot of their inherent benefits. A lot of human behaviors are good coroutines: “Go take a shower.” So that breaks down to: get undressed start the shower …