Did a quick hotfix, that issue should be resolved now. Not sure how I never ran into it when testing.
