This content has been marked as final. Show 2 replies
This bug was not fixed in 1.2.1 because it was a fairly large fix and the runtime was rewritten for 1.3. This bug has been confirmed fixed by our testing team in 1.3 which should be out next week.
I'm looking forward to getting 1.3 !