Quote from: S.L.C on Dec 11, 2014, 04:20 PMWhen the player disconnects:Code Selectmy_array[index] = null;
When the player connects:Code Selectmy_array[index] = my_class();
Now you signal that you wan't to use that slot/index/element of the array again. Keeping your array size constant and reducing overhead or resizing the array.
I was talking about the "players" table not about an array. about your examples everybody must know it lol (if is using an array), I have that in my functions but the question is, what will happen with the player when this is kicked? if you are saying that the players table must be removed from kickplr?
then I'll be only cleaning the data when players leaves but not when are kicked? I guess it you are confused or forgetting something
Quote from: S.L.C on Dec 11, 2014, 04:20 PMWhat do you think will be the output of that program? Do you think it will be 33? WRONG! the output will be 01, because you had no idea in the function body that you overloaded the global one. You think you know but it's easy to make mistakes. Not only that you have a more descriptive code but you're also protecting you're self from such mistakes.
I know it
Quote from: S.L.C on Dec 11, 2014, 04:20 PMQuote from: Fjose on Dec 11, 2014, 04:03 PMof where was taken out the "instance"?
Even though you use OOP you still don't have the slightest idea of what an instance is. I might write a short guide about classes and OOP some day but you really need to document a little about the concept.
just explain me now '-'
my skills are limited, what I learned, was reading the scripts created by others lol