bowmap-10 Packet code
Bowmap · bowmap.git · Tickets
A Bowmap Ticket (Completed):
Ticket · History
- October 10, 2026 Created (title: 10: Packet code)
Changes
@@ -0,0 +1,21 @@+---+title: "10: Packet code"+permalink: bowmap/10/+ticket: open+---++*A [[bowmap-tickets|Bowmap Ticket]]:*++- [x] Rename `net.bowmap.server.protocol.*` to `net.bowmap.server.packet.*`, as "protocol" isn't a great term. I guess "packet" isn't a great term either lol.+- [.] Remove identifiers as keywords, just use ns/name maps, and use `"minecraft"` as the minecraft namespace. - Ended up being kind of annoying :p Specifying registries with maps when they are really atomic identifiers.+- [x] Remove `types.clj`, just depend on the reader in `network.streams` and put the max varint size there.+- [x] `protocol.entity` might be a game concept (I don't think it is, it's about entity _ids_ which are a packet thing)+- [x] `protocol.block` _is_ a game concept, move it+- [x] Update old usages of "protocol" and "Minecraft"+- [x] Don't encode tags as strings++Questions:+- What about phases?+- What about encryption and compression? These are really about the byte format rather than the packets themselves, perhaps they belong in `packet.serialize`. Or maybe they're networking things instead, but they still depend on the connection state.++See also [[bowmap@9]]. - October 20, 2026 Change formatting
Changes
@@ -18,4 +18,4 @@ - What about phases? - What about encryption and compression? These are really about the byte format rather than the packets themselves, perhaps they belong in `packet.serialize`. Or maybe they're networking things instead, but they still depend on the connection state. -See also [[bowmap@9]].+See also [[bowmap@9|9: improve readers and writers]]. - October 20, 2026 Remove redundant permalinks and titles
Changes
@@ -1,6 +1,5 @@ --- title: "10: Packet code"-permalink: bowmap/10/ ticket: open --- - October 21, 2026 Update the rest of the ticket pages to use numbers (title: 10: Packet code → Packet code, status: none → closed, type: none → enhancement, resolution: none → completed)
Changes
@@ -1,10 +1,10 @@ ----title: "10: Packet code"-ticket: open+title: Packet code+status: closed+type: enhancement+resolution: completed --- -*A [[bowmap-tickets|Bowmap Ticket]]:*- - [x] Rename `net.bowmap.server.protocol.*` to `net.bowmap.server.packet.*`, as "protocol" isn't a great term. I guess "packet" isn't a great term either lol. - [.] Remove identifiers as keywords, just use ns/name maps, and use `"minecraft"` as the minecraft namespace. - Ended up being kind of annoying :p Specifying registries with maps when they are really atomic identifiers. - [x] Remove `types.clj`, just depend on the reader in `network.streams` and put the max varint size there. - October 24, 2026 Rename tickets to <project>-<number> <title> (renamed from bowmap@10.md, title: Packet code → none)
Changes
@@ -1,5 +1,4 @@ ----title: Packet code status: closed type: enhancement resolution: completed@@ -17,4 +16,4 @@ - What about phases? - What about encryption and compression? These are really about the byte format rather than the packets themselves, perhaps they belong in `packet.serialize`. Or maybe they're networking things instead, but they still depend on the connection state. -See also [[bowmap@9|9: improve readers and writers]].+See also [[bowmap-9 Improve readers and writers]]. - October 24, 2026 Replace ticket status, category and resolution with ticket (status: closed → none, resolution: completed → none)
Changes
@@ -1,7 +1,6 @@ ----status: closed+ticket: completed type: enhancement-resolution: completed --- - [x] Rename `net.bowmap.server.protocol.*` to `net.bowmap.server.packet.*`, as "protocol" isn't a great term. I guess "packet" isn't a great term either lol.