Error handling in custom blocks is a pain #168
Description
Currently, the way errors work in PenguinMod is that if they aren't caught within the block stack where the error was produced, the entire stack stops where it's at and displays an error accompanied by a red line surrounding the stack. This error handling, however, makes it a bit annoying and complicated to catch and handle errors produced in custom blocks that aren't already caught within the custom block, as you can't catch an error thrown inside a custom block, from outside the custom block.
The below video shows a situation where an error would normally be caught in literally any other programming language but isn't in PenguinMod.
video.webm
I request that catching errors produced in a custom block work in the same way as errors in most programming languages, where they travel up the callstack until they reach a catch statement or they can't travel up the callstack any more (at which the exception is displayed to the user). This would allow for much better error handling to be used in projects and make coders' lives easier.
P.S. if this could also be applied to the Lambda extension that'd be great because the only thing that currently happens there is errors being silently printed to the devtools console