sherwood
/
tf2DemoAnalysis
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
6 Commits
2 Branches
0 Tags
101 KiB
csharp
main
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'csharp'
${ noResults }
Go to file
Tarik Hijstek d154b31bbf copy paste from existing library 2 years ago
.vscode csharp init 2 years ago
demos initial 2 years ago
src copy paste from existing library 2 years ago
.gitignore gitignore 2 years ago
readme.md another shoutout 2 years ago

readme.md

Demo analysis

Analysis of TF2 Demo files. To help me get more data driven approaches to get better at the game.

Tracing what?

  • Accuracy
    • Meatshots hit (>100 dmg)
    • Meatshots missed (<100dmg shots when close to enemy)
    • shots hit / shots taken
  • Team positioning?
    • How close to the 'core'
    • How often on flanks
    • % of time spent overhealed
  • 1v1 %
    • How often do I go for flank 1v1's
    • How often do I win the 1v1

And how do we get that data?

Parsing the demo files. Hopefully once, maybe multiple times.

Only intrested after the start of the official match. Warmup should not count.

Big up for (DemoInfo)[https://github.com/StatsHelix/demoinfo/tree/master/DemoInfo] for providing some inspiration

And thanks to the lads at (demostf)[https://github.com/demostf/parser] for TF2 specific code

Another shoutout to (demolib)[https://github.com/PazerOP/DemoLib] for the big combo of C# code and tf2 info.