Hi ZyrByt, thanks for bringing this to our attention, we've made the appropriate fix and welcome any additional feedback. :)