How do you put a server's source together?

[xBlackPlagu3x]

So there are tons of different classes. Classes for networking, classes for packets. A lot of classes there. I no longer have anyone to help me with coding other then a few good friends on MSN and InfamousNoone's tutorials. I can probably bust my *** and throw a server together but there's a problem.

Where do I start!?

It wouldn't be in program.cs, I'm almost sure of it. And if I'm wrong, that means I need more help than I thought, because that's where you load everything, right? So there's character.cs, cryptography.cs, etc. Where do I start? The more advice you could give me for putting together a 5017 - 5160 server, the more I will love you. Don't get me wrong, any advice is fantastic advice, but I'm not sure a 5400+ patch server has the same shizz as a 5017 or 5124 server.

Beggers can't be choosers, so go ahead and give me whatever you have as long as it's not flamed and coming out of your ***. Thanks!

[Korvacs]

Sockets and surrounding classes
Basic Client Object (Enough info to login)
Cryptography and surrounding classes
Basic PacketHandler (Consisting of basic login handling)

From that you should be able to login, after this you have a few paths you can take depending on what you would like to do first, i tend to do things in this order from here:

Movement
Items
Database
NPCs
Monsters

And then its just a case of adding in the various features to the game, i leave the database untill i actually need it, no sense is adding it if your not going to use it untill say Item/Equipment loading, unless your doing some form of open development server where people can login whenever in whichcase Database should be after the basic setup and before any additions are made.

Theres plenty of source code released in the pserver guide section, ive released 2/3 different server sources in there myself you from this list and those sources you should be able to figure out a decent development path.

[Captivate]

Werent you coding one from scratch?

[pro4never]

*cough*



*cough*

[xBlackPlagu3x]

Thank you Korvacs, and lol Pro4Never, I seriously never noticed that until now xD... or maybe I did and figured it was some joke... or maybe I looked at it once and didn't understand it. Well either way, thanks Pro4never.

And I actually just started coding my own server together. Basically all I have right now is the "beginning" of sockets. I'm still learning how to do socket programming which is a major pain in my ***. So far this is all I know how to do...

public event Action<AsyncWrapper> ClientConnect
public event Action<AsyncWrapper, byte[]> ClientReceive
public event Action<object> ClientDisconnect

private Socket _connection = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp)

As you can see that's not near enough to even start on my sockets. There would be more but I just can't seem to understand it!

[.Kinshi]

In the base source I released, it has a KinSocket.dll file I made.
It has sockets, encryption, and a bunch of useful things.
If you want the source for the dll let me know.

[BaussHacker]

Originally Posted by xBlackPlagu3x

Thank you Korvacs, and lol Pro4Never, I seriously never noticed that until now xD... or maybe I did and figured it was some joke... or maybe I looked at it once and didn't understand it. Well either way, thanks Pro4never.

And I actually just started coding my own server together. Basically all I have right now is the "beginning" of sockets. I'm still learning how to do socket programming which is a major pain in my ***. So far this is all I know how to do...


As you can see that's not near enough to even start on my sockets. There would be more but I just can't seem to understand it!

[_DreadNought_]

Sockets are not the first thing you should be learning to code. Methods, class's, objects, operators and ****.

[Korvacs]

Its not that hes new to coding, hes just new to server development.

[_DreadNought_]

Gotcha.