Support coroutines on Timer and Cooldown outputs

Minh-Tri Nguyen 3 years ago updated by Lazlo Bonin (Lead Developer) 2 years ago 5

Not sure what's the best way to report bug so I'll just attach a screenshot this time.

Bolt Version:
Unity Version:
Scripting Backend:
.NET Version (API Compatibility Level):
Pending Review

Hi Minh-Tri!

The problem is that the Timer unit does not start a coroutine for its Completed port.

I'll see if I can find an intelligent way to do that without graph analysis.

Perhaps starting a coroutine every time would be an acceptable solution.

Working on Fix

I'll add an option to the unit to treat these output ports as coroutines.

While I'm at it, I'll try reworking the coroutine indication so that it lives at the port level and clearly displays it, along with warnings when you're trying to use a unit that requires coroutine flow without it.


Due to the core nature of the changes required to fixed this, it has been slated for a later update (currently 1.5.2).

A workaround could be to trigger and listen to a custom event marked as a coroutine right after your timer completed.


(Sorry for the bump/necro, I'm doing some roadmap grooming following the Unity acquisition!)

This is now supported in the latest Bolt 2 Alpha.