[valzargaming]

Summary

Moderator::scrutinizeCkey() runs from GameServer's 180-second serverinfo timer for every connected player. While hosted verification is unavailable, Verifier::get() throws VerifierException('Hosted verification unavailable'). Nothing caught it, so the bot died with:

PHP Fatal error:  Uncaught Civ13\Exceptions\VerifierException: Hosted verification unavailable in src/Civ13/Verifier.php:1187
#0 src/Civ13/Moderator.php(172): Civ13\Verifier->get('ss13', 'valzargaming')
#1 src/Civ13/GameServer.php(510): Civ13\Moderator->scrutinizeCkey('valzargaming')

This took the portable VZGCivilizationbot (Persistence/Gaia server) offline on 2026-10-28 10:32 and again on 2026-10-29 12:20, and control.php start does not relaunch after a crash exit.

Changes, in Moderator only:

• scrutinizeCkey(): if verification status is unknown, skip the new-account checks and log a warning. An unknown status is never treated as unverified, so verified players are not banned during an outage.
• Chat moderation: if the admin lookup throws, skip the ban for that message and log a warning, instead of crashing or risking a ban on staff.

Testing

• php -l src/Civ13/Moderator.php: no syntax errors.
• Not covered by an automated test; Moderator needs a full Civ13 instance. The live check is the portable bot staying up with a player connected while verification is unavailable.

Not in this PR

• control.php start does not restart the bot after an abnormal exit (only after a reload request).
• Repeated Unhandled promise rejection ... VerifierException and Could not create a MessageBuilder for test1714 (GameServer.php:579) in stderr; they are logged but not fatal.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Bug Fixes
  • Improved moderation reliability when account verification is unavailable. New-account checks and chat enforcement are skipped rather than proceeding with incomplete verification, and a warning is logged.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Moderator verification lookups now catch and log VerifierException. Account scrutiny returns without running new-account checks when lookup fails. Chat moderation returns false before the admin check and warning or ban flow when lookup fails.

Changes: Moderator Verifier Error Handling

Layer / File(s)	Summary
Handle verifier lookup failures src/Civ13/Moderator.php	scrutinizeCkey logs verifier exceptions and skips subsequent new-account checks. __relayViolation logs verifier exceptions and returns false before the admin check and warning or ban flow.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Merge Risk: High · up to bb95e

The PR's goal is to keep the bot online during verification outages, but the periodic player check can still crash it. That happens when a newly seen player with existing log history is scrutinized, because the verification lookup inside ckeyinfo runs before the new guard. Chat relaying also still fails during an outage. That failure makes logins return an error and skip the new-account and panic checks. Both gaps should be fixed before merging.

Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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