Repository navigation
fix(xp): stop banking experience at the level cap - #430
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 0 remain after this review. 📝 WalkthroughWalkthroughXP progression now uses shared logic for multi-level awards, remainder preservation, and level-60 capping. Capped characters receive no XP, rested XP drain, or XP event. Unit and ignored integration tests cover these rules. ChangesXP progression cap
Estimated code review effort: 3 (Moderate) | ~25 minutes Merge Risk: ⚪ Minimal · up to Level-60 characters now discard further XP and do not consume rested XP or emit XP events for capped awards. The cap, multi-level remainder, and kill behaviors are covered by the supplied tests, with no current merge-blocking risk identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
44852b5 to
9c701ab
Compare
|
@coderabbitai full review |
✅ Action performedFull review finished. |
Characters at level 60 could keep banking XP, and a large award could overflow the stored XP before leveling. XP progression now uses a wider intermediate value, discards the remainder when it reaches level 60, and stops capped kill awards before they drain rested XP or emit an XP event.
The shared non-grey kill calculation stays unchanged because Drain Soul rewards and Hunter pet progression also use it. This addresses the XP-cap finding in the performance and correctness report.
Verification:
The private tests use fresh in-memory processes. No existing realm was changed.
Implemented by GPT-5.6 Sol and GPT-6 through Codex, reviewed by GPT-6 through Codex.
Summary by CodeRabbit