If you introduce sleep (either sleep or uiSleep) into uiNamespace or parsing Namespace or profileNamespace it switches to missionNamespace.
The sleep should be longer than 0.001 second. If it is shorter it doesn't happen. However I suspect this threshold is individual to the PC spec.
can replicate it in debug console
null = [] spawn {
var = "apples";
with uiNamespace do {
sleep .00000000001; var = "pears";
};
hint var;
};
result is "apples" as it should be
null = [] spawn {
var = "apples";
with uiNamespace do {
sleep .01; var = "pears";
};
hint var;
};
result is "pears" as it shouldn't be.
Somehow we managed to overwrite a variable in the different namespace from what we started. This should get high priority on fixing list.
Not even reviewed? Come on devs this is serious bug with the engine that makes use of alternative namespace a risk.
One might think do not use sleep inside alt namespace and everything will be fine. It is not true. If you have a blocking call inside namespace which is a little bit too long it will switch the rest of the code to run in mission namespace. This is unacceptable. Please do something about it.