When it comes down to sources/resources, these are my opinions.
Gareth's 5187
Great documentation. Magnificent coding practice, great for people to learn from.
Roy's 5135
Finely coded, it does have a lot of stuff done, but it does require a lot of work to make it a fully functional source to run a server off of.
JP's CO2_CORE_DLL
If any of you have seen the project, this is self explanatory.
Jack's 4267(FO)
It's pretty old, yes, but it is definitely a great resource for people exploring aspects of a 1.0 server. Anyone can make a source and use that as a reference. Its what I did during Insomnia's 4267.
JP's 5017
Good coding structure, great resource for anyone needing things such as 5017 packet structures and their systems. As Jack's wiki doesn't have some correct 5017 structures.
These are for sure ones I believe should be stickied. If I think of anymore, I will post them.
JP's CO2_CORE_DLL I definitely agree with. Packet structures really should be on Jack's wiki, so if there are packets that aren't recorded, we need to get on that. I'm sure Jack wouldn't mind some more editors on the packet wiki.
When it comes down to sources/resources, these are my opinions.
Gareth's 5187
Great documentation. Magnificent coding practice, great for people to learn from.
Roy's 5135
Finely coded, it does have a lot of stuff done, but it does require a lot of work to make it a fully functional source to run a server off of.
JP's CO2_CORE_DLL
If any of you have seen the project, this is self explanatory.
Jack's 4267(FO)
It's pretty old, yes, but it is definitely a great resource for people exploring aspects of a 1.0 server. Anyone can make a source and use that as a reference. Its what I did during Insomnia's 4267.
JP's 5017
Good coding structure, great resource for anyone needing things such as 5017 packet structures and their systems. As Jack's wiki doesn't have some correct 5017 structures.
These are for sure ones I believe should be stickied. If I think of anymore, I will post them.
I would rather put my 5065 C++ source than COPS v6 (which is fine, but not that good). I think good sources should be stickied, for reference stuff like packet layout, it would be to update Korvacs' wiki.
I think JP has the right idea. Sources only used for packet structures should be used to improve Jack's wiki. Sources that can be used as a resource (such as his C++ source - I think that's a fantastic idea) should be stickied. I'll look into some sources when I get home this evening and make some suggestions.
I would rather put my 5065 C++ source than COPS v6 (which is fine, but not that good). I think good sources should be stickied, for reference stuff like packet layout, it would be to update Korvacs' wiki.
Perhaps but your COPS v6 has the nice algo's and packet structures :P
Jack is right, there really isn't much of a reason to bug the administrators. When I created my rule threads, I had to plan things carefully through the administrators, but adding and removing stickies is part of a moderator's responsibilities. Speaking of which, what's our new list looking like?
I think JP has the right idea. Sources only used for packet structures should be used to improve Jack's wiki.
I referenced the sources above not oONLY because of the packet structures, but for the protocols they follow, and the systems contained within them. Those are my reasons for those being good resources that I believe are worthy of a sticky. Especially since they range across different patches.
