New packets at bnetdocs?

[Networks]

I don't mean to start a commotion but are there a few new packets at bnetdocs?

Some I don't remember seeing as well as others:

[C>0x59]        SID_SETEMAIL
[S>0x59]    SID_SETEMAIL
[C>0x5A]    SID_RESETPASSWORD
[C>0x5B]    SID_CHANGEEMAIL
[C>0x32]        SID_CHECKDATAFILE
[S>0x32]    SID_CHECKDATAFILE

[Arta]

Yup. Like I said a while back, BnetDocs is changing muchly

[dxoigmn]

Yup. Like I said a while back, BnetDocs is changing muchly

Nice.  Now how about adding some public documentation on the rest of the SID_AUTH_* packets?  I'm sure it's already on the site, just priviledged.

[UserLoser.]

You can thank your favorite person ever for most of those newer packets up there and Arta ofcourse for BnetDocs

[Mephisto]

Bah!  :p

[Arta]

Yup. Like I said a while back, BnetDocs is changing muchly

Nice.  Now how about adding some public documentation on the rest of the SID_AUTH_* packets?  I'm sure it's already on the site, just priviledged.

It's not actually. There is no more privileged (practically none anyway). The SID_AUTH stuff isn't displayed because it's horribly incomplete and no one seems to have any decent notes for me to work with! Contributions welcome.

Just so that everyone knows:

Nearly everything on BnetDocs is now visible to everyone. The following is a list of reasons why things may not be displayed:

- Incomplete information to the point that the documentation would be more confusing than useful. This accounts for most of the stuff that's not displayed.
- Information that we deem may be damaging to Battle.net or its users if it were publicised. This king of thing generally isn't added to the site at all, for obvious reasons.
- Information that the contributor has requested to remain private. There's not much of this.
- Information about things that are no longer used (ever).

Of the things that are incomplete, I'm doing my best to bring them up to publishable standard. I look over the things that are marked private regularly to make sure it's still worth keeping them private.

When BnetDocs started, it was my strong feeling that the purpose of the site should be to provide people with a 'leg up' - to get people started, to the point where they could do research and figure things out for themselves. When I was starting, that is what I wanted, and that was the motivation behind keeping so much of the site private. I no longer feel that that approach is valid. There is now so much information and source code available that no one really needs to do any research unless they want to.  Thus, I feel it's more important to have an authoritative source of information that is available to everyone. For that reason, I have made as much information public as I can, user accounts are now optional, and I've worked on the site a lot to make it easier and quicker to use and to enable a more collaborative effort for updates and additions to the site.

As always, suggestions/contributions are welcome!

[Networks]

Perhaps a way to submit packet information may get you more complete and more  contributions.

[Blaze]

Maybe a page to show added packets? The news page doesn't really cover this.

[tA-Kane]

Arta, see the bug in Related Links for C->SID_SETEMAIL? It's listing S->SID_SETEMAIL twice.

[Arta]

Thanks Kane, I'll have a look.

Every page contains a "contribute/report error" link. That can be used to send me things. Alternatively you can email me.

I'll add a recently modified list to the news page, that's a good idea

[tA-Kane]

Every page contains a "contribute/report error" link. That can be used to send me things. Alternatively you can email me.

Bleh. I wanted people to see the bugs in BnetDocs. It's so good, it's just too good to be true. There has to be something wrong with it! 

[Mephisto]

Thanks Kane, I'll have a look.

Every page contains a "contribute/report error" link. That can be used to send me things. Alternatively you can email me.

I'll add a recently modified list to the news page, that's a good idea

You could just change the color of the links for newly added packets and provide a legend of some sort.

[Kp]

You could just change the color of the links for newly added packets and provide a legend of some sort.

That'd be fine for the short term, but what if every new contribution needs its own color?  Pretty soon it gets tedious.   Best just to post a date-changed summary somewhere if people care about additions/changes.

[R.a.B.B.i.T]

Or just make new contributions in red, and turn them to blue after a while (~month).

@Arta: thanks for BnetDocs   I have decoded a few packets, but much of my work is based off of BnetDocs.  It's also a great reference site.  My favorite upgrade so far was the move of the database (which made the site faster).  Keep up the hard work!

[Blaze]

On the topic of bnetdocs, me and hdx noticed that the search no longer works at all. After searching you just get returned to the main search page.