@Emil This is fixed now, thanks for the support!