Repository navigation
Releases: NosCoreIO/NosCore.Packets
Releases · NosCoreIO/NosCore.Packets
Release list
21.1.4
21.1.3
Merge pull request #541 from NosCoreIO/fix/exchange-scope-and-trailin…
21.1.2
fix(einfo): escape the spaces in the monster name (#509)
Name ends the e_info line, and a last field keeps its spaces so free text
like a chat message survives. A monster name is a value, not free text, and
EscapeSpaces already exists for exactly that - GInfoPacket, MlInfoBrPacket
and MlintroPacket declare it. This one did not, so consumers were left to
call Replace(' ', '^') themselves before handing the value over.
929 of the 1109 monster-info lines in a capture carry a name with a space.
Test asserts the serialised tail, and fails on the raw name without the
attribute.
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
21.1.1
fix(serializer): a sub-packet's last field is its own, not the parent…
21.1.0
The separator a string field is escaped against is the one it is join…
21.0.0
chore: bump NosCore.Packets to 21.0.0 (#495) Major rather than patch: GidxFamilySubPacket is gone and GidxPacket's FamilyIdentifier became a nullable FamilyId, so the public surface changed even though nothing in NosCore referenced either. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
20.0.3
fix: IsValid accepts empty strings for non-nullable string fields (20…
20.0.2
fix: AscrPacket leading-blank field (20.0.2) (#460) vanosilla UiPacketExtension emits `ascr <CurrentKill> ...` with a literal double space after the header. Adds a LeadingBlank field (non-nullable, defaults to empty string) at index 0 and shifts all other indices by +1. Same fix pattern as NsTeSTPacket (20.0.1) and SqstPacket. No in-tree consumer uses AscrPacket, so this ships as a patch. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
20.0.1
fix: NsTeSTPacket.LeadingBlank defaults to empty string (20.0.1) (#459) The field models the literal double space vanosilla emits after the `NsTeST` header; without a non-null default the serializer emits "-" for an unset property, producing "NsTeST - 0 …" on the wire. Make the property non-nullable with an empty-string default so consumers don't have to remember to set it. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
20.0.0
feat!: 20.0.0 - CMapPacket.IsEntering rename, add gmsg/gexp/rsfn/minf…