fix: avoid animation phase edge-case crashes#1683
fix: avoid animation phase edge-case crashes#1683Kizuno18 wants to merge 2 commits intoopentibiabr:mainfrom
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
📝 WalkthroughWalkthroughAdds an MSVC compile definition Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
|
Wouldn't it be good to add some warning logs to this PR? |
getSpeed() returns float (m_speed / 100.f), but was being stored as const int, truncating values < 1.0 to 0. This triggered the speed <= 0 guard and killed animations for any attached effect with speed < 100 (e.g. wings/auras configured with speed = 0.5). Also fixes thingTye typo to thingType in attachedeffect.cpp.
|
@CodeRabbit review |
✅ Actions performedReview triggered.
|
Hey folks!
This is a small safety pass to avoid a couple of nasty edge cases that can crash the client when assets/thing types are incomplete or in a weird state.
No functional changes intended beyond not crashing in those scenarios.
Cheers!
Summary by CodeRabbit
New Features
Bug Fixes