Skip to content

Releases: FAForever/server

v1.17.0 TMM map veto system & Python 3.13

01 Nov 23:13
d2295fd

Choose a tag to compare

What's Changed

Full Changelog: v1.16.2...v1.17.0

v1.17.0-RC4 Veto system & Python 3.13

28 Oct 20:30
3795aff

Choose a tag to compare

Pre-release

What's Changed

Full Changelog: v1.16.2...v1.17.0-RC3

v1.17.0-RC2 Veto sytstem & Python 3.13

19 Oct 11:47

Choose a tag to compare

Pre-release

What's Changed

Full Changelog: v1.16.2...v1.17.0-RC2

v1.17.0-RC3 Veto system & Python 3.13

27 Oct 21:00

Choose a tag to compare

Pre-release

What's Changed

Full Changelog: v1.16.2...v1.17.0-RC3

v1.17.0-RC1 Python 3.13

25 Sep 18:20
1a86db9

Choose a tag to compare

Pre-release

What's Changed

  • Update Python to 3.13 and dependencies by @Gatsik in #1067

Full Changelog: v1.16.2...v1.17.0-RC1

v1.16.2 - Join game log

14 Sep 20:35
bc4e2a2

Choose a tag to compare

What's Changed

Full Changelog: v1.16.1...v1.16.2

v1.16.1 - Game resolution error logging

21 Jul 01:24
cbc55f3

Choose a tag to compare

This release adds a log message describing why a game outcome couldn't be resolved, and a check on startup to ensure the connected database is at the right migration version.

Deployment Notes

New config options:

  • DB_FLYWAY_TABLE [default=flyway_schema_history] The database table to look at for determining the migration version.

What's Changed

Full Changelog: v1.16.0...v1.16.1

v1.16.0 - Game join failed commands

01 Mar 07:08
be44cf7

Choose a tag to compare

Developer Notes

  • Added new message game_join_failed for sending error responses to game_join requests. Clients can use these messages to more easily cancel a failed game_join attempt, and display a localized message to the user based on the error code.
  • Deprecated the notice messages that respond with error messages for game_join requests. These are still sent in addition to the game_join_failed messages for backwards compatibility and can be ignored.

Deployment Notes

New config options:

  • LADDER_VIOLATIONS_ENABLED [default=True] Switch to enable or disable the violation tracking system
  • LADDER_VIOLATIONS_BAN_THRESHOLD [default=2] How many violations are needed to trigger a temporary ban from queuing
  • LADDER_VIOLATIONS_BAN_DURATION [default=1800] Number of seconds that each temporary ban lasts
  • LADDER_VIOLATIONS_FIRST_BAN_DURATION [default=600] Number of seconds that the first temporary ban lasts. By default the ban for the first violation is shorter than the following bans.
  • LADDER_VIOLATIONS_RESET_TIME [default=3600] Number of seconds needed since last violation to reset the counter

What's Changed

New Contributors

Full Changelog: v1.15.2...v1.16.0

v1.15.2 - Decapitation and Bugfixes

08 Feb 21:43
5244d42

Choose a tag to compare

Deployment Notes

  • Requires database version 136

What's Changed

Full Changelog: v1.15.1...v1.15.2

v1.15.1 - Dockerfile and Bugfixes

23 Jun 19:03
645d001

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.15.0...v1.15.1