Moroutines

Moroutines transfer work with coroutines to steroids! A lot of the things you stumbled over while working with coroutines have been improved and given to you wholeheartedly. Moroutines adhere to the philosophy of coroutines, but expand the functionality of working with them. 

Here are the disadvantages that coroutines have:

• Coroutines do not store information about their state (reseted, running, stopped, completed or destroyed).
• Coroutines cannot be paused/reset and then started while continuing its execution.
• No ability to wait (yield) pause or play coroutine.
• Coroutines do not know how to return a result.
• Coroutines cannot be grouped for easy control.
• A coroutine does not store information about its owner object.
• Game objects do not display information about the coroutines that are associated with them.
• No way to create an unowned coroutine.
• There is no way to wait (yield) the execution of several coroutines
• Coroutines do not have state change events.
• Coroutines B and C cannot wait (yield) for coroutine A at the same time.
• There is no way to add a delay (in seconds or frames) before starting an existing coroutine.
• Coroutines don't have names, they harder to filter and harder to debug.
• And other shortcomings.

Moroutines excludes the disadvantages listed above. You can easily control the coroutine with just a couple of lines of code, determine its state, react to events, and so on.

Just read documentation on github.