howto tutorial request

[drozz]

Could a developer please take a small amout of time and post a howto tutorial for my request below? When the packet collecter is up and running, those of us who use it also have our own eqemu servers up and running. When we use the packet collector and it generates a .pf file, the only option given to us it uploading it to the people who created the collector for editing. However, some zones in databases are still not 100% npc complete. PEQ for example, is infact a great database, the closest db to live yet. Their site says classic thru velious, however there are several zones even in classic that are missing alot of npcs that effect quest scripting. Now, for some non-questers it may seem un-needed to go back and get the missing npcs from live, but to the rest of us its needed; if only for our private servers. Please understand, Im not trying to bash anyone here.. I was just using PEQ as an example of missing npcs. Getting back to the request at hand, Im not looking for the source code of the collector, Im just asking for a howto tutorial on how to use the .pf files Ive collected from live to my own server, instead of being forced to upload them. Furthermore, I feel the biggest disadvantage over devs who have been around and people who are creating their own private servers, is documentation. Yes, theres a howto forum, but really documentation like the request Ive made above would really make a difference.. since this project is suppose to be for everyone who wants to host their own servers.

having to upload without being able to implement by myself makes me feel like Im in the 40's saying yes sir, no sir like a slave working in a cotton field answering to the man. does it really have to be like this?

drozz

[Teppen]

btw, Im also drozz. I posted under teppen to note Im not a newbie and have been around for awhile.

[RangerDown]

The PF files contain raw packet data. You're free to parse them and use them for your own implementations as you like, but to do that you're gonna have to write some code. Some very ugly complicated code and you're gonna have to understand EQ packets inside and out to make sense of what's in the PF file.

That is way beyond the technical abilities of 95% of the userbase here. When something is that complex, it can't be solved in by a dev taking "a small amount of time to write a small howto." To do this would be akin to me asking a surgeon to "take a small amount of his time to write up a howto cuz my wife needs an operation but I wanna do it myself."

You are free to use the packet files for your own implementations. They are not encrypted, nor was anything about the collector designed as some conspiracy hide data from the unwashed masses. Just write your own code to parse the PF files and do what you like with them. If you can't code or don't understand the first thing about network packet structures, though, then you'll have to accept that it simply ain't gonna happen.

[Teppen]

Originally Posted by RangerDown

you're gonna have to understand EQ packets inside and out to make sense of what's in the PF file.

Then submit a guide on Understanding EQ Packets then.

A guide on Everquest Protocol Layer would be helpful too.

I hold a degree in CS. I understand Assembler, and C quite well. However, like Ive said in drozz post. Documentation that the Dev's hold out of the tutorial sections leads to the disadvantages of people who are intelligent enough to code, from further understanding the code. Ive been around long enough to know that the devs must have a typed up guide on the Everquest Protocol Layer, and more so, a guide on Understanding EQ Packets. Otherwise your telling me that all devs new and old to the projects have telepathic minds so when one knows they all know without any form of documents or verbal or typing communications between one another. If thats the case then.. well thats not the case.

To stop people from questioning the guide just put **no support for this guide** then lock the thread per guide. That way, those of us that can understand it have the resources.

Information is gained by sharing. Code is not the only thing that should be opensource, and infact alot of subprojects here are closed source but thats a totally different rant which I wont start because Ive been around since 2002 and I have lived thru the "this is closed source" excuses posts.

Oh.. I thought this looked familar. Reminds me of highschool if your not in the "click" then the door doesnt swing both ways.

[RangerDown]

Why don't I lead you to a couple of files from the source that might be of use to you:

zone/eq_packet_structs.h
? zone/eq_opcodes.h ? <--- not sure if this is the right name but something like that

I get the feeling that this is the extent of the "typed up documentation" you suspect exists. That, and a few discussion boards on the net like Hackerquest. The source code exists at SourceForge as the project name "eqemulator". In the case of network packets, with that stuff changing every other patch so it's futile to try and keep up separate documentation about it. In cases like these, the code simply has to be the authoritative source.

I've found the current crop of devs to be pretty open when it comes to asking questions about the inner workings of the system. They don't always have time to be bothered, but if you're motivated to help them they'll be motivated to help you.

[Teppen]

Im not really sure what documents posted on hackerquest forums that your are referring to, but Im certain its not what Im referring to. EQEmu has had several Dev's in the past leave do to conflict between other Dev's. Out of fustration towards other Dev members for doing them wrong or what not, they leak out info on irc, im, other mb's, and even on stray sites that any simple google search can bring up easily. Note, Im not going to post any of that here due to the fact that its probably considered bannable without consent of the Dev who typed it up, but still a good read from the site itself. I would like to see the updated version tho, think the last entry I read from that stray site was dated september 2004.

I get the feeling that this is the extent of the "typed up documentation" you suspect exists.

It seems this thread is going to be an infinite ping pong match between me and you on this matter. If your saying that documentation doest exist then thats fine. Either, its not suppose to be released, or you really dont know what im talking about. What Im referring to is around 20 pages if printed out with ascii tables, code, and some theory based charts of the protocol layer... but I guess that doesnt exist. Anyways, feel free to lock this thread.. nothing good is coming out of it. I'll go check myself into a crazy ward now.

end of rant.