Not a Bug

Console error links to Trigger Custom Unit instead of actual unit

Vong 3 years ago updated by Lazlo Bonin (Lead Developer) 3 years ago 1

(Not sure if Bug or by design)

If code that is triggered by Trigger Custom Unit for whatever reason errors, double-clicking the error in the Console log will redirect to the Trigger Custom Unit, rather than the code that is actually error-ing.

(The error message would also be on the Trigger Custom Unit itself as well, which can be confusing if you don't know that its the error message for some other unit that got triggered by this one.

While I can see cases where this might be preferred (specifically when you have many trigger sources) I mostly found it tedious to manually hunt down the misbehaving units each time.

Bolt Version:
Unity Version:
Scripting Backend:
.NET Version (API Compatibility Level):
Not a Bug

That is "by-design", or rather just a limitation of the Unity console. We unfortunately can't customize what happens when a user selects or double-clicks a log item in the console, so Unity just opens the associated Bolt source file. 

One thing we're looking into for the future (2.x) is to create our own console window that allows quick-jump to the erroring nodes. It's kind of ridiculous that we have to recreate the console entirely just to have a custom behaviour on click, but it seems like the only way.