Week #5 #
Feedback #
Sessions #
| User | Context | Key Comments |
|---|---|---|
| User 1 (classmate, competitive-FPS fan) | Played staging build on gaming laptop (Wi-Fi). | • Wanted visible armor/health pick-ups. • Asked for an in-match leaderboard. • Noticed brief stutter when > 6 players shoot simultaneously. |
| User 2 (neighbor, casual gamer) | Tested Windows build with Xbox controller. | • Spawn points felt “too exposed”, died quickly. • Couldn’t change nickname after launch. • Jump-pads are fun but need SFX cue. |
| User 3 (TA, network-engineering background) | Joined public server over 4 G. | • RTT good but memory grew after ~15 min. • Suggested clearer domain/transport split for scaling. • Recommended Prometheus metrics endpoint. |
Analyze #
| Issue | Priority | Backlog Ticket |
|---|---|---|
| Missing in-game leaderboard | P1 | feat/leaderboard-ui |
| Visual cues for armor/health pick-ups | P1 | feat/pickup-devices |
| Stutter on mass shooting | P1 | perf/bullet-pool-optimization |
| Change nickname post-launch | P2 | ui/nickname-input |
| Spawn safety | P2 | level/spawn-balancing |
| Server memory climb | P2 | ops/memory-leak-investigation |
| Prometheus metrics endpoint | P3 | ops/prometheus-endpoint |
Iteration & Refinement #
Implemented features based on feedback #
- Armor system & pick-up devices — models, logic, UI.
- Leaderboard UI — real-time ranking panel.
- Nickname input dialog — local storage + send to server.
- Multiplayer fixes.
- Map update & safer spawns.
- DDD + Clean Architecture refactor — domain split, graceful shutdown.
- Server documentation — build/run guide & diagrams.
Performance & Stability #
Collected metrics
| Metric | Measured value | Target |
|---|---|---|
| Avg. server tick duration | 2 ms | ≤ 5 ms |
| 95-th percentile RTT (EU stage) | 45 ms | ≤ 60 ms |
| Max concurrent players without GC spikes | 14 | ≥ 12 |
Improvements
Much more concurrent players could be obtained if we will take more powerfull server with better configuration.
Documentation #
- README.md — quick-start, compose, FAQ.
- Inline XML-comments — public API & packet definitions.
- CI/CD notes — workflow explanations inside
.github/.
Weekly commitments #
Individual contribution of each participant #
Plan for Next Week #
- Complete migration to DDD branch across all modules.
- Re-engineer server hit-detection & damage logic.
- Add Prometheus metrics exporter and enhance logging.
- Identify and patch memory leak.
- Polish codebase and write final slide deck for project defense.
Confirmation of the code’s operability #
We confirm that the code in the main branch:
- In working condition.
- Run via docker-compose (or another alternative described in the
README.md).