The first thing we should know is what IDs are already being used by jj2. I was working on a JJ2TCP documentation a while ago and I'll quote a part of it here.
Quote:
The packet ID byte allows up to 256 different numbers, but only a very narrow range is actually used – 0x0D to 0x1B (13 to 27 decimal) to be precise, the rest are unused.
| ID | Function | Traffic | | 0x0D | Error message | C<==S | | 0x0E | Client details | C==>S | | 0x0F | Join request | C==>S | | 0x10 | Server details | C<==S | | 0x11 | Client join notify | C<==S | | 0x12 | Server player list | C<==S | | 0x13 | Join process complete | C<==S | | 0x14 | Data transmission | C<==S | | 0x15 | Download request | C==>S | | 0x16 | Level cycle | C<==S | | 0x17 | Game over | C<==S | | 0x18 | Status update | C<==S | | 0x19 | Server stopped | C<==S | | 0x1A | Status update request | C==>S | | 0x1B | Chat | C<=>S |
|
We have a lot of free packet ID's to use. JJ2 itself will currently ignore the unused so that's a good thing. Now the task is to assign a "use" (purpose) to each unused ID and make standard of it... sort of like the table shown above. I suggest we first make a list of features and possibilities. However, this is where my imagination ends. Neobeo might want to share some ideas for his dedicated server extended functionality.
__________________
<a href="http://nmap.org/"><img border="0" alt="Nmap Security Scanner" src="http://images.insecure.org/nmap/images/prop/nmap_bnr_matrix_pfos.gif"/></a>
|