On 06 Dec 2021, g00r00 said the following...

 g0>  TY> Not sure if the message I posted to you in Araknet got to you, but I 
 g0>  TY> wondering what changes between a46 and a47 would cause an MPY script 
 g0>  TY> suddenly hang up on someone using either a break or a true/false
 g0>  TY> statement to break out of a loop to happen, and if you know, what I
 g0>  TY> could do to remedy that. Thanks!
 g0> 
 g0> I think I missed some messages there or something.  I probably
 g0> accidentally did a "Catch up" on that base.
 g0> 
 g0> Can you give a small example that I can run to see this happening?

I was going to, and then on a lark decided to check the error.log. It's coming up as:

MYSTIC001 An error has occured: EAccessViolation Access Violation

No idea what that means, but I bet you do! =) This has only been happening since I upgraded to a47 a few weeks ago. I deleted the false paths for the two different Python versions in the config after upgrading (left blank after) and thought maybe that was it, then added the paths, was still hanging up on me.

--- Mystic BBS v1.12 A47 2021/12/01 (Linux/64)