No Information (Record) in Battle View (Wot 1.9.1.0)
No Battle View Records

With the latest Wot version 1.9.1.0,  I am not getting any battle view records - absolutely nothing

And Home Gadgets and Tank Views  are also not updating


  • Zavar - 11.06.2020

    I'm seeing the same.  We probably won't see any update until the other servers are on 1.9.1.0 so that dev's have something to debug/look into the problem with.

  • Kliphie - 12.06.2020

    This happens every major update.  The pathways change and need to be updated, usually takes a couple days

  • ProvoBob - 12.06.2020

    Can't say I've seen it before, but it makes sense that it's the WoT update causing this.

  • Nobody33 - 12.06.2020

    I just Test. No Battles see in WOTNumbers

  • Mykk - 12.06.2020

    No big deal, but once WotNumbers is updated, is there a way to import the battles that were missed?

  • Gladiusetscutum85 - 12.06.2020

    Same here on EU.  Played 19 matches today, but they're not showing in WoTNumbers.

    It would be good if WG would release an update early to external developers, legit modders etc. so that they can get their own updates ready for release when the game itself updates publicly.  Not to do so is  arguably somewhat unprofessional.

  • mfezi - 12.06.2020

    From previous experience, you can get most of battles once app has been updated....

  • Stan Lee - 12.06.2020

    Sadfly you cannot retreive data from the previous day(s).

  • BuSH - 13.06.2020

    fixed dossiers and begin fixing battleresults

  • BadButton - 13.06.2020

    Hi, a lot of changes in this version. Managed to fix reading dossier file (total tank stats), but I struggle getting the battle result parser to work (detailed battle stats).

  • BadButton - 13.06.2020
    Quoted: BuSH

    fixed dossiers and begin fixing battleresults

    Please let me know if you figure it out, I have implemented the normal updates to the battle parser, but ended up with this error (suspect i have not fixed the dictpackers.py correctly - my Python skills are limited yell):

    File "D:\Dev\WoT Battle Parser\wotbr2j.py", line 274, in dumpjson

        finalfile.write(json.dumps(bresult, ensure_ascii=False, sort_keys=True, indent=4))

      File "C:\Programs\Python2\lib\json\__init__.py", line 251, in dumps

        sort_keys=sort_keys, **kw).encode(obj)

      File "C:\Programs\Python2\lib\json\encoder.py", line 209, in encode

        chunks = list(chunks)

      File "C:\Programs\Python2\lib\json\encoder.py", line 434, in _iterencode

        for chunk in _iterencode_dict(o, _current_indent_level):

      File "C:\Programs\Python2\lib\json\encoder.py", line 408, in _iterencode_dict

        for chunk in chunks:

      File "C:\Programs\Python2\lib\json\encoder.py", line 408, in _iterencode_dict

        for chunk in chunks:

      File "C:\Programs\Python2\lib\json\encoder.py", line 408, in _iterencode_dict

        for chunk in chunks:

      File "C:\Programs\Python2\lib\json\encoder.py", line 408, in _iterencode_dict

        for chunk in chunks:

      File "C:\Programs\Python2\lib\json\encoder.py", line 408, in _iterencode_dict

        for chunk in chunks:

      File "C:\Programs\Python2\lib\json\encoder.py", line 382, in _iterencode_dict

        raise TypeError("key " + repr(key) + " is not a string")

    TypeError: key ('a15x15', 'frags') is not a string

  • PjhDeKoning - 13.06.2020

    I got a bit further, replaced wotdc2j.py(276) with 'finalfile.write(json.dumps(bresult, ensure_ascii=False, skipkeys=True)) '. This will stop it crashing when the keys are not strings (they are tuples when they crash). JSON format requires keys to be strings.

    The key that is causing the problems is: personal/6945/c11nProgress/129404/progress/('a15x15', 'battlesCount'). 

    I have no idea what the c11nProgress is. Maybe to do with the StrumTiger event or so?

    Now I have the problem that wotdc2j.py complains about 'Unsupported tankversion 103'. I have no idea how to make a new 'structures_103.json'.

    Any suggestions? Are they available in the WOT files?

  • BadButton - 13.06.2020  

    Yes, I found the same - eventually. I just deleted this section before parsing as json, at least in Wot Numbers we do not utilize this info.

    The tank version needs to be handled by the dossier parser, I have fixed that one.

    Publishing new version now, you can take a look at my changes and let me know if think you have found a better solution, 

  • BadButton - 13.06.2020
    Quoted: PjhDeKoning

    I got a bit further, replaced wotdc2j.py(276) with 'finalfile.write(json.dumps(bresult, ensure_ascii=False, skipkeys=True)) '. This will stop it crashing when the keys are not strings (they are tuples when they crash). JSON format requires keys to be strings.

    Thanks for this tip, I will add 'skipkeys=True' in the future

  • WakaWaka67 - 13.06.2020

    I just realised how dependant I got to the stats... Thanks for making my life nicer with your hard work!cool

  • ProvoBob - 14.06.2020

    Just downloaded and installed the latest version for the new WoT version.  When I start it up I get the mini window telling me that a new version is out, but I already istalled it!

  • ProvoBob - 14.06.2020

    Cannot get past that mini window without it bringing up the download page.

  • PjhDeKoning - 14.06.2020

    Looks good, can confirm it works.

    Did you consider seperating the Dossier2json from the main project for easier maintenance. Maybe have the main program get a zip file with the python stuff (from your site or maybe github). That should make it easier to update without having to make a new installer everytime the python code changes.

    If you put it on github others could help maintain it. I would like to help with that, I have some python experience.

    How do you create the structures_103.json file? Is it from the game files, like the battle_results_shared file?

    Thanks for the awesome program and keep up the good work.wink

  • BadButton - 17.06.2020
    Quoted: ProvoBob

    Just downloaded and installed the latest version for the new WoT version.  When I start it up I get the mini window telling me that a new version is out, but I already istalled it!

    Go to Windows applications and uninstall Wot Numbers, it might be that you have several versions installed.

  • BadButton - 17.06.2020
    Quoted: PjhDeKoning

    Looks good, can confirm it works.

    Did you consider seperating the Dossier2json from the main project for easier maintenance. Maybe have the main program get a zip file with the python stuff (from your site or maybe github). That should make it easier to update without having to make a new installer everytime the python code changes.

    If you put it on github others could help maintain it. I would like to help with that, I have some python experience.

    How do you create the structures_103.json file? Is it from the game files, like the battle_results_shared file?

    Thanks for the awesome program and keep up the good work.wink

    Thanks for the feedback!

    It would be nice to get some help on keeping the parsers up to date, my Phython skills are limited (I mostly develop using C#). When there are bigger changes like the last version it takes some time for me to figure it out.

    I have a separate Python application that generates new structure files when dossier parser needs it, it was made by Phalynx (previously vBAddict), and I got the source code from him. 

    The source code for both the parses and the system creating new structs are available in a GIT on BitBucket, but I have set them private currently. Occationaly people have helped me updating these, but it has normally just been for a short period. I guess the fun of it last just for a short time. I have probably spent more time helping others getting started, than the actual help I have got in return undecided

    I am afraid it will be quite some work developing a solution for automatically downloading the parsers and keep them separate from the installer. For me to include a new parser when it is made is just a couple of minutes of work.

Sign in for replying to topic Close