Last question for 2 weeks I swear! (Unless it's about a source)

Alright so I have now decided to stick with C#. After talking with Fang, he has given me some slight inspiration to buckle down and learn Conquer Online Server Development. Can someone PM me a list of the systems that you need to add in a project in order, in order to achieve a stable working Conquer Online Server? I know that Networking is first, that's all I know though. Also if anyone could PM me some tips along with that (that's not reading through documentation) that'd be great too!

Lastly, if you can code a conquer online private server I would be real grateful if you could add me on MSN so that I may ask you questions when need be. (They are relatively smart questions such as: "Explain to me what a packet does and what it's use is", "What is the advantage of using pointers versus not", etc. stuff like that)

I lied. Lastly, if someone is searching for an apprentice, I still need a mentor that would teach me how to put systems together and whatnot. If you think it's a waste of your time to offer me an apprentice position then this is what I have to say: I will respect your time, but you have to respect my ability to learn at a slightly slower rate than most have learned programming. I will work hard and as swiftly as need be, but you have to give it just as much as I do.

So yeah, any comments about any of that just PM or add me on MSN: [Only registered and activated users can see links. Click Here To Register...]

Learn the language well before attempting to code a server. Seriously. Work through the bullshit examples and practice exercises, and don't learn anything from any of the public sources before you do, or you'll adjust to the way everyone in this community codes. When you learn it, don't even think of how any of the concepts can be applied to a private server. Just work your way up with harder and harder exercises, and it will click eventually. You should also learn how to read through documentation, because it should be your primary source when using functions from unfamiliar libraries.

Programming takes practice. Lots and lots of it.

Didnt we already go over this in anouther thread of yours?

Quote:

Originally Posted by Korvacs Didnt we already go over this in anouther thread of yours?

I'm pretty confident that he already made a thread similar to this one, in where he got his answers, I just can't find it in the thousands of thread that he has made :(.

[Only registered and activated users can see links. Click Here To Register...]

Thats the thread i was thinking of.

Remember there is only 2 things that makes a source to be bind with Conquer.

The encryptions and the packets.

In reality it could be used for any games, even custom games.

@Lateralus: Alright, I guess a break from struggling with understand conquer server source would be nice so I will take that advice.

@IAmHawtness: I did make a thread of where I asked what you need to do to basically create a base but I asked for a more specific answer more down to like what systems are first ex: Networking, Auth, World, Mobs, etc.

@Korvacs: Same to Hawtness

@BaussHacker: So once I understand encryption and packets I could *basically* and I use that word loosely, make a server source for a custom game? What would the consist of, changing the packets to something you want for whatever you want that packet to control? Idk how packets work so excuse me if I'm not using packets in the correct context.

Quote:

Originally Posted by xBlackPlagu3x Idk how packets work so excuse me if I'm not using packets in the correct context.

If you don't even know what "packets" are, you're a loooooong way from creating your own private server from scratch. Seriously, it's not worth it, you have no idea how far you are away from being able to create your own private server.

Quote:

Originally Posted by IAmHawtness If you don't even know what "packets" are, you're a loooooong way from creating your own private server from scratch. Seriously, it's not worth it, you have no idea how far you are away from being able to create your own private server.

Yeah I know and it really really sucks that there are some concepts I'm having a hard time grasping and I'm trying so hard to understand them but it's just coming at me so slow! I'm only 16 so I have some years left, but it seriously would be nice if I could grasp the concept. And I know what packets are, just not how they work (I should've clarified)

Correct me if I'm wrong so that I can get this wrong idea out of my head but arent packets just a byte array of data that you send to the client or whatever it is you are sending data to?

Quote:

Originally Posted by xBlackPlagu3x @Lateralus: Alright, I guess a break from struggling with understand conquer server source would be nice so I will take that advice. @IAmHawtness: I did make a thread of where I asked what you need to do to basically create a base but I asked for a more specific answer more down to like what systems are first ex: Networking, Auth, World, Mobs, etc. @Korvacs: Same to Hawtness @BaussHacker: So once I understand encryption and packets I could *basically* and I use that word loosely, make a server source for a custom game? What would the consist of, changing the packets to something you want for whatever you want that packet to control? Idk how packets work so excuse me if I'm not using packets in the correct context.

Oh, see thats not what you actually said. If you have literally no idea how anything that goes into a server source works, then you need to go and study existing sources and forget the notion of making your own for at least 3 - 6 months.

Quote:

Originally Posted by Korvacs Oh, see thats not what you actually said. If you have literally no idea how anything that goes into a server source works, then you need to go and study existing sources and forget the notion of making your own for at least 3 - 6 months.

Sorry, screwing up with my grammar today. Yes I made a thread asking what systems you code into a server first, but in THIS thread I wanted more specific answers like Networking(Sockets, etc), Auth, World and so on. And yes, I imagine you are right, I do need to forget the notion it's just that I can't. It's not that I don't know what it does, it's that I don't know how it does what it does. Does that make any sense? Someone once showed me some source for a server and they were showing me how dictionaries work and how they add mobs into the dictionary. Well I asked them "How does it add them, I know it counts them all but how does it count them, how does it add it to the dictionary? How is add.ljsdljl<Dicitonarysdlsjfjslaj> (<-- that was because I can't remember the code) supposed to add it to the dictionary? And they said they don't know, why can't I just learn to code how they did and just understand. My questions get down to the rawness of basically how it knows to do what at compile time, and that's what I don't understand. I know what it does pre-compiling (pre-compiling being before you debug your project and it makes the .exe) Does that make any sense? I'm sorry I can't explain things and I'm sorry ask so many questions and most of them are because of my rage towards not being able to understand how something does what it does. The reason I can do 2 + 2 is because you take two of something and add two more of it and you can count the total. That's raw data. The reason I don't know what packets are is because of *(lsljf) + (ptr)*(&_lsdlle)[buffer]. Obviously that's not exact, but that's my representation.

Damn you got a lot to learn. Start with hello world.

Quote:

Originally Posted by BaussHacker Damn you got a lot to learn. Start with hello world.

Can we be serious for once? I know I have a lot to learn, but Hello World?
Or are you saying start from the beginning?

Quote:

Originally Posted by xBlackPlagu3x Can we be serious for once? I know I have a lot to learn, but Hello World? Or are you saying start from the beginning?

A CO server can be coded in a billion different ways, all it really takes is just establishing a connection with the client and then responding to the client with the correct packets. It's as simple as that. The implementation, however, is where it gets tricky.

I mean, do you even know how to re-direct the client to your server? You really, REALLY need to understand the basics of how programs work before trying to make a private server.

Quote:

Originally Posted by IAmHawtness A CO server can be coded in a billion different ways, all it really takes is just establishing a connection with the client and then responding to the client with the correct packets. It's as simple as that. The implementation, however, is where it gets tricky. I mean, do you even know how to re-direct the client to your server? You really, REALLY need to understand the basics of how programs work before trying to make a private server.

The largest thing I've done with a client and server is making a message system and client that "talk" to each other. But that was with the help of documentation. So I guess I understand a little, just not enough to make it count. But now that I mention it, I think I just had one of those "Aha!" moments and I think a little daylight just broke through for me with C#.