cmss13-devs
Statistic
About the pull request
Now you can see detailed statistic, kills/shots/hits/damage and more, kills/shots/hits/damage ff (admins can see it too, so don't do a lot of ff, grief ban 200%), and etc
Basicaly old statistic with full backend rework + new UI, also DB link... and potential easy way to adding new features to it
... (outdated screenshots)
Take this screenshot, most actions is here you can see... just imagine more different values,
Changelog
:cl: BlackCrystalic add: Added new statistic traking values refactor: Fully redone statistic plus save in DB ui: New TGUI for statistic code: Made round end announce and etc more flexible code: Mode names now is DEFINED /:cl:
This pull request has conflicts, please resolve those before we can evaluate the pull request.
Conflicts have been resolved. A maintainer will review the pull request shortly.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
we need friendly fire counters for guns, soul
It's already exist : 3
Conflicts have been resolved. A maintainer will review the pull request shortly.
This changes 130 files without a changelog or any details as to what it does beyond a vague titling of "Statistics 2.0" fix the changelog and detail what you're doing.
90% of 130 files changes is just renaming function and adding new statistic values... basicaly I can only highlight changes to round end announces system and... that all, all other is directly linked to working statistic functionality
If it's not right to do around something with statistic (opti, issues), I can try port it over to UI, with only sending raw data acessible to the user
This PR has been inactive for long enough to be automatically marked as stale. This means it is at risk of being auto closed in ~ 7 days, please address any outstanding review items and ensure your PR is finished, if these are all true and you are auto-staled anyway, you need to actively ask maintainers if your PR will be merged. Once you have done any of the previous actions then you should request a maintainer remove the stale label on your PR, to reset the stale timer. If you feel no maintainer will respond in that time, you may wish to close this PR youself, while you seek maintainer comment, as you will then be able to reopen the PR yourself
![cmss13-ci[bot] avatar](https://avatars.githubusercontent.com/u/84123730?v=4 "Published by a pub.dev verified publisher"){kind=small}
This pull request has conflicts, please resolve those before we can evaluate the pull request.
Conflicts have been resolved. A maintainer will review the pull request shortly.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
Conflicts have been resolved. A maintainer will review the pull request shortly.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
Conflicts have been resolved. A maintainer will review the pull request shortly.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
Conflicts have been resolved. A maintainer will review the pull request shortly.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
Conflicts have been resolved. A maintainer will review the pull request shortly.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
Conflicts have been resolved. A maintainer will review the pull request shortly.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
Conflicts have been resolved. A maintainer will review the pull request shortly.
This pull request has conflicts, please resolve those before we can evaluate the pull request.
Conflicts have been resolved. A maintainer will review the pull request shortly.