@noelrap every time you have an unexpected nil is a type error, right? That seems to be an extremly common class of errors, even if it was caused by a subtle logic bug.