Bug: The max loop limit can no longer be avoided serverside with a sleep.

[Devil_Lord2]

Originally Posted by ffcmike

Do you realise you have 2 conditions which are exactly the same?
If you were to remove the first line of player.account in this.tempStaff, it would still work.

Yes, I did that so if the first part didn't check, it wouldn't have to do the for loop, I assumed it would speed up what ever else it is doing if the first part was not correct.

The second part is only to add +1 to whatever the i is for the level, which I believe I could do with .index() but don't know how...

Originally Posted by ffcmike

player.level is an object rather than a string, the correct value to check is 'player.level.name'.

I have been told this many times, and I still don't quite understand it since the results are always the same. :[

Originally Posted by ffcmike

It's a bad practise to loop through non-changing arrays and use .size(); for every cycle, as the function will occur every time rather than once, this can generate a lot of overhead with very large arrays. The array size can be defined as a temporary variable beforehand, which can then be used in the loop condition.

for instance temp.num = something.size(); and stick that in the loop?
I shall do that!

Originally Posted by ffcmike

onTimeout(); occuring within function onTimeout(){} without any specification for it would run infinitely until cancelled by the engine/NPC-Server.

I'll ask you later, he says it does not work but I don't know what he had done. All I know is he had many loops inside of his and said it kept maxing out or something...

He is not on for me to ask. :[

-Correction-
He gave it to me to see, but I don't know if I have the right to expose it. :X
So I must ask.