Add forced movement guri packet fields - #513
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (4)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe change extends ChangesGuri packet serialization
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The change adds optional forced-movement values while preserving shorter Guri packets and includes passing build and test verification. No actionable merge-blocking risk remains beyond normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 4 functions across 2 files. (2 skipped: 2 unsupported.)
✨ 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 |
|
All checks are green and the full local test suite passes (130/130). This package change is required by the general Type 40 forced-movement refactor in NosCore. Could a maintainer please review and merge it? |
|
Closing because this change will be used only in a local private build. |
Extends the existing server GuriPacket with the three optional fields required by forced movement packets.
Adds serialization coverage for both push/pull and dash layouts while preserving existing shorter guri packets.
Verification:
Summary by CodeRabbit
New Features
Tests
Release