Skip to content

v1.4.0 - Rating workaround

Compare
Choose a tag to compare
@Askaholic Askaholic released this 27 Mar 07:56
· 239 commits to develop since this release
08a796c

Summary

The big change in this release is a temporary workaround in computing game winners to be more resilient against bad results. We discovered that some work needs to be done on the FA side of things, but until that work is done, this server change should mitigate a lot of the rating issues present in the last release.

This release also includes another important rating related fix. Game end times should now be computed more accurately, meaning fewer opportunities to have rating overwritten by playing games too closely back to back. In particular, game end is no longer determined by when you leave the score screen, but instead when the simulation actually ends.

Other noteworthy changes

  • Reworked metric reporting with the official Prometheus library. This means metrics will be more accurate and more plentiful!
  • Game launch options should now be sent correctly.
  • The army outcome for each player is now written to the database. This will let us see when results were missing or conflicting.
  • Updated to python3.7

Deployment Notes

The server no longer uses StatsD. Instead we will need to update the faf-prometheus.yml file. Just copy and paste the scrape config for faf-aio-replayserver and change the job and target name to faf-python-server.

Pull Requests

  • Make matchmaker test more reliable (#556)
  • Add build info to metrics (#555)
  • Issue/#525 update python3.7 (#526)
  • Majority vote game outcomes (#550) [by UmbraSolis]
  • Log API error (#549)
  • Issue/#346 game length too long (#511)
  • Write GameOutcome to db in Game.persist_results. (#543) [by UmbraSolis]
  • Tweak automatch options (#545)
  • Issue/#527 fix game_launch options (#530)
  • Prometheus metrics (#538) [by UmbraSolis]