Improve clientside transform logic#189
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 (3)
💤 Files with no reviewable changes (2)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughRPC handlers for 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 |
…ransform-improvments # Conflicts: # code/framework/src/world/client.cpp
This pr makes logic related to updating transform of entities more robust. getting rid of unnecessary callback, replaces potentially crashing code with simple method that make sure updating transform never crash, removed unnecessary method to update transform.
Now if you want to listen for transform changes create flecs system that listen for "Transform" being changed.
Summary by CodeRabbit