@IamHavoc Thanks for the feedback. The Issue has been fixed with the release of version 1.5.3 today. Thank you for your patience.