Quote:
|
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.