search

HumanityZero / wot-xvm

Automatically exported from code.google.com/p/wot-xvm
0 stars 0 forks source link

Missing damage values in API #221

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
It's not really affecting XVM code, but remote XVM stats proxy.

WarGaming has again set to 0 values of _damageDealt_ for every vehicles in 
_data.vehicles_ in their mobile API 
(http://worldoftanks.eu/community/accounts/.../api/1.8/?source_token=...) so 
again it's not possible to calculate average damage for vehicles (at least for 
EU server).

Original issue reported on code.google.com by sunri...@gmail.com on 13 Dec 2012 at 10:28

GoogleCodeExporter commented 8 years ago 
What is your proposition?

Original comment by m.schedr...@gmail.com on 13 Dec 2012 at 11:45

GoogleCodeExporter commented 8 years ago 
To keep old tank damage values in mongodb and additionaly check while getting 
stats for players if data.battles.damage_dealt is equal to sum of damageDealt 
in data.vehicles

Original comment by sunri...@gmail.com on 13 Dec 2012 at 12:10

GoogleCodeExporter commented 8 years ago 
It will increase server load. I'll make only checking for '0' to keep old 
damage values.

Original comment by m.schedr...@gmail.com on 13 Dec 2012 at 12:33

GoogleCodeExporter commented 8 years ago 
Your link is broken, give another example.

Original comment by m.schedr...@gmail.com on 13 Dec 2012 at 12:55

GoogleCodeExporter commented 8 years ago 
Well, it was example without ID and token.

http://worldoftanks.eu/community/accounts/500662837/api/1.8/?source_token=Intell
ect_Soft-WoT_Mobile-unofficial_stats

Original comment by sunri...@gmail.com on 13 Dec 2012 at 12:59

GoogleCodeExporter commented 8 years ago 
I think better to wait while WG will fix their API.
I tried to make skipping of 0 values, but it is not so easy, because we are 
operating with objects and cannot update one fields and skip other. The only 
way is to merge objects, but this will also add extra load.

Original comment by m.schedr...@gmail.com on 13 Dec 2012 at 2:02

GoogleCodeExporter commented 8 years ago 
OK, it seems like API is working again. Sorry for the mess ;)

Original comment by sunri...@gmail.com on 13 Dec 2012 at 7:18

GoogleCodeExporter commented 8 years ago 
Ok

Original comment by m.schedr...@gmail.com on 13 Dec 2012 at 9:54