Spawning Character Items 5361

Page 1 of 2 1 2
02/09/2011 14:13 §hift#1
Problem solved, Thank you everybody
#request close
02/09/2011 15:05 pro4never#2
We've mentioned this a bunch of times. You have to send a new show gear packet which includes the uid for the item in each equipped slot. That controls what is displayed on the character.

Hint, it's a 1009.
02/09/2011 17:19 Spirited42#3
I gave you hints for the packet a week ago...
why aren't you using them?

Edit: Yikes... that's NewestCoServer. ><
That gave me the chills.
02/09/2011 19:45 QuickCo#4
Quote:
Originally Posted by Spirited View Post
I gave you hints for the packet a week ago...
why aren't you using them?

Edit: Yikes... that's NewestCoServer. ><
That gave me the chills.

You can't be 100% sure of that just from the screen shot and code snippet. Ever wonder maybe he just likes the packet builder? So maybe that's just something he took out of ncs.
02/09/2011 19:57 Spirited42#5
Quote:
Originally Posted by Yo J-Dread, Its Arco! View Post
You can't be 100% sure of that just from the screen shot and code snippet. Ever wonder maybe he just likes the packet builder? So maybe that's just something he took out of ncs.
I'm 100% sure because I saw him working on it and it gave me the chills.
02/09/2011 20:19 §hift#6
Quote:
Originally Posted by Spirited View Post
I gave you hints for the packet a week ago...
why aren't you using them?

Edit: Yikes... that's NewestCoServer. ><
That gave me the chills.
I deleted it by mistake :/
02/09/2011 20:31 QuickCo#7
Quote:
Originally Posted by Spirited View Post
I'm 100% sure because I saw him working on it and it gave me the chills.
As far as I've seen the socket system is the only shit part of it, and really, I switched it out with an entirely different socket system for a friend, and the server runs like a charm.
02/09/2011 20:39 Syst3m_W1z4rd#8
Socket System is not the biggest problem.

Character.cs, Threading, 1million tries/catches.

That's the problem.
02/09/2011 20:44 QuickCo#9
Quote:
Originally Posted by Syst3m_W1z4rd View Post
Socket System is not the biggest problem.

Character.cs, Threading, 1million tries/catches.

That's the problem.
You must be an idiot. Take out the threading, replace it with your own, and your good to go. And yes the socket system is the biggest problem cause it can't take many connections for 6+ hours or else, laaag. Character.cs, tell me whats wrong with that hmm? And Try/Catches, take them out and you're good to go. But knowing you, you'd take them out of the most important places they're needed.
02/09/2011 20:49 Syst3m_W1z4rd#10
If threading wasn't a problem, why replace it? o.o

For character.cs find Step().
02/09/2011 20:53 QuickCo#11
Quote:
Originally Posted by Syst3m_W1z4rd View Post
If threading wasn't a problem, why replace it? o.o

For character.cs find Step().
Lol you know what, I want you to actually TELL me, whats wrong with threading. Cause I'm pretty sure you're goiing by on what you've been just told, not with any valid proof.
02/09/2011 20:56 Syst3m_W1z4rd#12
Not the actual threading, but the things threading.
But the main part of the bad things in it. is the tries and catches.

Example:
Code:
            try
            {
                foreach (Hashtable H in Kernel.Items.Values)
                {
                    ArrayList Deleted = new ArrayList();
                    try
                    {
                        foreach (DroppedItem I in H.Values)
                            if (DateTime.Now > I.DropTime.AddSeconds(60))
                                Deleted.Add(I);
                        foreach (DroppedItem I in Deleted)
                            I.Dissappear();
                    }
                    catch { }
                }
            }
            catch { }
Could just been used one catch, since no exception are caughed.
02/09/2011 20:57 QuickCo#13
Quote:
Originally Posted by Syst3m_W1z4rd View Post
Not the actual threading, but the things threading.
Alright, tell me, exactly what sthe problem then?
02/09/2011 20:58 Syst3m_W1z4rd#14
I edited my post :)
02/09/2011 21:02 QuickCo#15
Quote:
Originally Posted by Syst3m_W1z4rd View Post
I edited my post :)
You are retarded. Learn to code. Try/Catches catch exceptions no matter what. It just doesn't write them to the console when there's nothing in the catch. Look at it this way, if those try catches weren't there, and something went wrong with that void, server crashes, but since the server catches, then then nothing happens. Nothing happening is better than a server crashing.

Code:
try
            {
                foreach (Hashtable H in Kernel.Items.Values)
                {
                    ArrayList Deleted = new ArrayList();
                    try
                    {
                        foreach (DroppedItem I in H.Values)
                            if (DateTime.Now > I.DropTime.AddSeconds(60))
                                Deleted.Add(I);
                        foreach (DroppedItem I in Deleted)
                            I.Dissappear();
                    }
                    catch { }
                }
Telling the server to do a foreach, if it can't do it, then catch the error so the server won't crash.

Code:
try
                    {
                        foreach (DroppedItem I in H.Values)
                            if (DateTime.Now > I.DropTime.AddSeconds(60))
                                Deleted.Add(I);
                        foreach (DroppedItem I in Deleted)
                            I.Dissappear();
                    }
                    catch { }
Telling the server to try doing the actions listed, if it can't then it catches the error, instead of the server crashing.
Page 1 of 2 1 2