Skip to content

Releases: Mesharsky/CS2-Advanced-TeamBalance

Advanced Team Balance - V5.2.0 - Beta

20 Sep 00:04
@Mesharsky Mesharsky
v5.2.0-beta
70da1d4

Choose a tag to compare

View all tags
Advanced Team Balance - V5.2.0 - Beta Latest
Latest

CS2 Advanced Team Balance - v5.2.0

Bug Fixes

  • Fixed an issue where the boost feature didn’t always trigger - it now applies correctly when configured, before just a message was printed but nothing happened lol
  • Stopped boost messages from showing when boosts were disabled. They’ll now only appear if BoostAfterLoseStreak > 0 and not in OnlyBalanceByTeamSize mode.
  • Cleaned up streak debug messages so they now show the right T/CT values.

New Features

Progressive Boost System

  • Added a new tiered boost system: the longer your team’s losing streak, the bigger the boost.
  • You can fully customize tiers (e.g. 3 rounds = 10%, 5 rounds = 20%, 7 rounds = 30%).
  • New config options:
    • ProgressiveBoost (true/false)
    • [Balancing.BoostTiers] for defining the tiers

Admin Commands

  • New preview commands: css_balancepreview / css_previewbalance
    • Lets you check upcoming balance changes before they happen
    • Shows current team averages and the proposed swaps
    • Reports how many moves would be made

Balance History Tracking

  • The plugin now keeps a history of balance operations in daily log files.
  • Each entry includes team counts, average skills, and the exact changes made.
  • Config: EnableBalanceHistory (true/false)
  • Logs are saved to: logs/balance_history_YYYY-MM-DD.log

Improvements

Balance Logic

  • Boost notifications are now clearly shown when boosts are actually applied.
  • Balance messages explain why players were moved (team size vs skill).
  • Debug logging for boosts is more transparent.
  • Config option: ShowBoostOnApplication (true/false).

Performance / Validation

  • Optimized LINQ queries for smoother performance.
  • Reduced redundant calculations when comparing team strength
  • Configs are validated automatically, invalid values get corrected instead of breaking things.
  • Added a locking mechanism to prevent race conditions when multiple balances run at once.
  • If something goes wrong, the system falls back to simple team-size balancing (just by team size)
  • Improved error logs with fallback mechanism
Assets 3
Loading