BNETDocs Redux

Idea: Set it up so users can submit documents themselves, set up a section in right side menu showing user submitted documents.

Idea: Make it possible for users to comment on news posts, as well as any other sections on the website.

Bug Report: bnls.dementedminds.net is no longer functional. Also, the status sections at right side menu is no longer functional. Needs to be fixed.

Request: Search script needs to be coded.

idea: make the quick jump work with packet id's also like 0x0F and have it pull up a list of the 0x0F packet's or if there's only 1 go straight to it

What do you guys think about setting up D2GS and W2GS to be split by packet type GameServer and GameClient, the packets are related to each directly Server//Client each direction the packets are wildly different.. If naming scheme's were updated to Diablo II Warcraft III (Game title), then D2GS, D2GC, W3GS, W3GC (or anything similar) it would probably help organization in the long run..
I've been hesitant about adding S>C packets for D2 because of this...

... i don't understand.... how is D2GS and W3GS any different? client sends -> to server then server responds -> to client just like all the other protocols.. we don't setup BNCS and BNCC...

D2GS the packets aren't like bncs and mcp where the send and recieve packet basically match up.. In D2 the C>S packet for 0x15 is to send chat to game while the S>C packet 0x15 is to reasign player at position.
None of the D2GS C>S packets corrispond to the S>C packets the way they do for bncs/mcp etc. I'm assuming its the same way for War3.

Poke thru this sometime will give you an idea of what I mean:
http://files.serverhash.com/code/other/D2Packets.chm

Compare the d2 packets for 0x15, 0x26, 0x16 server > client vs client > server they generally have nothing to do with one another unlike bncs/mcp where they generally are a responce or similar type of information etc.

hmm... well if you look at the packet list... we didn't group the s->c and c->s so.. all you really need to do is post the packets with the correct name then where it says "related items" add the corresponding packet...

Yah, that's something I had asked Don to do that does help was just thinking long term if we add them all the list is going to get big.

Cleaning up the D2GS packets some, and will start adding more soon.

Suggestion: A packet submission form where logged in users can submit new packets and information to be reviewed and added.

I may work on this idea some soon.

Wheres the SCGS Messages, there's a solid amount of info people have put out, and the formats for the packets, that are accurate enough.

waiting for don to get around to putting that back up... remember the whole server crash thing guh.. i woulda done it my self but i have yet to find that part of the code lol..

be patient we are both very busy... also there is a new version of bnetdocs coming out soon as posted on the news

The messages were lost in the server crash. So they will have to be re-added.

As for the new version of BNETDocs, yea, been working on it. My job has me working alot, so it's hard to find time, but I'm definitely working in my spare time.

I have the day off on Friday, so I aim to put in a very decent amount of work in BNETDocs.

Your bnls server status isnt working that great. HDX's servers were offline and on this site they are marked as online

The bnls server status script checks status every hour, so if a server goes down right after the script checked, the site wouldn't see it until it checks back a hour later. Maybe that's what you saw? If the bnls server was down for more than a hour, and the site still said it was online, then yes, there's a problem. Can you tell me which is the case?

it might have lasted more than a hour

You should add a page with the current VerBytes like this page here: http://www.bnetdocs.org/old/contentbb03.html?Section=d&id=5

Also I think a page with the flags should be added like here:
http://www.bnetdocs.org/old/content49b6.html?Section=d&id=1
I think the icons should be displayed as well with those.

Don, fix it so that we can properly add tables into posts/docs/packets.

Remove the "/index.html" and all the pages it links to on this server.

@Jailout2000, already done. But thanks for pointing it out.

@Hdx, will work on it.

@Alendar, re the flags, good idea. Re the verbytes, already done by Hdx. http://www.bnetdocs.org/?op=doc&did=12

@Myst_Doom, fixing the redirector isn't really a priority, but it's definitely on the todo list. Very few people (if any at all) make use of it.

@The rest, thanks for the input. I'm working on BNETDocs v2.0, which is why you're not seeing any further updates to BNETDocs Redux. :-)

When will the flags page be added?

The flags page is added, but it doesnt contain any useful information. Especially for channel flags.

This is for a far-future to-do, but you should integrate the forums into this style page. Each forum being a link on the left (like a packet/documentation page), and each topic being a link on that docs page that leads to a user-comments styled topic page.

@ZergMasterl: Forums will be integrated with the site in BNETDocs v2.

@Jailout2000, comment on the flags page stating what information needs to be included and an admin will add it. The admins usually are very good about adding stuff.

http://www.bnetdocs.org/?op=packet&pid=360 - I always thought the limit to how long a message could be was 224, not 223. Correct me if I'm wrong.

F7 1E 33 00 00 00 00 00 00 00 00 00 00 E4 17 00 00 00 00 7C 72 41 75 74 6F 52 65 66 72 65 73 68 00 01 00 02 00 17 E0 7F 00 00 01 00 00 00 00 00 00 00 00

Any idea what this means? It comes from a Auto Refresh program for Warcraft III... And the header says that it's Warcraft III (F7 1E 33 00), It sends 0x1E, with the length of 51 (0x33) bytes... The name is AutoRefresh, which accounts for the 41 75 74 6F 52 65 66 72 65 73 68... I just want some confirmation, and maybe add it to the W3GS documentation since that documentation has nothing yet...

Thanks...

Add Telnet/Chat-icon packets to the packet list, if you will. Contact me for the full list, since I haven't seen anyone besides myself have the complete, correct, list. I can also help add the documentation on each Telnet packet.

On a side note, that should be highly noted, you need to sanitize your PHP to SQL code (use the PHP function stripslashes or addslashes, one of those two). In order to add a ' you need to backslash it \' which some people don't know how to do.

Why were the following removed from the Document list?

BNLS Checksum Algorithm
Diablo II Game Server Accept Sequence
Diablo II Realm Server Logon Procedure
Icons.bni
NLS/SRP Protocol
Notational Conventions
Warcraft III Profile Requests