Datastrike Documentation

website·Indexed 30 days ago

https://datastrike.github.io/datastrike-docs/

Documentation for Datastrike, featuring guides on its architecture, analysis tools, game tracking, team management, and scouting capabilities for fetching player, team, and match information.

Tokens
1.3K
Snippets
2
Records
16
Agent score
74%

What's inside Datastrike

  1. Overview of Datastrike

    Datastrike is a tool designed to provide an easy-to-use platform that aggregates the needs of staff, players, and individuals interested in competitive video games.
  2. Understand the DataStrike Tracker architecture

    The tracking feature utilizes a standard form input. Submitted data is sent to the backend and stored in the tracker_results table. All statistics and charts are generated and updated on the client-side in real-time.
  3. Understand Datastrike analysis visualizations

    Datastrike provides several visualizations based on parsed log data:

    • Timeline: A high-level overview of game events including hero swaps, kills, deaths, and ultimates.
    • Comps: Displays team compositions and the duration each hero was played, highlighting differences when swaps occur.
    • Fights: Identifies combat encounters using a custom detection algorithm.
    • Graph: A dynamic comparison tool for player statistics extracted from logs.
    • Rounds: Provides raw data tables showing events that occurred during each round.
  4. Track game results using the Datastrike Tracker

    The Datastrike tracker provides a user interface for logging game results. Users enter game data into a form, which then automatically updates a table view for performance tracking. The tracker captures the following data points:

    • Opponent name
    • Date
    • Additional information
    • VOD Link
    • Map details (including Map Name, Score, and Replay code)
  5. Fetch player and match data via Scouting sources

    The scouting system retrieves information on players, teams, and matches using two primary external APIs. The frontend manages these calls using Tanstack Query for caching and efficient data fetching.

    • FACEIT: Uses the FACEIT API for player, team, and match data. Note: Some FACEIT data (e.g., player history results) may be inaccurate.
    • Blizzard: Uses the OverFast API to retrieve data for players with a public career, including hero stats, win rates, and role-based game counts.
  6. Manage player groups using Teams

    Teams allow players to be grouped together. A user can either create a new team or join an existing one. Users can view other members of their team, access invite codes to bring in new players, and leave a team at any time.
  7. Process game log analysis via Scrimtime

    The analysis feature processes .txt log files generated by the scrim workshop code DKEEH from Scrimtime. The workflow is as follows: 1. .txt files are sent to the backend. 2. The backend forwards files to a Python processing server. 3. Once analysis is complete, the backend notifies the frontend via websockets to trigger a real-time update without requiring a page refresh.
  8. Manage team roles and permissions

    Teams are used to group players. Users can create or join teams. The creator of a team is automatically assigned the ADMIN role. Users with ADMIN privileges can manage the team, which includes promoting other players to ADMIN or kicking members from the team.
  9. Contribute to Datastrike via GitHub

    Datastrike is an open-source project divided into four main repositories: Frontend, Backend, Python-Processing, and Docs. All repositories are hosted on the Datastrike GitHub Organization page. Contributors are encouraged to report bugs or request new features by creating Issues, and to submit bug fixes, UX/UI improvements, or code quality enhancements via Pull Requests.
    GitHub Organization: https://github.com/datastrike
  10. Fetch player and match data using FACEIT API

    The scouting system utilizes the FACEIT API to retrieve information regarding players, teams, and matches. Note that some data provided by FACEIT, such as player history results, may be inaccurate and should be handled with caution.