@alteredEnvoy I see the issue, although I'm not sure *why* that was happening... I believe it should be fixed now.