| 1 |
For
clarification:
the
.
gz
is
a
sqlite
data
of
the
damages
reported
between
units
per
battle.
This
can
be
used
with
the
.
gz
of
the
sqlite
database
of
all
the
games
(
at
http://zerok-local-analysis.
s3-website.
eu-west-3.
amazonaws.
com/data_version2/zk.
db.
gz)
.
|
1 |
For
clarification:
the
.
gz
is
a
sqlite
data
of
the
damages
reported
between
units
per
battle.
This
can
be
used
with
the
.
gz
of
the
sqlite
database
of
all
the
games
(
at
http://zerok-local-analysis.
s3-website.
eu-west-3.
amazonaws.
com/data_version2/zk.
db.
gz
)
.
|
| 2 |
\n
|
2 |
\n
|
| 3 |
I can consider making some UI, but I would need some idea on what to represent. I collected them as @chaplol suggested and it was rather easy (I started the data collection several months ago, but did not get to process them).
|
3 |
I can consider making some UI, but I would need some idea on what to represent. I collected them as @chaplol suggested and it was rather easy (I started the data collection several months ago, but did not get to process them).
|
| 4 |
\n
|
4 |
\n
|
| 5 |
The idea of ZKLA was to do the representation only on the client side (load all data in JS from a static json). While this is possible for battles/awards (for the full 10 years), for the damage it might get a bit too much (don't know did not test), so probably will need to do some summarization.
|
5 |
The idea of ZKLA was to do the representation only on the client side (load all data in JS from a static json). While this is possible for battles/awards (for the full 10 years), for the damage it might get a bit too much (don't know did not test), so probably will need to do some summarization.
|
| 6 |
\n
|
6 |
\n
|
| 7 |
If anybody wants to do locally some visualization this would make it much easier, so hope it helps someone.
|
7 |
If anybody wants to do locally some visualization this would make it much easier, so hope it helps someone.
|
| 8 |
\n
|
8 |
\n
|
Zero-K Local Analysis