[pokemonmaster]

OK, I'm sick of this, it made me confused.
I read in some codes and tutorials (especially Exolent's tutorial about enums):

// Top
#define WhatEver 49162

public anything(id)
{
    set_task(0.1, "fw_fw", id + WhatEver)
}

public fw_fw(bla)
{
    id = bla - WhatEver
    // Code ...
}

Why do they sum the index of the player (id) with the define (WhatEver) if they, eventually, will get the same player id, and they never re-use the define.

It's just confusing!!!!

[DjOptimuS]

PHP Code:

set_task(0.1, "fw_fw", id) 


This is enough, then you use

public function(id)

where id = playerid from 1 to 32

[t3hNox]

The id (3rd param.) in set_task() has to be unique, so you cannot have (actually can have, but using player IDs (1-32) in set_tasks() may turn out to be a bad idea) two or more simultaneous tasks with the same id.

Defines are usually used in cases when a plugin has several set_task() functions which are related to players (but not only). When set_task() executes a function it is possible to get player's id.

[pokemonmaster]

Originally Posted by t3hNox Defines are usually used in cases when a plugin has several set_task() functions which are related to players (but not only). When set_task() executes a function it is possible to get player's id.

If you can provide some examples to that, it'd be nice.

[DjOptimuS]

i use that all the time and i remove the task when player disconnected if the task is with B flag and i never had any problems, you can set a random constant + playerid if you don't like

new const task = 32784;

and set task with the id + task

[hornet]

EDIT: This example I've used is misleading and is likely to fail. See post #9.

A player might have several tasks running which require their player index when ready. For example, a weapon pickup delay for both primary and secondary weapons, therefore you need 2 task identifiers, incase a player picks up a secondary weapon before his delay has expired for his primary weapon ( or vice versa ):

#define TASK_PRIMARY      1001
#define TASK_SECONDARY    1002

You add the identifier to their player index:

set_task( 5.0, "GetPrimary", id + TASK_PRIMARY );
set_task( 5.0, "GetSecondary", id + TASK_SECONDARY );

And then deduct the identifier to retain the player index once again:

public GetPrimary( id )
{
    id -= TASK_PRIMARY;
}

public GetSecondary( id )
{
    id -= TASK_SECONDARY;
}

Hope that helps.

[hleV]

Basically if you want to remove (or change) a task, you need to provide its ID. It gets problematic when you have several tasks with same ID and want to remove/change a certain task.

[pokemonmaster]

Ahhhhh, now I understood it.

Thanks all!

[Emp`]

Originally Posted by hornet #define TASK_PRIMARY      1001 #define TASK_SECONDARY    1002

You should space them with the max players available (ie. 1001, 1033, 1065, etc.)

Usually you will see authors use an enum to do this:

enum += 32
{
   TASK_ONE = 1001,
   TASK_TWO,
   TASK_THREE,
   //etc.
}

If you used your examples, primary task for id 2 (1001+2) would have the same task id as secondary task for id 1 (1002+1). This would only be problematic if you need to check, change, or remove tasks though.

[hornet]

Originally Posted by Emp` You should space them with the max players available (ie. 1001, 1033, 1065, etc.) Usually you will see authors use an enum to do this: enum += 32 { TASK_ONE = 1001, TASK_TWO, TASK_THREE, //etc. } If you used your examples, primary task for id 2 (1001+2) would have the same task id as secondary task for id 1 (1002+1). This would only be problematic if you need to check, change, or remove tasks though.

Oh, I never actually thought of that. Somehow I survived without functional errors in my concept so far.
Thanks