Hello, candrid!
I've identified the issue: A typo in the patches borked it, causing the error on the second screenshot. I am working on a hotfix and I'll upload it as soon as possible.
And this, is why you are amazing.