Nexori 2.2.0

Backend-Driven Matchmaking

• Added BACKEND_DRIVEN queue mode for servers that want an external backend to own matchmaking decisions.
• Backend-driven queues let your service decide match assignments using custom logic such as ELO, regions, tournaments, party rules, load balancing, or any other matchmaking algorithm.
• Added /nexori/sync heartbeat support so Nexori can send queue, arena, active match, and pending assignment ACK state to your backend.
• Added backend assignment execution for creating matches from backend responses.
• Added assignment ACK reporting so Nexori can report whether an assignment was launched, rejected, or failed.
• LOCAL_FIFO queues remain available for standalone servers that want Nexori-managed FIFO matchmaking without a backend.

Backend Result Reporting

• Added event-driven match result reporting through POST /nexori/results.
• Arena servers can report completed match results without needing to run matchmaking heartbeat.
• Result reporting can be enabled separately from backend-driven matchmaking.
• Completed result reports are stored durably and retried if the backend is temporarily unavailable.
• Backend result payloads include Nexori match identity, player outcomes, rules engine id, and optional custom minigame data.

Backend Menu

• Added Backend Config and Terminal views to Nexori Menu V2.
• Operators can configure backend origin URL, API key/server token, sync interval, result reporting, retry interval, region, and request timeout from the in-game UI.
• Added backend terminal visibility for sync and result requests, including request type, HTTP status, recent health, and backend activity.
• Queue editing now supports choosing between LOCAL_FIFO and BACKEND_DRIVEN matchmaking modes.

Manual Game Ownership

• Added rulesEngineId support for Manual games.
• The Games UI now shows a Rules Engine ID field when Manual is selected.
• Manual games now require a Rules Engine ID before saving from the UI.
• Third-party rules mods can read rulesEngineId from active match info and only control matches meant for them.
• This allows multiple minigame/rules mods to be installed on the same arena server without each mod trying to control every manual match.

Minigame Public API

• Expanded the existing public minigame API into a cleaner rules-mod integration surface.
• Added active match context APIs so rules mods can read match identity, queue id, arena id, backend assignment identity, expected players, active players, eliminated players, placement state, required result players, accumulated outcomes, and rulesEngineId.
• Added separated runtime actions for rules mods:
  • setPlayerOutcome(...)
  • setPlayerSpectator(...)
  • returnPlayerToLobby(...)
  • submitFinalMatchResult(...)
• setPlayerOutcome(...) lets rules mods record player results during the match as gameplay happens.
• submitFinalMatchResult(...) completes the match using the outcomes accumulated during runtime and optionally queues backend result reporting.
• Added logical spectator state for rules mods that want to track players who are still part of the match context but are no longer actively playing.
• Added custom JSON result data so minigame mods can attach their own stats to backend result reports, such as captures, damage, objectives, chests looted, beds broken, or any other mode-specific data.
• Added idempotent final result submission with stable result hashing.
• resolvePlayerOutcome(...) remains available but is now deprecated because it combines outcome resolution and return-to-lobby behavior. New minigame mods should use the separated API methods instead.

Arena Match Identity

• Arena runtimes now retain match identity across backend-driven and local launches:
  • local match id
  • external match id
  • assignment id
  • queue id
  • arena id
  • expected players
  • rules engine id
• This identity is exposed to rules mods through the public API and included in backend result reports when available.

Compatibility Notes

• Existing queue configs without a matchmaking mode are treated as LOCAL_FIFO by default, so older queues should continue using Nexori-managed local matchmaking after upgrading. Server owners should still review their queues in the UI after updating.

• Existing 2.1.0 minigame mods using findActiveMatchId(...), findActivePlayerUuid(...), findMatchPlacementState(...), or findMatchResolutionTriggerId(...) remain compatible.

• Mods using resolvePlayerOutcome(...) should still work, but the method is now deprecated because it combines player outcome and return-to-lobby behavior. New rules mods should migrate to the separated API:

  • setPlayerOutcome(...)
  • returnPlayerToLobby(...)
  • submitFinalMatchResult(...)