Detect if a player has predator.

[Kentoss]

How would I go about detecting this? AFAIK there's no bonus detection for GetPlayerStat, unless it's undocumented or something. So I'm wondering what other methods I could use to detect it?

[Hacktank]

There is no real way, but its possible to save a buffer of the previous health of every person and the number of flamer/pred/med/beserk boxes each second. And if the players health goes up and the predkit count goes down then you can assume that he has a pred. But this is very inaccurate.

IMO: Cant be done.

[Kentoss]

How do I check the number of pred boxes? I suppose I could just check if someone ran over a pred-box by checking player X and Y relative to the box X and Y, then just doing a scripted timer to coincide with the in-game timer.

[Hacktank]

You would have to read in all the bonus spawns in a map and disable them. Then simulate them by using apponidle and spawnobject(). Very complicated and there is no way for this to work every time (if the player has full health when the box is gotten for example).

[dnmr]

You would have to read in all the bonus spawns in a map and disable them. Then simulate them by using apponidle and spawnobject().

or loop through all objects and look for style 19

[JFK]

But this is very inaccurate.

IMO: Cant be done.

Everything can be done :p


I think you can get pretty close with apponidle. Loop through objects, see if there are players near. You could find out how long exactly a pred stays in game, so if it disappears sooner it might have been picked up. Hackthank's health trick might help, but a player might have had full health before picking up a pred. Or worse might have been damaged after he picked it up, but before you check his health again.

Of course the problem is there will always be doubtful times, when a player is close to a pred but the pred is about to dissapear in the following second. Or when mutiple players approach the pred in the same second (who picked it up?).

But I can think of three four ways to deal with that:
- Use a threaded function (nsc says they're stable in 1.51), check more often than once a second, decreases the chance for doubtful moments
- Be creative with the velocity info of players and try to predict (hellz yeah!)
- Better safe then pretty sure: just give everybody a (extra) pred who's in the doubt zone.
- Improve Hacktank's health trick by damaging a full health player if a pred is about to disappear and you might be able to keep track of the damage done to that player after he picked it up. (pff)

Lotsa work though...
If anyone makes it please call the project 'Shrödinger'...
Sorry for thinking out loud so much :p

[Kentoss]

I managed to accomplish what was discussed earlier. Every second it loops through all the objects with type 19, gets their X and Y, then loops through all the players, gets their X and Y, and checks if they're within 25 (what's the unit of measurement in Soldat?) pixels of the point.

I assumed that the time that it takes for Pred to wear off is whatever the default is (24 or 25, it's never accurate, though) and then counted it down manually for each player. This started giving me errors like something Out of Range and Access violation or something in the server, so it's limited in terms of FOR loops.

It's also not very accurate. Unless you get there RIGHT on the second it checks, it wont detect it. I don't see why there isn't a native method for checking these things, though. There's methods for all sorts of stuff about the player, including if the player has the flag, but not for bonuses. Would I be pushing it if I asked for a method to check this in a new update to the server?