Level 1: A bit complicated, but Switches that are inside the parent code of an Emitted object do not get reset properly when that object is destroyed, and instead they stay off or on in the next copy of that object that gets Emitted. Other values like Object Values or Numbers might not get reset as well.

LEVEL 2: Copying to the clipboard doesn't seem to work while in fullscreen. (I have tested this on Edge and Chrome.)

LEVEL 3: If you Emit an object, and that object sends itself a message, and that object has a parent with a mailbox to receive the message, and that message is supposed to Attach another object, the object will attach once and then fail to attach most other times afterwards.

LEVEL 4: If you rotate an object using the Spin behavior, its forward direction angle isn't correct IF you input a POSITIVE NUMBER into "forward" on a Velocity or Impulse (but NEGATIVE NUMBERS use the correct forward direction angle for some reason, EXCEPT with a motor, then BOTH positive and negative numbers don't use the correct forward direction angle).

LEVEL 5: Spawned objects are undetectable by Proximity until 1 frame after they are spawned (i.e. they cannot be detected on the same frame that they are created on). This seems kind of odd given that Proximity can have its origin changed mid-frame, multiple times, and still detect objects properly...So in my opinion Spawn should be consistent with this.