result | |
type | |
spawn | |
version | |
played | |
uploaded | |
server | |
downloads |
base | |
total | |
free |
base | |
total | |
repair cost |
mouse enabled | |
camouflage type | |
battle level |
# | name | dmg | frags | exp |
---|
# | name | dmg | frags | exp |
---|
capture/dropped points | |
wp points earned/stolen | |
mileage | |
time alive |
total | |
base | |
for damage | |
for assist | |
team bonus | |
hero bonus |
total | |
base | |
hero bonus | |
repair cost | |
penalty |
made | |
hit | |
splash | |
pen |
received | |
bounced | |
splash | |
pen |
dealt | |
assisted | |
assisted on tracks |
received | |
blocked |
**** | ***** | *********** [***] | ****** **** ** |
---|---|---|---|
**** | ***** | ******** [****] | *** ** ******* ***** |
**** | ***** | *********** [***] | ******* *** *** **** |
Upon receiving a new replay, wotinspector can only obtain limited information contained in the summary. To extract the things like heatmaps, chat, shots or other things not available in WG stats (blocked damage, etc..) we need to analyze the replays and extract the data. Unfortunately doing it for each incoming replay server-side introduces high costs for CPU-hours spent by server. Instead replays could be processed locally on PC or tablet.
You can do that when watching a replay in Map Inspector or just by pressing the button below. The button will download this replay and few others, parse them on your local machine and then upload results into the database so every other user can have access to that data thanks to you.
process data