mirror of
https://github.com/OpenSquawk/OpenSquawk
synced 2026-08-03 15:36:24 +08:00
cd4c640040
A rejected take-off and a go-around both happen by chance about once in five hundred flights, which is the point of them — you cannot practise reacting to something you were told to expect. That also made them impossible to teach. Two switches under Special scenarios force either on the next flight. They are read when the session is created rather than watched, so flipping one mid-flight applies to the following one — which is how an instructor sets it up without the pilot seeing it coming. Only a switched-on value is sent: the backend reads the variable's absence as "leave it to chance", so sending false would pin the roll off instead of leaving it alone. Styled amber rather than the usual cyan, and the consequence is spelled out while either is armed: neither scenario continues to the stand.