Ok, uploaded a fix for this (Hopefully correctly, this time...) As a note, the build number is the same (v1.13.1)
