[Snippet] PlayerUtils

[Troll-Brain]

Originally Posted by Magtheridon96

After realizing that calling a struct Player makes it impossible for me to call the function Player even inside the library itself, I changed my system to use:
function PlayerEx takes integer i returns player
I gave it TESH Highlighting too <:

It's true than you won't be allowed to use the native function Player anymore in "bottom" libraries, and scopes.
But if you really want to spell your struct Player, you can still use a second library used by your player library, where a global player array is filled with the 16 players.
And then, inside your player library you use this global variable.

Or if jasshelper memorize this struct name in the whole vJass scripts, you still can use a custom common.j or blizzard.j for this global array.

And if you use the Player native when there is now a great way to use a global instead, it will even give you a nice senseless error on compilation to prevent this heresy to happen.

[Bribe]

I have seen PlayerManager by Nestharus but I will accept this as a simpler alternative.

[LuizBills]

These locals need not be nulled?

Jass:

private function IndexPlayers takes nothing returns nothing
  local player  pl
  local code    c = function DetectLeavers
  //...
  set pl=null
  set c=null
endfunction

[PurgeandFire]

The reason we null locals is because of a bug where, upon destroying an object, the handle id will not be recycled unless all locals pointing to the object have been nulled. (or assigned to point to something else) However, since we are dealing with players and code variables which will never be destroyed, we don't really have to null them.

[LuizBills]

Oh thanks man =)

[Bribe]

Just null all handles. There are semi-confirmed reports of people who reduced lag in their game simply by nulling player handles.