supmate

Hey Aslain, the female voice of deathmatch announcer is actually male voice. I tried deleting the download cache file but still its male not female. Thx mate.

Alright :D lets just blame MS

I am always installing it as admin. I have not configured any special permission things on this system other than creating a standard user account. When I tried to launch WOT as a standard user I encountered this problem. The question is why should these files permissions differ from other files permissions in the wot folder after running your installer. As in for example: Why has the file _Aslain_logs.zip different permissions than the file _Aslains_Installer.log. o/

So you were not able to reproduce it? I cannot explain how this should be local, can you? My only explanation for now would be that your source files of these files have wrong/missing permissions, and these permissions get preserved to my disk somehow. For the sake of completeness the missing permissions are "Authenticated Users" and "Users". Anyway, its not a big thing...I will try to reproduce it on another machine on occasion. Have a nice weekend :)

Hey Aslain, while playing around fighting lags and errors of python.log, I figured, that the filesystem permissions are set wrong on some files. after running your installer. I used AccessEnum from sysinternals.com to check the WOT folder. See screenshot. If I start WOT as Non-Administrator, I get errors in python.log and the game hangs at battleloading screen if I start a random battle. If I start it with an account that has administrator-rights, it runs fine. this might also be the cause for the other thread To resolve the issue, I manually set permissions on the WOT folder recursively. Procedure (for Win7) for others with issues: goto Properties of WOT folder > Security > Advanced > Change permissions Check the option "Replace all child object permissions..." then click OK. Thanks mate. python.log _Aslain_logs.zip

Hey Aslain, first of all THX MATE for your hard work! GG Today I had serious issues with the installer for the first time. I had a small recurring issue before (i will explain) that I have been able to resolve myself every time it occured. It is the error of any_to.js.I attached a screenshot. This error did not show up every tme I updated your modpack, but sometimes it showed up. I have been able to resolve it every time with just installing the your modpack again with the same settings. Then the error did not show up. To the more serous error I got today: As there has been a client update, I completly wiped my wot folder (as I do always when there is a client update) and used a vanilla client install where no mods have ever been installed on. I did that multiple times before and it always worked without issues. I ran the wot-laucher to get the update, then ran your modpack installer. The any_to,js error appeared. So I ran your installer again. (like I described above) But this time another error showed up (screenshot attached). After clicking retry for about 5 times, the installer continued. Alright then I thought but it was not. When I wanted to copy over my modified xvm files, I did not find the folder. Instead I found other folders in the res_mods folder. (screenshot attached) EDIT: OMG I just read that the folder structure has been changed so I will have a look again, maybe everything is fine. Anyway the error messages maybe helpful) I also tried your preset modpack installer options (not my custom mod selection I normally use, but the error was the same). I also attached the other files you need. If you need further info let me know. Thanks mate. _Aslain_logs.zip python.log