Quote:
Originally Posted by hornet
Code:
#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:
Code:
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.