Juno: New Origins | Vizzy Breaks with Bad Variable-String Manipulation

When setting a variable-with-no-value to letters 1 to -1, that particular event breaks (all other events function normally).

To Test

Go back to the Designer, and check the Flight Program for the Beacon.
Launch craft, and open Beacon logs.
Press AG1, and see the while loop break
The beeping noise will still play, meaning that the AG1 event is broken rather than the part's Flight Programme.

Expected behaviour

Instead of crashing/breaking, it should skip that part and continue with rest of the event (in this case, continue the while loop).
Ideally it should log the error as well.

Bug Rejected Found in 0.9.615.1

Sandbox	View

2 Comments

Log in to leave a comment
1,469 t4zcomz

I very much see your point. It would be nice to have a more user-friendly crash log though. Maybe it could show the last block it executed before breaking or something.

+0 4.0 years ago
Dev Pedro

This is indeed a bug but not in the game. When programming you have to be careful with this kind of occurrence because there's no way to skip them and they'll break almost any program.
Think about it this way: you skip that part of the program and keep running the rest of the code, but the next block is calling that same variable. How can the programmer know what's inside that variable? Does it still have their previous contents, a null, 0...? It's sadly an unfixable problem that has to be dealt with on the vizzy programming level.

+0 4.0 years ago

3 Upvotes