Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Data in xlsx export #790

Closed
Dying-Ducks opened this issue Mar 24, 2024 · 1 comment
Closed

Missing Data in xlsx export #790

Dying-Ducks opened this issue Mar 24, 2024 · 1 comment

Comments

@Dying-Ducks
Copy link

What problem is this solving

Using the xlsx export function reveals that the .xlsx file is "missing" a lot a data.

In the "csgo version" of the demo manager one could easily recreate the overview the manager displays after the analysis with the information within .xlsx file.
Now you can’t do that, as things like
-MVP
-Score
-All Utility related data (like everything, utility isn’t mentioned once in the .xlsx)
-In depth Weapon data like damage/shots/hits/accuracy for each weapon per player
-opening deals stats
are not in the exported .xlsx file. So the demo manager has far more information than it gives you through the xlsx export.

Proposed solution

It would be nice if the missing data could be "added back" and we are able to export every information the demo manager pulled from the demo with the .xlsx export.

Describe alternatives you've considered

No response

akiver added a commit that referenced this issue Mar 29, 2024
akiver added a commit that referenced this issue Mar 29, 2024
- fix a bug where the flashbang matrix may not show correct values

ref #790
akiver added a commit that referenced this issue Mar 29, 2024
akiver added a commit that referenced this issue Mar 29, 2024
@akiver
Copy link
Owner

akiver commented Mar 29, 2024

👋
The next version will provide more data in XLSX exports (see related commits for details).
Because it would be impossible to fit everyone's needs, you could generate your own export using SQL.
See this documentation.

Adding SQL examples to the documentation is also a possibility.

@akiver akiver added next-release-resolved This issue will be solved in the next release and removed next-release-resolved This issue will be solved in the next release labels Mar 29, 2024
@akiver akiver closed this as completed Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants