Skip to content

fix: operator warnings and docs for CrossFaction and the first-pass warning window#12

Merged
FrancescoBorzi merged 3 commits into
mainfrom
fix/warnings-and-docs
Jul 2, 2026
Merged

fix: operator warnings and docs for CrossFaction and the first-pass warning window#12
FrancescoBorzi merged 3 commits into
mainfrom
fix/warnings-and-docs

Conversation

@FrancescoBorzi

Copy link
Copy Markdown
Contributor

No description provided.

CountUninvitedWaiters split waiter counts by gInfo->teamId, which CFBG
staging overwrites on every staging attempt and does not restore on
failure, so with CrossFaction = 0 per-faction viability drifted across
passes. Split by RealTeamID instead, which the core writes exactly once
at queue join and never mutates.

Also warn once per config load when CrossFaction = 1 runs without an
active cross-faction matcher (uninvited players sitting in a
faction-specific NORMAL bucket can never pop on a stock core), and
document the matcher coupling in conf.dist and the README.
LoadConfig warned when WarningLeadTime swallowed the Interval half of
the warning window but not the InitialDelay half: with
0 < InitialDelay <= WarningLeadTime the first pass silently queues
everyone without the advertised broadcast. Log-only; default configs
(InitialDelay = 0) stay silent.
@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: 5 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: b6296872-840d-48d0-9c02-a25d7413059a

📥 Commits

Reviewing files that changed from the base of the PR and between 5dfbd53 and bd8a06a.

📒 Files selected for processing (4)
  • README.md
  • 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/warnings-and-docs

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 merged commit 6d709fb into main Jul 2, 2026
2 checks passed
@FrancescoBorzi FrancescoBorzi deleted the fix/warnings-and-docs branch July 2, 2026 16:51
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