Data - more is better
Posts: 1158
For example, commander choices can be tracked and displayed for all users to see. It can be ordered either custom by the user or maybe even by CoH2 displaying a top 5 commanders along the side of the site. This could show a variety of percentages, such as percent of all allied players that chose the commander or even percent of all games since the last patch that the commander was used in. With visualizations of this data, you would be able to literally see the meta. Discussions could be easily and plainly backed up by the data, unbiased as it happens.
Right now, Relic tells us something about the game and we just have to take their word about it, because they don't show the data they are collecting. It would be even better if we were given an API to this database, so fan sites and individual users can query it themselves. This could be an asset not just to CoH, but to all games that Relic makes. I know of at least 1 other game company doing this, which I believe was 343 games, possibly even Bungie as well. There was a fan site I visited that took advantage of the API and could show me all kinds of crazy statistical data about the games I played in Halo. So, I think this would be amazing for Relic and CoH without being too difficult to implement.
Posts: 2066
Good post mate!
Posts: 1158
Posts: 3145 | Subs: 2
You wanna guess how many lifetime bullets have been fired in coh2? No one could even verify it.
You're not serious, if the game engine did really keep track of EVERY single bullet fired by an infantry unit or a machine gun in this game they'd have to write new numbers to incorporate all of them.
Games won and lost are a whole different matter now.
Posts: 1158
Posts: 8154 | Subs: 2
Regarding CoH, not the same you are asking for, but there was a project to analyse and make use of the data hold in the replays.
http://cohdb.com/
I'm sure if the game didn't struggle so much during it's lifetime + a bigger n more stable population we could might end up with something like this:
http://www.hotslogs.com/Sitewide/HeroDetails?Hero=Samuro
This is for Heroes of the Storm. People upload the replays and then you have a huge database with all the relevant information you might want.
Posts: 4630 | Subs: 2
(their damage is counted in "total damage" but not for unit itself; even okw flak has its own match stats).
Then I would add damage made by abilities, mines, demos.
Posts: 1158
Another example: Planetside 2 API allowed for the awesome Recursion stat tracker to be made. Fan made overlay with customizable voicepack announcer on kills and different events (like screaming rage quit when someone disconnects after you killed them )
Regarding CoH, not the same you are asking for, but there was a project to analyse and make use of the data hold in the replays.
http://cohdb.com/
I'm sure if the game didn't struggle so much during it's lifetime + a bigger n more stable population we could might end up with something like this:
http://www.hotslogs.com/Sitewide/HeroDetails?Hero=Samuro
This is for Heroes of the Storm. People upload the replays and then you have a huge database with all the relevant information you might want.
Great examples, I'll have to check them out in more detail when I get home after work. Pulling the information out of replays would be a good thing too, but I'm not sure if the replay file has every transaction. I mean I think it would, otherwise it should be impossible to recreate the game, since missing actions would be present.
Firstly I would add all units to match-stats casue Pit, Bofors and 17P despite being units, they are not counted in match stats
(their damage is counted in "total damage" but not for unit itself; even okw flak has its own match stats).
Then I would add damage made by abilities, mines, demos.
They must be some kind of entity that the game transacts with. I mean if it wasn't, then it would be like units receiving some kind phantom damage, with no way to explain the destruction of their instance.
Posts: 141
I would very much like to see big data style heat maps from all the uploaded replays from, say a tourney and stuff. Right now, very valuable community members are doing a shit ton of work to record, analyze and display actually relevant and interesting stats from tourneys.
We don't even need relic to do it, just give us good APIs, (modding) tools and boom, community can take over this piece of unpolished, half assed shit.
Posts: 1138 | Subs: 2
- Replays
- Match history
Re replays:
These contain the setup (players, map, loadout) and all commands issued by a player. For example, it contains commands for:
- Build a gren squad
- Upgrade the gren with an LMG
- Send gren squad to point (x,y)
- Use the ability "Panzerfaust"
It does NOT contain the result of this action, like, it doesn't contain if the gren squad ever reached the point it was sent to or if it was shot at, let alone if it hit anything or if he took damage or died. It also does not contain resources or the status of the territory. It doesn't even contain which player won (unless one player surrendered).
When watching a replay file, the program literally replays the game issuing the player commands to the game engine and the game engine figures out what the effect of those commands is like it did when the game was played. This is the reason why old replays don't work when the "rules" have changed in the meantime due to a patch.
Re "Match history":
This is available to display "Recent Matches" on the leaderboard webpage. The data package that you get contains more information that what is displayed on the webpage (e.g. info on the map), but it's not as comprehensive as you might like (there are about 30 numbers that you get back), for example as far as I can make out there is no info on the commander choice.
Relic obviously has those two data sets (the first is probably what is actually exchanged via battleservers during the game, but it also has to be stored on the server - at least temporarily - to be able to spectate a match).
Not sure, though, if they actually have a game client running on their end that also runs the replay or if the second set is produced by your client and sent to Relic after the match...
Posts: 1158
What I don't understand about the replay file is how it removes the luck from the game. If in a replay a sherman shoots at a panther, it doesn't always penetrate. So the replay file has to be able to tell the game that in a particular engagement, the round did indeed penetrate. So every time the replay file is played that shot always penetrates. Same for small arms fire accuracy and where arty shells landed. These things have to be done exactly as they occured or the replay file has no integrity, rendering it useless and corrupting the outcome.
Posts: 1138 | Subs: 2
And indeed, the replay file contains the RNG_SEED, the number with which the RNG generator is initialized for this specific match.
This means that when the replay runs and an RNG number is needed, the RNG will spit out the same number that it produced originally. So, if the shot penetrated the first time around, it will also penetrate the second time.
Posts: 20
Back in the CoH1 days the replay system could sometimes end up with sync errors when you sped the game up too fast.
Posts: 1158
Livestreams
93 | |||||
37 | |||||
34 | |||||
15 | |||||
9 | |||||
181 | |||||
17 | |||||
8 | |||||
7 | |||||
2 |
Ladders Top 10
-
#Steam AliasWL%Streak
- 1.653231.739+13
- 2.839223.790+2
- 3.35057.860+15
- 4.592234.717-1
- 5.278108.720+29
- 6.306114.729+2
- 7.645.928+5
- 8.922406.694+1
- 9.1122623.643+3
- 10.265138.658+2
Replay highlight
- cblanco ★
- 보드카 중대
- VonManteuffel
- Heartless Jäger
Board Info
0 post in the last week
28 posts in the last month
Welcome our newest member, Baqis73421
Most online: 2043 users on 29 Oct 2023, 01:04 AM