[Development] Complete COServer

Page 2 of 3 1 2 3
03/13/2011 14:11 SimplyPerfection#16
As I said earlier Lateralus, this isn't just a dev thread but an thread where we'll discuss and share ideas, I already got some very good ones out of this thread. And, leave rest up to the moderators, I believe they can handle it.

Thanks
03/13/2011 14:47 Lateralus#17
Quote:
Originally Posted by SimplyPerfection View Post
As I said earlier Lateralus, this isn't just a dev thread but an thread where we'll discuss and share ideas, I already got some very good ones out of this thread. And, leave rest up to the moderators, I believe they can handle it.

Thanks
This seems more like an advertisement for your own server to reach a larger audience, as you should have suggestions on your own forum so that your community can contribute rather than a community to whom giving suggestions doesn't benefit the majority unless they are willing to join your server (which then would cause them to join your forum to make suggestions). You should have at least made this a broader thread, like "Good ideas for a private server?", not a server-specific development thread.

Although I do see you claim to have TQ's official algorithm for VPs... May I direct you to this thread? [Only registered and activated users can see links. Click Here To Register...] None of those algorithms are right, and the official one seems to be fairly complicated as far as how it is split up after level 40 from the values I've gotten up to level 63.
03/13/2011 15:03 SimplyPerfection#18
I'll PM you this evening, on my phone at the moment.
03/13/2011 21:34 Arco.#19
Any proof you're using a custom source?
How do we know you're not just posting all these updates, but using a ready-made source?
03/13/2011 22:00 CØĐ£Ř||Mã©hÍñє#20
no itsnt a joke i saw it already
03/13/2011 23:19 SimplyPerfection#21
Quote:
Originally Posted by Yup Arco View Post
Any proof you're using a custom source?
How do we know you're not just posting all these updates, but using a ready-made source?
It's a custom source. I showed parts of it to someone that was interested in the project.
03/14/2011 11:12 Korvacs#22
Development threads are allowed, this section is for all private server discussion, as such both public, and private developments are allowed to be posted here.

Cleaned somewhat.
03/14/2011 23:00 SimplyPerfection#23
Anyone got the Quiz layout for the latest patch? I only seem to find old ones on the forum, and not being able to log from TQ CO.

I'm able to spawn the Quiz window, but not to print out the questions, so the packet for the question window would be real helpful if anyone got it.

Thanks
03/15/2011 01:41 Arco.#24
[Only registered and activated users can see links. Click Here To Register...]
03/16/2011 07:12 SimplyPerfection#25
Quote:
Originally Posted by Yup Arco View Post
[Only registered and activated users can see links. Click Here To Register...]
Why do you define the question and answer as smallbyte? It's obviously strings
03/16/2011 07:16 pro4never#26
Quote:
Originally Posted by SimplyPerfection View Post
Why do you define the question and answer as smallbyte? It's obviously strings
It's one of the ways you can use pointers to write strings to the packets.

I forget what source this is from but yah, as someone mentioned it's wrong.


Example of sbyte from hybrids new source.

Code:
public unsafe struct AuthResponsePacket
    {
        public ushort Size;
        public ushort Type;
        public uint Key2;
        public uint Key1;
        private fixed sbyte szIPAddress[16];
        public uint Port;

        public unsafe string IPAddress
        {
            get { fixed (sbyte* bp = szIPAddress) { return new string(bp); } }
            set
            {
                string ip = value;
                fixed (sbyte* bp = szIPAddress)
                {
                    for (int i = 0; i < ip.Length; i++)
                        bp[i] = (sbyte)ip[i];
                }
            }
        }

        public static AuthResponsePacket Create()
        {
            AuthResponsePacket retn = new AuthResponsePacket();
            retn.Size = 0x20;
            retn.Type = 0x41F;
            return retn;
        }
    }
It IS a string it's just a way of storing a string in such a way that it can be read/written simply using pointers.


It's basically saying in that packet that you are allocating 16 bytes for the string packet in the structure. That way it essentially holds the same structure in memory as it does in a packet and can be easily converted without using messy writers like many public sources use.

Ps: I'm sure you know it but 16 bytes is the length for any non specified string length that tq uses.
03/16/2011 16:53 -impulse-#27
Quote:
Originally Posted by SimplyPerfection View Post
Why do you define the question and answer as smallbyte? It's obviously strings
Since when does the 's' before a type mean small? The last time I checked it was called signed which gives the type different min/max values(int(signed) min: -2147483648, max: 2147483647 and uint(un signed) min: 0, max: 4294967295...

Did I fall behind the news or something?
03/16/2011 18:40 SimplyPerfection#28
Sorry sorry sorry. Guess I didn't spend much time looking at the code itself since ImmuneOne already pointed out it's wrong, so didn't spend too much attention on it. Thought he was using the signed bytes to print out the numbers of each question (which I'm not completely sure if Quiz does either).

Anyhow, can anyone confirm that's the correct layout?
03/16/2011 20:30 andyd123#29
Quote:
Originally Posted by SimplyPerfection View Post
Sorry sorry sorry. Guess I didn't spend much time looking at the code itself since ImmuneOne already pointed out it's wrong, so didn't spend too much attention on it. Thought he was using the signed bytes to print out the numbers of each question (which I'm not completely sure if Quiz does either).

Anyhow, can anyone confirm that's the correct layout?
Well two things -- you openly proved that you have little experience in coding. Even if you "didn't hardly look at it," you still saw sbyte and thought it meant "small byte".
Not sitting here trying to flame you, but seriously bro. You can't make any excuse to cover for the fact that you did indeed say that.

Secondly, since lost replied and said it isn't the right layout....I'm guessing it isn't the right layout.
03/17/2011 00:45 Syst3m_W1z4rd#30
Quote:
Originally Posted by -impulse- View Post
Since when does the 's' before a type mean small? The last time I checked it was called signed which gives the type different min/max values(int(signed) min: -2147483648, max: 2147483647 and uint(un signed) min: 0, max: 4294967295...

Did I fall behind the news or something?
So byte = unsigned and sbyte = signed?
That's how I understand it:
{ sbyte, short, int, long }
{ byte ushort, uint, ulong }
Page 2 of 3 1 2 3