Task nonrepeatable

[Derision]

I did consider adding a 'nonrepeatable' field, as well as allowable class/race fields to the task table, but didn't as I figured it was already complicated enough to create tasks, and this could be handled by Perl if needed. If the consensus is that any of these fields should be added, I would be happy to add them.

[trevius]

I think as long as fields have defaults that work in 99% of all tasks and you only need to change them if you are doing something special, then making it more complex isn't really too bad.

[Rocker8956]

If you are up to putting a nonrepeatable field in I would be very grateful.
Currently I think the only way to keep a task from being repeated is to put it in a taskset then do something like this in the quest.

if(!quest::istaskcompleted(quest::lasttaskinset(1))) {
		# If the player has no tasks enabled for this task set, enable the first one
		if(quest::enabledtaskcount(1) == 0) {
			quest::say("You have not done any of my tasks before!");
			quest::enabletask(quest::firsttaskinset(1));
		}

Another method would be to check if the task is disabled but I did not see a perl quest command to do that.
Honestly I find writing tasks to be easier than quests if I use KLS taskmaster program.

[KLS]

There should definitely be a repeatable (default:false) field in there if you ask me. Most tasks aren't repeatable anyway. Asking people to keep track of that via quests kinda takes away from the ease via automation the system already has(same reasoning I added task_stage_complete event; tracking them via quests was too clumsy).

[joligario]

From what I can tell, most tasks are repeatable... Especially when it came to doing the crystals. All the lower level tasks I have found are repeatable also.

[cavedude]

Either way, I agree a nice easy column to determine if it's repeatable or not would be awesome.