This thread should be closed,there are many subjects not related to topic theme.

Note: I posted this on another thread,my bad =p

It won't continue for much longer. The argument is pretty much out of steam.

I am making a special Graalian Award for this thread:
'Best, and most equal and stubborn fight thread Award'

*Hands Kai and PS trophies*

Hmm, I should be proud, I don't recall having my scripting insulted, just my lack of promise in narrowing bugs down before I assume it's a problem with graal.

Reviving an old thread just to post more spam is a good way to win points. :)

(And, I'd be interested as to just what about PS and Kai you consider 'equal.')

:rolleyes: oh well, it was a really nice arguement.


The arguement.

You wouldn't have happened to actually read the thread, would you? 'Cause if so, you'd note the obvious difference between the arguments used in this thread...

Yes, I did. And I thought both arguements were very good. :) And if you think different, that is fine, but you can't assume your opinion will be the same as everyone elses.

Not really, I would have considered it a one way arguement, PS's
explanations didn't even phase kai, so he got frustrated and started being aggressive towards kai, which never works, and kai brought him to the point where he just shut his mouth, so this goes to my point, I've never seen kai loose an arguement

I know it's a bit late, but I believe Projectshifter had a Hat system on Rudora that forced people to reconnect to the server because they couldn't turn it off properly, and it created big gray blocks on the screen.

Hm? It's not really matter of opinion; look at the arguments for yourself. Kaimetsu used logic, Projectshifter used emotion (instead of thought) and poorly strung together attacks on Kaimetsu.

x.x
 

Guys quityour*****in he gave a script if you don't like it don't use it...don't waste peoples time having to scroll thru a hundred posts that all say "Your ineffecient!" "You suxor my c0x0r" and just read it...don't like it? don't reply unless your going to say
"Its good but if your replaced <insert line here> with <inseret better thing here> it'll possibly speed it up" don't just post and go "Thats a stupid script!"

I R = bad speller so just kinda close your eyes and pretend to be in a happy place in a mis-spell. >_<

Re: x.x
 

You're kinda missing the point in the debate.

Re: x.x
 

Don't like it? Don't read it.

Re: Re: x.x
 

lol *gets bad rating*

Re: Re: Re: x.x
 

:eek: MEANIE! *Gives bad rating in exchange*

I love mis-information as always =D
I made a hat-system (almost a year ago!) and it worked fine. I didn't add mouse features, it scrolled with 'u' and 'y' because I never had time to finish it. I did Spark a favor back then. THEN people started editing it, and that's when it no longer worked.

And I was on vacation for a week. I refuse to contribute more to this stupid "arguement".
---Shifter

I read through alot of the yelling and what not and the ocassional spouting of ideas and I wanted to get to an idea solution for the first problem in this thread.
The having a timeout loop in the control npc.

I think you should not do it for the simple fact that the control npc has alot of other processes involved with it and you might run into complications (doubled variables/strings, one small typo that renders all actions in the npc to cease and you cant seem to find it but you see it about 5 hours later after you have had to take 3 asprin and beat your head on the wall several times and it was a frigin extra ")" that you put in while trying to do 50 things with one string, ect...) later on when you have so many things being used at once on one npc. Although I see no problem with doing it as far as lagging or cpu time is concerned, loading down one npc would pretty much the same as giving 1/3 the script to 3 other npcs that might even cause more of a problem.
[edit] condsidering its all part of the same process

I was working on a Control2 NPC that had a timeout loop in it but other npcs could access this npc and give it information and depending on the information the Control2 NPC could do tasks and give information back. Example- instead of having a timeout loop in 4 npcs that I realy need it in but only at certain times and a high timeout time I would have the 4 npcs access the control2 npc give it the time they need before another proccessing was needed say 30 seconds then the control2 npc would log those npcs names/id and would have seperate countdowns as a this.var or just one variable as an array and would call those npcs when 30 seconds was up for them to repeat their action.

I know that sounds like a pain but say it wasnt just 4 of those npcs maybe it was 100 and they had to be accessed at different times for different reasons some player initiated and some casualy then that would reduce server lag tremendiously than having 100 npcs running timeout loops(thats a little nutz btw).

So what did Stefan say?

*Stefan: hmmm timeouts in the control-npc are not bad,
*Stefan: only if combine them with some with (allplayers[]) loops

So, ProjectShifter, I guess this is the benefit that comes from your amazing serverside scripting experience? :)

*Chalks yet another for Kai.*