16 game stats

[FreddyMSchubert]

Stored in misc section so it's sent via rabbitMQ so @Peu77 can easily read it out later. In the replay they look like this:

Decided to go for unified namings over object-specific verbs, e.g. bombs destroyed = count of bombs that exploded.

I think we should highlight mainly stuff like "damage-self" and "cores-destroyed" and "units-spawned" on the website but make all of them accessible.

Cores destroyed is a stat because theoretically eventually three teams might play a game against each other.

[Copilot]

Pull Request Overview

This PR implements comprehensive game statistics tracking for replay analysis. The system captures 16 different game metrics including damage dealt, objects spawned/destroyed, gems transferred, and action counts.

Key changes:

• Added a singleton Stats class to track game metrics across all game actions
• Integrated statistics collection into action execution (attack, build, move, etc.) and object destruction
• Statistics are included in the replay's misc section for external consumption via RabbitMQ

Reviewed Changes

Copilot reviewed 13 out of 13 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
server/src/game/Stats.cpp	New singleton class implementation for tracking game statistics
server/inc/game/Stats.h	Header defining 16 stat keys and Stats class interface
server/src/game/ReplayEncoder.cpp	Integration of stats into replay misc section
server/src/game/Game.cpp	Object destruction statistics tracking and code formatting
server/src/action/*.cpp	Statistics collection in all action types (attack, build, move, create, transfer)
server/inc/object/Bomb.h	Added Stats.h include for bomb explosion tracking
server/inc/game/ReplayEncoder.h	Added Stats.h include and formatting cleanup
server/inc/action/AttackAction.h	Added Stats.h include for attack statistics

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}