[Marttt]

So my question is related to Tanks passing control on L4D/L4D2.

I didn't found how to detect that the Tank has been passed to another client.

Any events hooked on "tank_spawn" will execute again (reset).

Does anybody have some best practices on how to detect that?

I mean, is possible to hook the "tank_frustrated" and create a global variable that holds the last human tank. But that is like a workaround. When there are 2+ tanks spawned, this logic may fail(?)

[Marttt]

By now the only solution seems to hook the "tank_frustrated" event and then set a bool to "true", and reset it to false on "tank_spawn" that runs next, is not 100% but may work on 99% of times

[Silvers]

Left4DHooks has:

PHP Code:

// Not invoked if tank is bot
forward void L4D_OnReplaceTank(int tank, int newtank);

// Is used for displaying the "X gets Tank" window and transferring Tank control
forward Action L4D_OnTryOfferingTankBot(int tank_index, bool &enterStasis); 


[Marttt]

Thanks Silvers!

Gonna try to use that, probably I will need to use it.

Btw will be my first time creating a plugin with an optional #include (kinda noob on it yet).
Gonna check some examples.

I found that many tanks plugins would fail on versus when tank gets frustrated, or even when the player left the match or change team while tank, because "tank_spawn" event runs again, probably would be an issue with most of the plugins that use this event to do something.

[Marttt]

Well did some tests and doesn't seem to fire when Tank becomes a bot

I know that has this note:
// Not invoked if tank is bot

But actually there is a scenario where the tank = client, and the new tank is the bot.

L4D_OnReplaceTank(int tank, int newtank);

Anyway maybe through "tank_index" parameter I could check it, but don't know how to get it.

[Silvers]

tank_index is just the client index passed as a variable when L4D_OnTryOfferingTankBot is triggered. Same way any other forward works.

When frustrated or a player takes over a tank, the last tank is kicked and a new one is created for the player to take over, theres a delay between the actions happening. You would have to play around with it, debug print to figure out what's going on.