Task System

From LSWiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 13:43, 21 May 2008 (edit)
Matts (Talk | contribs)
(→Fields - Bringing these together into a coherent manner.)
← Previous diff		 Revision as of 13:44, 21 May 2008 (edit)
Matts (Talk | contribs)
(→Fields)
Next diff →
Line 55: Line 55:
** '''Description''': This field holds the various bitmask flags for the descriptor. ** '''Description''': This field holds the various bitmask flags for the descriptor.
** '''Example''': Task_Flag_Active ** '''Example''': Task_Flag_Active
-** '''See''': [[Task System#Task Flags]]+** '''See''': [[Task System#Flags]]
* Task_Unique_Tag * Task_Unique_Tag
** '''Data type''': int ** '''Data type''': int

Revision as of 13:44, 21 May 2008

This page is for the developers to discuss, debate, and collaborate on the in-process dynamic task system. To start I'll outline the various sections that I think we will need to interact with and then list the expected interactions there of.

Contents

Incarnos

  • ability to store gathered tasks
  • ability to show and retrieve information on stored tasks via show?

Autonomon

  • This section will all likely be encompassed by an extension attachable to a living. Incarnoi could possibly inherit this functionality?
  • ability to know it's a task granter
  • ability to poll for available, and suitable, tasks
  • ability to respond to queries for available tasks
  • ability to describe available tasks to incarnoi
  • ability to evaluate progress of an incarnoi's relevant task
  • ability to complete and reward an incarnoi who completes a relevant task

Task Daemon

  • broker for task type definitions
  • stores all tasks? ever? (database interaction?) at minimum, provides ability to specify an incarnos/autonomon/unique-tag and find out what active tasks in the MUD it is involved with and what roles it has in them
    • should tasks that are defined at an individual level for say Losthaven be kept track of by a centralized daemon or a project specific daemon? Are there any physical limitations to holding a potentially large subset of tasks in a central place like that? interlacing it with the SQL would be interesting, I'd like to see the available tasks able to be thrown up on the webpage dynamically.

Task Descriptor

Fields

  • Task_Type_Code
    • Data type: int
    • Description: Identifies the task's type which defines default beavhior.
    • Defined by: /lib/task_types.h, /def/task_type/*
    • Example: Task_Type_Elimination
    • See: Task System#Task Types
  • Task_Name
    • Data type: string
    • Description: A basic short title for the task.
    • Example: "Aildrek's Rat Problem"
  • Task_Description
    • Data type: string
    • Description: A verbose description of what the task entails.
    • Example: "Aildrek's tavern, the Lost Lamb, has an ongoing rat problem that needs dealing with."
  • Task_Status
    • Data type: ?? (should this be a Task_Flag instead?)
    • Description: ...
    • Example: ...
  • Task_Roles
    • Data type: mapping
    • Description: An infostore field that will hold the varying roles unique to each task type.
    • Example: ([ "actor" : "/usr/erebus", "originator" : "/d/Almeria/Losthaven/npc/aildrek", "target" : "/d/Almeria/Losthaven/Sewers/mon/rat" ])
    • See: Task System#Task Types
  • Task_Objectives
    • Data type: ?? (does this need to be a seperate descriptor type possibly?)
    • Description: This would ideally describe the objective of the task in some meaningful way.
    • Example: ([ "/d/Almeria/Losthaven/Sewers/mon/rat" : 30 ])
  • Task_Info
    • Data type: variable
    • Description: A general purpose infostore for the descriptor.
  • Task_Flags
    • Data type: bitmask
    • Description: This field holds the various bitmask flags for the descriptor.
    • Example: Task_Flag_Active
    • See: Task System#Flags
  • Task_Unique_Tag
    • Data type: int
    • Description: A system generated unique numeral tag for this task.
    • Example: -1159877561

Flags

  • Task_Flag_Active

Functions

  • task_setup?
    • this will do basic setup for the descriptor and the Actor for the task type
    • for example with the elimination type above it could setup an At_Kill hook on the Actor that would check for its target against the killed, and if found flip the task to completed
  • task_validate
    • validates the task descriptor against the defined 'win' conditions, returns true or false
  • task_complete
    • completes the task, awarding any rewards and setting the task to completed

Task Types

  • Courier
    • Originator gives object/information to Actor who must deliver it to Objective.
    • Roles:
      • Originator
      • Actor (courier?)
      • Deliveree?
  • Knowledge
    • Originator dictates X pieces of Objective knowledge Actor must become familiar with/memorize.
      • Originator
      • Actor
  • Exploration
    • Originator dictates location Objective that Actor must become familiar with/memorize.
      • Originator
      • Actor
  • Elimination
    • Originator dictates Objective target that Actor must kill.
      • Originator
      • Actor
      • Target
  • Collection
    • Originator dictates X Objective items that Actor must gather.
  • Escort
    • Originator dictates Actor must escort Objective to destination.
      • Originator
      • Actor
      • Escorted

(suggestions by twi -- dunno if some of these are too uwieldy for the system being envisioned)

  • Heal
    • Originator dictates Objective target with an injury, malady, or curse that Actor must remedy.
  • Befriend
    • Originator dictates Objective target of whom Actor must acquire friendship (befriended status).
  • Recruit
    • Originator dictates Objective target of whom Actor must acquire "ownership" (command).
  • Arbitrate
    • Originator dictates two or more Objective targets for whom Actor must forge a friendship between (reciprocal befriended status)
  • Ally
    • Originator dictates two or more Objective targets for whom Actor must forge a command relation between.
  • Convert
    • Originator dictates Objective target that Actor must convince/force to change worships.
  • Protect
    • Originator dictates Objective target(s) that the Actor must protector from harm for some delimited amount of time [with the amount of injury that can be sustained and the proportion of the targets that must survive being variables].
  • Guard
    • Originator dictates Objective target item(s) that must be kept in a location for some delimited amount of time.
  • Alter
    • Originator dictates Objective target item(s) that must be altered in some way -- cursed, uncursed, enchanted, disenchanted, sharpened, repaired.
  • Destroy
    • Originator dictates Objective target item(s) that must be destroyed.
  • Dissention
    • Orginiator dictates Actor must cause strife between targets Objective. Polar opposite of Ally.

[removed suggestions by iggy; see discussion. --twi]

Retrieved from "http://wiki.lostsouls.org/Task_System"
Personal tools