[deprale]

So I've got this piece of code

PHP Code:

public client_putinserver(id)
{
    set_task (2.0, "CheckName", id) // CHECK HIS NAME

    if( IsWarmupActive == true && !is_user_alive(id) )
        set_task (5.0, "task_respawn", id, _, _, "b") // The TASK that worries me.

}

public player_spawn(client) // Basic Ham_Spawn Hook.
{
    remove_task(client) // Will this remove the "Infinite" task that checks if a player is dead?
    
    if (IsMatchLive == true && is_user_alive(client)) {

    set_task(0.3, "show_money", client, _, _, "a", 28)

    }

    if ( IsWarmupActive == true ) {
        remove_task(client)
        fm_strip_user_weapons(client)
        cs_set_user_money(client, cs_get_user_money(client)-cs_get_user_money(client))
        cs_set_user_armor(client, 100 ,CsArmorType:1)
        give_item(client, "weapon_knife")
        cs_give_user_weapon(client, "weapon_deagle", CSW_DEAGLE, 60)

            if(cs_get_user_team(client) == CS_TEAM_CT)
                cs_give_user_weapon(client, "weapon_m4a1", CSW_M4A1, 120)

            if(cs_get_user_team(client) == CS_TEAM_T)
                cs_give_user_weapon(client, "weapon_ak47", CSW_AK47, 120)
    }

        
}

public task_respawn(id)
{
    if(cs_get_user_team(id) != CS_TEAM_SPECTATOR && cs_get_user_team(id) != CS_TEAM_UNASSIGNED) {
        ExecuteHamB(Ham_CS_RoundRespawn, id)
    }
} 


Do I have to assign an ID @ the task_respawn, to be actually able to remove it when that player actually spawns or do I just leave it be like that and it's gonna remove every single task that was assigned to the id?

Pretty much commented my question in the code, thanks in advance!

[Oops9499]

If you have more than 1 task in your plugin, you should use id's for each, otherwise when you do "remove_task(id)" it will remove all of your tasks.

PHP Code:

 remove_task(client) // Will this remove the "Infinite" task that checks if a player is dead? 


And yes, it will.

[eat1k]

remove_task(id) will remove all the existing tasks in the plugin where it was called.

[^SmileY]

What exactly you want to do with this plugin?
Since you do not need a task itself for spawn a player in some cases.
And in your case set_task is wrong

[DjSoftero]

Hook the event where player chooses team and set the task to not loop itself, then hook the event where player spawns and if player spawns before task is over, check if the task is valid and if necessary, remove it. And I don't know if it's a good practice, but instead, I use entities instead of tasks, as it is easier for me to handle everything in entities thinking function. But I only do that where I have to check certain things over and over again once every designated time interval.

[deprale]

Thanks, read that on amxx docs but wasn't sure on whether I understood it's meaning or not, cause I've seen people assigning ID's to their tasks always, but I've never bothered doing that.

[HamletEagle]

Originally Posted by deprale Thanks, read that on amxx docs but wasn't sure on whether I understood it's meaning or not, cause I've seen people assigning ID's to their tasks always, but I've never bothered doing that.

But you did:

PHP Code:

 set_task(0.3, "show_money", client, _, _, "a", 28) 


Here the task id is the player index(client). If you are talking about other people doing:
set_task(.., .., id + TASK_SOMETHING)

and then

id = id - TASK_SOMETHING

they are just doing that to create a unique id for their tasks(assuming you are using more than one task at the same time which need access to player's index). If you simply pass player id then all tasks will have the same index. So they add a random number to each task, for example one task may have index player id + 1234, the other one player id + 4234, creating unique task ids.