Frame mismatch not functioning when point in world

I'm running into an odd issue. When a point is taught in world, and you run to it in a different userframe, instead of generating a frame mismatch error, the robot just simply runs there with no errors. Active frame doesn't change.

If the point has a user frame number other than 0, and you run to it with a mismatched frame number, you get an alarm, as expected.

Is there a system variable besides FRM_CHKTYP that governs this behavior? I want the robot to fault if you run to a point taught in world, and you have the a frame that is not world active.

Yeah, this is kinda nuts. I'm teaching a class, and was confident if the students had the wrong frame selected when running the program, the robot would fault. Then we did the classic move the paper they made their path on, and one student had accidently touched up everything in world, even though at the top of their program they had the UFRAME= and UTOOL= commands.

I've been able to recreate it on 2 real V9.30P robots, and one virtual V9.30P, and one virtual V8.30.

Its been eye opening what they've been able to find that I've missed over the years.