When using funk it is really easy to have syntax errors that break the whole program. The log says SetVariableInstruction: Error running flight program: Syntax error or something similar depending on the error. While this is somewhat helpful, it doesn't give much information about which line is causing the error. This makes it really hard to track down bugs in programs with lots of funk, especially when the errors only happen with some but not all conditions.

Since vizzy doesn't have line numbers I'm not sure what the best traceback method would be. Maybe the log could say the variable name or print the line of funk that caused the problem, or the function that it was called in. Really anything would be helpful.

EDIT: it would also be helpful if error messages from part input controllers get logged somewhere, either the main command chip log or the dev console

Suggestion Active

3 Comments

9 Upvotes

Log in in to upvote this post.