Hello Diatomic Muffin,
Thanks for taking the time to report this issue. Fortunately this bug was caught and reported in 4.11.2 and has been fixed within the 4.13.1 engine release.
Go ahead and test it out to see if the issue is resolved on your end, but let me know if you need further assistance.
Thank you,