Skip to content

fix: override-aware viability minimums and odd-wave trim under strict EvenTeams#11

Merged
FrancescoBorzi merged 5 commits into
mainfrom
fix/viability-minimums
Jul 2, 2026
Merged

fix: override-aware viability minimums and odd-wave trim under strict EvenTeams#11
FrancescoBorzi merged 5 commits into
mainfrom
fix/viability-minimums

Conversation

@FrancescoBorzi

Copy link
Copy Markdown
Contributor

No description provided.

IsViable and the tier-c smallest-min fallback read the raw template
MinPlayersPerTeam, ignoring Battleground.Override.LowLevels.MinPlayers.
Resolve the bucket's bracket on the candidate BG's own map and use the
same minimum core matching uses, falling back to the raw template value
when no bracket resolves.
With CFBG.EvenTeams.Enabled=1 and MaxPlayersThreshold=0 the CFBG queue
never invites an odd total, so one player of every odd wave was left
in queue forever. Re-validate the bucket first, and when the wave plus
the uninvited waiters comes out odd, leave the newest player unqueued
for this pass; the next pass picks them up. The trim self-disables
when CFBG or EvenTeams is off, the threshold is above 0, or the
module runs faction-vs-faction.
@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@FrancescoBorzi, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 13 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d116a5cc-251f-4c98-9a14-f7ab3f46a57d

📥 Commits

Reviewing files that changed from the base of the PR and between 84d05e3 and df6fc2b.

📒 Files selected for processing (3)
  • conf/mod-bg-auto-queue.conf.dist
  • src/BgAutoQueue.cpp
  • src/BgAutoQueue.h
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/viability-minimums

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@FrancescoBorzi FrancescoBorzi changed the title Fix/viability minimums fix: override-aware viability minimums and odd-wave trim under strict EvenTeams Jul 2, 2026
@FrancescoBorzi FrancescoBorzi merged commit 5dfbd53 into main Jul 2, 2026
2 checks passed
@FrancescoBorzi FrancescoBorzi deleted the fix/viability-minimums branch July 2, 2026 16:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant