Repository navigation
Surgery: switch penalty, old RPCharacters warning and physician failure report - #31
Conversation
… penalty Switching after sedation or cutting ended the operation without the healing penalty, while quitting applied it. The session end fires while the outgoing character is still loaded, so the penalty now lands on it for both. A permakill still applies none. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 46 minutes. View limit details
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Summary
Merge Risk: 🟡 Moderate · up to If the production SWITCH event arrives before the outgoing session is removed from the current-session lookup, the intended healing penalty may not apply. Confirm RPCharacters event ordering before relying on this behavior.
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. Comment |
… surgery failed With TLibs 2.3.0 but RPCharacters older than 2.16.0 there is no character provider, so every offer failed as "Both characters must be ready" with nothing logged. Surgery now warns on the first tick when RPCharacters is enabled but provides no character identity. The failure report required the physician's session to be current, so a physician who switched character or was permakilled heard nothing. It is an account message, so it now reaches the physician whenever they are online. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A patient who quit after sedation or cutting got the healing penalty, but one who switched character didn't, so switching was a free way out of a failing operation. Healing counts down in real time, so the switch cost them nothing.
The session end fires while the outgoing character is still loaded, before RPCharacters saves or deactivates it, so the penalty now lands on that character for a switch exactly as for a quit. A permakill and shutdown still apply none, and completion commands still never run on a session end.
With TLibs 2.3.0 but RPCharacters older than 2.16.0 there is no character provider, so every offer failed with "Both characters must be ready" and nothing in the log. On the first tick after startup, Surgery now logs a warning naming RPCharacters 2.16.0 when RPCharacters is enabled but provides no character identity.
The failure report also required the physician's own session to be current, so a physician who switched character or was permakilled mid-operation heard nothing, where Stage 1 told them. The report is a message to the account, so it now reaches the physician whenever they are still online. Shutdown still sends nothing.
mvn clean verifypasses: 165 tests, coverage gate met.Docs: TF-Minecraft/Docs#171
🤖 Generated with Claude Code