May i suggest that in the future instead of posting all the revision directly to github you do some kind of regression tests so such errors can't pop up to who always update to the last commit but happens in a test enviroment? Is just a tip not some kind of offense anyway



you're right. i should have tested but I was interrupted then time was lacking...next time, i'll push into a distinct branch if untested.be aware of: my repo is only a unofficial temporary (and dirty) solution in waiting of official wolf's update. (if any)