Add UPON_COOLDOWN_SET bonus end type for Energy Drink#2356
Add UPON_COOLDOWN_SET bonus end type for Energy Drink#2356kanyaveral wants to merge 1 commit intomainfrom
Conversation
Energy Drink's COOLDOWN-30s bonus was incorrectly routed through UPON_HARVEST_ACTION, causing two bugs: 1. Feeding regular food wiped the drink (feed resets harvest bonuses but never sets cooldown — bonus destroyed for nothing) 2. Liquidation never consumed it (killer gets permanent -30s cooldown as long as they keep killing without collecting) New UPON_COOLDOWN_SET end type is consumed after every resetCooldown() call: deploy, collect, stop, and liquidate. Feeding no longer touches it.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughThe pull request adds support for a new bonus end type, UPON_COOLDOWN_SET, enabling bonuses to be cleared when cooldowns are set. Changes span client-side bonus handling (getters and parsing) and contract-side bonus reset logic across multiple harvest systems. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
No actionable comments were generated in the recent review. 🎉 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 |
Summary
UPON_COOLDOWN_SETend type so cooldown bonuses (Energy Drink) live on a separate path from harvest bonusesLibBonus.resetUponCooldownSet()is called after everyresetCooldown()in: HarvestStart, HarvestCollect, HarvestStop, HarvestLiquidate"til next cooldown")clearAll()updated to include the new typeBugs Fixed
resetUponHarvestActionwhich wiped the drink's bonus, even though feeding never sets cooldownNotion Data Change Required
In the allos table, update the
COOLDOWN-30srow's Terminator column:Without this data change, the Energy Drink will still register under the old end type and the code fix won't take effect.
Summary by CodeRabbit
Release Notes