[Dragonshadow]

Ok, so in the tank death event I need to check if any other clients ingame are currently a tank (to support multi-tank plugins).

I know I'll use a for loop to loop through all of the clients, but what do I check for? Details please lol.

[Dragonshadow]

Nevermind, I think this works:

PHP Code:

{
//  A Tank just died, check if any are still alive
//  LOOP TIEM LOL
    for (new i=1; i<=MaxClients; i++)
    {        
    //  Are the clients on infected?
        if (GetClientTeam(i) == 3)
        {
        //  Yup, now check the model
            new String:class[100];
            GetClientModel(i, class, sizeof(class));
        //  Is it the tank model?
            if (StrContains(class, "tank", false) != -1)
            {
            //  Yes, are they alive?
                if (IsPlayerAlive(i))
                {
                //  Yep, still alive
                    tanklive = 1;
                }
                else if (!IsPlayerAlive(i))
                {
                //  Nope, they're all dead
                    tanklive = 0;
                }
            }
        }
    }
} 


Though I'm pretty sure there is a less-hacky way of checking rather than checking the model.

[Flynn]

On Whatever Spawn event, take note of their HP, if it's the Tank style HP, store to an array saying it's the tank?

Heck, wouldn't use a for loop; limit it to known infected players (or just limit it to the spawn event of an infected - so much easier).

So in short;

//pseudo design code

On Spawn Of Infected
Check Tank Model
If Tank, Store to TankArray

On Death (of an infected?)
Check Array, If Tank, Remove (they died)

On Disconnect
Check Array, If Tank, Remove (they left)

No need for any resource hogging for loop.

[Flynn]

Or even simplier...

tank_spawn

Hook that event, store the ID and you're away. Done.

[Dragonshadow]

My plugin modifies tank hp, and there is a tank spawn event.

I'm doing this so that the plugin will still work when you have multiple tanks alive at once.

Besides this loop only fires when the tank dies, and its not resource hogging.

Storing the id of the player who got tank to start with wont work as tank control can switch...

[Dragonshadow]

I thought about something with an entity index but I'm not quite sure how to get/mess with those.

[Flynn]

Originally Posted by Dragonshadow Storing the id of the player who got tank to start with wont work as tank control can switch...

If you know what event causes the switch (or what condition), or you can intercept it, then you can update it.

[Dragonshadow]

I'm not sure but I don't think an event fires when the switch happens.

What I could do is get the entity index of the actual tank and store it, I just don't know how to get an ent index, nor do I know what I'd do after I store it. The idea is to support multiple tanks, storing one id to check isn't going to do anything, and I can't store multiples without hardcoding a limit.

[AtomicStryker]

Don't use tank_spawn. It fires way too often to be reliable - on a spawned bot tank, on the human who gets control, on whoever gets it if a tank gets frustrated...

Use player_spawn instead and check for the tank model. You could use Entprop m_zombieclass to check for being tank but i dont know which value a tank would have, you'd have to find that out yourself.

Also, i dont think a model check loop is too intensive.

[Dragonshadow]

Originally Posted by AtomicStryker Don't use tank_spawn. It fires way too often to be reliable - on a spawned bot tank, on the human who gets control, on whoever gets it if a tank gets frustrated...

Ahh ok

tank_death only fires when a tank actually dies right?