[TACZ] CallOfDuty Matchmaking

CODMatchmaking 1.1.6 — Changelog

  Hotfix release focused on stability — closes seven bugs uncovered by a code audit. No new features.

  Bug Fixes

  Stability / Crash Prevention

  - Fixed server crash at the end of the vote phase when no votable maps remain. If all secondary maps were deleted or
  invalidated while a vote was in progress, getVoteWinner() would call Random.nextInt(0) and crash the server. The vote
  now gracefully aborts with a chat warning and sends players back to the lobby.
  - Fixed crashes on Gun Game maps with no loadouts configured. Previously, since 1.1.5 allowed Gun Game maps to appear
  in lists even without loadouts, starting such a match could lead to IndexOutOfBoundsException on kill/demote. Gun Game
   matches are now refused at countdown start with a clear message: "Cannot start: Gun Game requires at least one
  loadout configured on this map." The demote-on-suicide path also has a defensive guard.
  - Fixed potential NullPointerException in teleportToSpawn(). The method now early-returns if player.getServer() is
  null, instead of dereferencing it.

  Player Experience

  - Lobby teleport no longer silently strands players when the lobby spawn isn't configured. If an admin hasn't set the
  lobby with /tdm setlobby, players returning from a match are now sent to the world spawn instead of being left in
  place. A yellow warning is shown to the player telling them to ask an admin to configure the lobby.

  Admin / Diagnostics

  - Invalid gameMode values in map JSON files are now logged. Previously, a typo or stale enum name (e.g. after a
  version migration) was silently swallowed and the map defaulted to TDM with no indication. The mod now writes a
  warning to the server log: Map '<name>' has unknown gameMode '<value>' — falling back to TDM.