Hi Bryan, I've gone ahead and created an issue for this on the GitHub. We'll get to work seeing if there's a good way of making the addon not behave like that.