Ohhh trust me, you do.
Theres 100's of features in vbGORE that I have completely forgot about that I find every now and then just because the project has become so large I even loose my way around it sometimes.
Also, if you ever want to have other programmers or distribute your code, it is a must to have. If you are going to use this method, it is a pretty safe thing to say that you will need a lookup table of "some sort". I suggested the above since I like to be able to type in a command where all my packet IDs are gathered up and nothing more, and have a list of the packets be shown. Since I use binary packets, too, misformatting one part of a packet can ruin the whole entire packet for the one recieving it (whether it is the server or client).
A seperate document with the packet information may be nice, but I can see it causing a bit of updating problems. For example, it'd be extra work if you want to change numbers or move things around since you have to edit it in multiple places. With this, I just have a sub that sets all the packet values, copy it from the server to client (or vise versa) and then the packet values will always match up, period. Doesn't matter then what numbers I use, as long as the names are correct.
You will also be kicking yourself if you ever take a break for a week or two and end up forgetting a bunch of the packet numbers if you dont chart them.
Another way you could do it is to format them like:
Code:
Public Const DCmd_Server_UpdateUserPos As String * 1 = C
...then type DCmd_ and press I believe Alt + Space to bring up the pop-up box, but that'd prevent you from using a lot of characters unfortunately.
@William, No. Like Gilgamesch said, I use from 1 to 236 and 238 - 255. 0 and 237 are the Sep and End chars.