Skip to content

feat: add Qnamli2Packet and ServerPackets.Player.BpmPacket (17.5.0)#453

Merged
erwan-joly merged 1 commit intomasterfrom
feat/qnamli2-bpm-server
Apr 24, 2026
Merged

feat: add Qnamli2Packet and ServerPackets.Player.BpmPacket (17.5.0)#453
erwan-joly merged 1 commit intomasterfrom
feat/qnamli2-bpm-server

Conversation

@erwan-joly
Copy link
Copy Markdown
Contributor

@erwan-joly erwan-joly commented Apr 24, 2026

Two missing schemas that were flagged by the validator:

  • Qnamli2Packet — matches qnamli2 100 #rl 1646 13 2514 Gladi.
  • ServerPackets.Player.BpmPacket — matches the compact bpm 0 0 0 server form, distinct from the existing client-side request packet.

Packets directory placement confirmed: all ClientPackets.* live under src/NosCore.Packets/ClientPackets/ and all ServerPackets.* under src/NosCore.Packets/ServerPackets/ (scanned tree, no mismatches).

Summary by CodeRabbit

Release Notes

  • New Features

    • Added support for two new in-game server packet types, expanding protocol communication capabilities.
  • Documentation

    • Updated ServerPackets documentation to reflect newly supported packet formats.
  • Chores

    • Incremented package version to 17.5.0.

- `qnamli2 100 #rl 1646 13 2514 Gladi` — new class, mirrors QnamliPacket
  with an extra trailing string.
- `bpm 0 0 0` server-side — compact 3-byte marker, distinct from the
  existing client-side BpmPacket that ships the full quest list.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@erwan-joly erwan-joly merged commit 3bdfcfb into master Apr 24, 2026
@erwan-joly erwan-joly deleted the feat/qnamli2-bpm-server branch April 24, 2026 09:47
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 24, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: b6cd224f-2605-4eff-b8d7-299768fe1807

📥 Commits

Reviewing files that changed from the base of the PR and between ef78e9e and 6046649.

📒 Files selected for processing (4)
  • documentation/DocumentationTest.PacketsDocumentation.verified.md
  • src/NosCore.Packets/NosCore.Packets.csproj
  • src/NosCore.Packets/ServerPackets/Player/BpmPacket.cs
  • src/NosCore.Packets/ServerPackets/Quest/Qnamli2Packet.cs

Walkthrough

This pull request introduces two new server packet implementations (BpmPacket and Qnamli2Packet) to handle additional in-game message formats. The project version is incremented to reflect these additions, and documentation is updated to reflect the new packet types.

Changes

Cohort / File(s) Summary
Packet Definitions
src/NosCore.Packets/ServerPackets/Player/BpmPacket.cs, src/NosCore.Packets/ServerPackets/Quest/Qnamli2Packet.cs
New packet classes with indexed byte/int/string properties for serialization/deserialization of bpm and qnamli2 server packet formats. BpmPacket defines three byte fields; Qnamli2Packet defines six properties including quest and target identifiers.
Project Configuration
src/NosCore.Packets/NosCore.Packets.csproj, documentation/DocumentationTest.PacketsDocumentation.verified.md
Package version bumped from 17.4.0 to 17.5.0. Documentation updated with references to the two new InGame packet types in Player and Quest sections.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

  • PR #440: Deferred the qnamli2 packet implementation that this PR now completes
  • PR #446: Previously attempted to add both Qnamli2Packet and BpmPacket with similar structure and intent
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/qnamli2-bpm-server

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant