getAreaPlayers()

[coreys]

Since there's a getAreaNpcs() function, why is there not a getAreaPlayers()? It would be very useful to have this, and if there's one for NPC's, why not players? Doesn't seem like it'd be hard to implement, either.

[Cubical]

I wouldn't mind seeing this, would make things a bit easier.

[DustyPorViva]

This would eliminate a lot of unneeded checks and calculations and loops that are used for things like hit detection, when you only need to for players in a specific block, and not worry about ALL of the players in the level.

[coreys]

On a related note; something like triggerarea() to trigger every player/npc in a specified area would be just as, if not more, useful. This has been requested more than once before, and seems like such an obvious addition.

[Admins]

The problem is that accessing players[] is much faster than level.players[] and you would probably expect findareaplayers() to work regardless if your current position. It could be possible to add a findareaplayers() which only accesses the players around you.

[Cubical]

Originally Posted by Stefan

The problem is that accessing players[] is much faster than level.players[] and you would probably expect findareaplayers() to work regardless if your current position. It could be possible to add a findareaplayers() which only accesses the players around you.

Do you mean that it would only be able to get players from your current level and surrounding levels? If so that sounds fine to me.

[adam]

I really don't understand Stefan's post at all.

[coreys]

Originally Posted by Stefan

The problem is that accessing players[] is much faster than level.players[] and you would probably expect findareaplayers() to work regardless if your current position. It could be possible to add a findareaplayers() which only accesses the players around you.

Well that's pretty much what I (we?) want.

[DustyPorViva]

Originally Posted by Cubical

Do you mean that it would only be able to get players from your current level and surrounding levels? If so that sounds fine to me.

Which is what getnearestplayers() does...

[fowlplay4]

Originally Posted by DustyPorViva

Which is what getnearestplayers() does...

It'd be nice if an optional radius parameter was added so it wouldn't require a scripted distance check, getnearestnpcs would be cool too.

[Deas_Voice]

Originally Posted by DustyPorViva

Which is what getnearestplayers() does...

what's the difference between findnearestplayers() and getnearestplayers() ?

[coreys]

Of course we can just use getNearestPlayers() and check if the player is within a box but it's always faster for that to be done in the engine, and things like hit detection can use any speed boost they can get.

[DustyPorViva]

Originally Posted by Deas_Voice

what's the difference between findnearestplayers() and getnearestplayers() ?

Do both of those functions exist? I guess so! Anyways, wiki says:
getnearestplayers(float, float) Deprecated. Use findnearestplayers() instead.

I honestly don't know. getnearestplayers may return the indexes of players that was compatible with the old GS1 methods of players[x].

Of course, they could be exactly the same thing but just two function names.

[DrakilorP2P]

Originally Posted by Deas_Voice

what's the difference between findnearestplayers() and getnearestplayers() ?

One returns indeces the other returns objects. I forget which.

[cbk1994]

I'd love to see a radius parameter added to findNearestPlayers

Originally Posted by DrakilorP2P

One returns indeces the other returns objects. I forget which.

find returns the object, getNearestPlayers shouldn't be used anymore.