Task nonrepeatable

[Rocker8956]

Sorry if this is in the wikki or posted somewhere. I looked and did not see anything but I could have missed it.

Is there a way to make a task nonrepeatable?

Also, is there a way to make a NPC say something when a task is completed?

[KLS]

Task shouldn't be available if it's done...

There's a couple ways to make npc respond after task was complete. The most obvious is to just have the npc handle the reward like any other quest turnin and have them quest::say in that then complete the step via perl.

A player event for task stage completion was just added too. Mostly I found having to dole out rewards when all I wanted was a simple additional effect to be a tad cumbersome. I'd rather have the system do the rewards for me if practical.

ex:

#player.pl
sub EVENT_TASK_STAGE_COMPLETE
{
	if($task_id == 1 && $activity_id == 1)
	{
		my $somenpc = $entity_list->GetMobByNpcTypeID(123456);
		if($somenpc){
			$somenpc->Say("Great work! You sure showed that task who's boss.");		
		}
		$somenpc = undef;
	}
}

[joligario]

You can look at my tasks on PEQ. I knew that it would be a problem to have the NPC say something at the end of the task, so rather than having the task system update the task, have the NPC update the task. Then he can also say something before the final step is updated.

http://www.projecteq.net/phpBB2/viewtopic.php?t=5697

[joligario]

To make a task non-repeatable, you could have the NPC check the completed tasks table for that specific ID and not issue the task if it is present.

[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.