Hi @GroovyNoody, thank you for sharing your concerns with us, we’re already aware of this issue and we assure you it’s not intentional, so it should be addressed in an upcoming patch.