[Starlight] SocketAsyncEventArgs Sockets 0.1 - BETA
@Update 2: http://www.mediafire.com/?of54d1n94g4557c
Started on Packetfinder, coded some packets and made an incomingheaders and outgoingheaders class + some minor edits.
__
Hello RaGEZONE!
I've had a little bit of free time the past months and made 300 bases for emulators in C#. I want to start a emulator once in my life and finish it, so I decided to relax and really look over every code 50x. I'm now working on the best sockets I could ever make before I'm going to start on something else. I want you to say what you think of these sockets (and maybe use them?). I want to do this same thing with my database handler too when I've finished it, but I don't have much time and no experience in MySQL in C#.
DL: Starlight.rar
Please comment on what you think about the sockets and tell me if you find any bugs?
(I know it's not much but I want to make everything 100% perfect before I start the next step)
Re: [Starlight] SocketAsyncEventArgs Sockets 0.1 - BETA
Thanks for the release Azaidi, good work.
Re: [Starlight] SocketAsyncEventArgs Sockets 0.1 - BETA
How Lasse said, good work. I like how you do your things. Step for step is better as one step with much bugs.
Thanks, JustTime.
Re: [Starlight] SocketAsyncEventArgs Sockets 0.1 - BETA
I'll not create a new thread this time, Starlight Emulator 0.2: Starlight 0.2.rar
What do you think about this base? I'm going to continue with R63A because I don't want to go into the R63B bullshit with shuffling headers etc.
Re: [Starlight] SocketAsyncEventArgs Sockets 0.1 - BETA
Why keep releasing? No one has used it.
Re: [Starlight] SocketAsyncEventArgs Sockets 0.1 - BETA
Hi,
I'd recommend you to put all handlers (Handler.SetIncomingHeader) to it's own classes (makes it easier to look through). And I'd recommend doing the same thing for packets (A new class per packet), it gives a more "smooth" overview. Rather than that, I think it's great :)
Re: [Starlight] SocketAsyncEventArgs Sockets 0.1 - BETA
Quote:
Originally Posted by
Quackster
Why keep releasing? No one has used it.
Still useful for those who are searching for this sort of thing and they come across this.
OT: Looking sweet
Re: [Starlight] SocketAsyncEventArgs Sockets 0.1 - BETA
Quote:
Originally Posted by
Quackster
Why keep releasing? No one has used it.
Because I'd like some good feedback on my coding and this might be useful for some people?
[Starlight] SocketAsyncEventArgs Sockets 0.1 - BETA
Quote:
Originally Posted by
Quackster
Why keep releasing? No one has used it.
Pretty awful for someone to say. Like your emu was finished. Sure Sulake forbid you but work under a Latino alias or something. They won't know the difference.
Re: [Starlight] SocketAsyncEventArgs Sockets 0.1 - BETA
Quote:
Originally Posted by
FullmetalPride
Pretty awful for someone to say. Like your emu was finished. Sure Sulake forbid you but work under a Latino alias or something. They won't know the difference.
If Sulake finds out (and sure, they will) he will have even more troubles.
Re: [Starlight] SocketAsyncEventArgs Sockets 0.1 - BETA
Quote:
Originally Posted by
Quackster
Why keep releasing? No one has used it.
You forget.. Not everyone has decided to go R63B.. It has alot of bugs unless you can fix them. So this 'could' help users.
~ Mikey
Re: [Starlight] SocketAsyncEventArgs Sockets 0.1 - BETA
Quote:
Originally Posted by
Mister. M
You forget.. Not everyone has decided to go R63B.. It has alot of bugs unless you can fix them. So this 'could' help users.
~ Mikey
Or you could just use a complete/near complete server instead. :laugh:
http://cdn.memegenerator.net/instanc...x/38401253.jpg
Re: [Starlight] SocketAsyncEventArgs Sockets 0.1 - BETA
Quote:
Originally Posted by
Quackster
People has lifes too, even people here @ RZ!! :o
Re: [Starlight] SocketAsyncEventArgs Sockets 0.1 - BETA
Quote:
Originally Posted by
Aquel
Hi,
I'd recommend you to put all handlers (Handler.SetIncomingHeader) to it's own classes (makes it easier to look through). And I'd recommend doing the same thing for packets (A new class per packet), it gives a more "smooth" overview. Rather than that, I think it's great :)
Thanks, I've done this now and cleaned up some code. This is the kind of feedback I want.
I will put all Incoming Headers in separate static functions in one class so people can easily find any incoming packet without having to go through 100+ files.
I will also put the outgoing packet structures in a separate static class without any work going on, just changing parameters -> servermessage so the code will look a lot cleaner and it will be very easy to change it to R63B if I'm going to do that.
Quote:
Originally Posted by
Quackster
What's up with discouraging other developers?
I'm not doing this for making my own hotel, I'm doing it for the coding experience, what you should do it for anyway. If you want to run a succesful hotel use Phoenix Cracked, because this will never beat it. But I'm still going to work on this untill it becomes usefull and code CMS'es on this.
Re: [Starlight] SocketAsyncEventArgs Sockets 0.1 - BETA
Good work, looking forward to see some more from you. :)