Skip to content

Commit

Permalink
Fix changelog from rebase
Browse files Browse the repository at this point in the history
  • Loading branch information
nickdnk committed Mar 20, 2023
1 parent 08b235b commit 6640d4f
Showing 1 changed file with 2 additions and 7 deletions.
9 changes: 2 additions & 7 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -172,13 +172,8 @@ details.
immediately following the end of the series, but now waits until the restore timer fires. Get5 will be in `post_game`
until the timer runs out, similarly to when waiting for the next map. This means that GOTV broadcasts will have a
chance to finish before Get5 releases the server.
7. The map is now always reloaded when a match configuration is loaded, even if the server is already on the correct
map. Similarly, if doing in-game map selection (veto), the map is always changed to the first map in the series, even
if the server is already on that map. This reverts this change
from [0.13](https://github.com/splewis/get5/blob/development/CHANGELOG.md#0130). You can disable this behavior
via [`get5_always_reload_map`](https://splewis.github.io/get5/dev/configuration/#get5_always_reload_map), but you
should only do this if you know your server is *always fresh*; if it was just rebooted or started as a container. The
reason we force-reload the map is to prevent various game state bugs caused by previous matches, such as [the warmup
7. The map is now always reloaded when a match configuration is loaded *if* a game was previously played on the same map
with no map reload in between. This is in effort to clear the game state and prevent bugs such as [the warmup
countdown timer stopping at 0.01](https://github.com/splewis/get5/issues/976).

### New Features / Changes 🎉
Expand Down

0 comments on commit 6640d4f

Please sign in to comment.