That just means that butler’s directory isn’t in your PATH environment variable, not the developer’s fault.
Sorry if I implied it was the dev's fault, that's not at all what I meant. What I meant was that the dev might know how to fix the issue, but I think I'm gonna just leave it be for now.
You need to add the directory that “butler.exe” is in to the PATH environment variable, and that should fix the issue.
I don’t know if Butler has a Windows-specific installer or if it has an option to automate that.
