- Gather a resource (may require a tool)
- Capture a monster
- Grow a plant
- Use X of a quest item on X monsters or locations (example there is or was a quest in WoW where you put medicine on diseased gazelles)
- Successfully execute a combo, this is kind of related to minigames like DDR and Guitar Hero where you match the pattern and timing
- Buy X (I don't really like this kind of quest, but it seems different from Find X or Build/Make X or Gather X)

variations on themes. but that's the whole idea here: there seem to be a small number of generic themes for all types of quest / missions in all types of games, apparently irrespective of genre.

gather resource:

get action, or someone_has(player, 50 wood) condition.

get actions can come from buying, killing and getting treasure, gathering resources, finding, pretty much any means. the fundamental goal is to place some quantity of something in someones possesion. which would lead to questgen code like: qty=dice(10), item=random_object(), for_who=npc[questor].

capture a monster:

depends on whether you have to deliver it to someone/somewhere or not.

if you do, this is a transport against their will mission (kidnap).

if you don't this is just an attack (to subdue) mission. And yes, the game supports attack to subdue, capture of subdued wild animals, taming of captured animals that are domesticable (dire wolf only at this point), killing captured animals, escape of captured animals, etc. I've tried to be thorough. ; )

- Grow a plant:

that would probably be a make action.

Use X of a quest item on X monsters or locations (example there is or was a quest in WoW where you put medicine on diseased gazelles):

Hmm, use of an item... that may be a new one...

by George! looks like we got us a winner! Give that man a cee-gar!

1. attack/destroy

2. defend

3. goto

4. transport

5. make/build

6. get

7. steal

8. find

9. influence

10. use

1. person/NPC/friendy unit or monster/badguy/hostile unit

2. item

3. information

4. landmark, location, building (a fixed position).

1. at_location(who/what, where)

2. someone_has(who, what, how many)

3. exists(person/place/thing)

4. is_known(what, bywho)

5. time_expired(deadline)

getting back to suggestions for the list:

Successfully execute a combo, this is kind of related to minigames like DDR and Guitar Hero where you match the pattern and timing:

could be another new one here. everyone on my block plays sports games, NBA2K13 and Madden for the most part. I see this type of optional mission goal in those types of games frequently. Tiger woods (another popular title in the 'hood) does some of that too, as i recall. stuff about executing a trick combo or some number of trick plays, etc.

Hmm, whats a good way to list that one, so it might apply to all game types...

can't think of anything better than "execute combo/trick maneuver" at the moment.

and so the list grows again:

1. attack/destroy

2. defend

3. goto

4. transport

5. make/build

6. get

7. steal

8. find

9. influence

10. use

11. successfully execute

1. person/NPC/friendy unit or monster/badguy/hostile unit

2. item

3. information

4. landmark, location, building (a fixed position).

5. combo/trick maneuver

1. at_location(who/what, where)

2. someone_has(who, what, how many)

3. exists(person/place/thing)

4. is_known(what, bywho)

5. time_expired(deadline)

Isn't 'get' fighting through enemies to acquire Object?
And isn't 'steal' sneaking past enemies to acquire Object?

you're already ahead of me, aren't you!

i hadn't read your post yet when i posted the AQUIRE(who, what,howmany) simplification.

yes, you are exactly right. and this is exactly what i want to do, determine the _fundamental_ most generic actions.

So it seems it would be better to add modifiers as well.

correct again. i hadn't gotten to that part yet. once you have your basic action (acquire, etc), and your basic parameters (who, what, howmany, etc). then come your modifiers. basically restrictions. time limit is the first, and can be applied to just about any quest. coming up with context to justify a time limit for some actions may be difficult or impossible in cases that simply don't make sense to have a time limit.

the second modifier would be things like bywhatmeans for the acquire() action.

i'd like to get to a point where you could generate a quest by picking an action from column A, parameters from column B, and zero or more modifiers from column C. throw out the cases that don't make sense, and whats left is a design for a generic questgen. possibly generic enough to use in different types of games by changing the parameters who=player or npc in an rpg, who = building or unit in a RTS, etc.

Wow! that list you made is Huge! I'm going to need a little time to read though them all and see whats covered already and whats not. definitely a VERY good start on the list of possible modifiers. Something tells me we'll see a number of new things on the list coming from your list, and probably a few insights and simplifications as well. A couple things like that caught my eye during a quick glance at the list. But i want to take the time to thoroughly review it to make sure i don't overlook any patterns, simplifications, etc.

Few more:

- Avoid doing X for the duration of Y

- Consume a specific consumable

Examples of "Avoid doing X for duration of Y"

- Defend the base: keep the base from being captured or destroyed for Y minutes.

- Escort quest: keep the npc from dying before they reach the end of their gauntlet

- Gauntlet: survive in extra-hard mode for Y minutes or until the end of a physical level.

- Timed test: accomplish a goal while avoiding running out of the Y minutes on your timer.

- Enforced avoidance: consume a potion or be the target of a spell that transforms you such that you are incapable of doing one of your normal actions for Y minutes; this can't be failed unless you die or unless it's combined with another goal you have to accomplish to reverse the transformation.

- Moral/factional avoidance: you can't gain advance with faction A if you have a black mark on your record from doing something related to faction B. You must clear your record or repudiate B to begin/resume advancing with A.

- Avoidance of the "cheap" way - you must build Z without using any of a list of the easiest/cheapest resources, and only use their more expensive substitutes.

- And as mentioned, complete a battle without using X ability, taking Y length of time, or taking Z damage

Have you studied the procedular quest determination of ProgressQuest?

is there a description of it or something online?

Servant of the Lord:

still digesting your list.

just finished looking at the get actions, about to start on talk actions.

under modifiers you listed:

don't get caught

isn't this already implied by any kill of someone with friends? or any non-lethal hostile action against anyone (where they're not dead and can catch you).

early insights gained from your list (so far):

Servant of the Lord:

Looking at these talk actions...

deceive looks to be a give/deliver/transport info action, where the info is false.

hmm... transport information, how many quest actions fit that description? may be more opportunity for simplification.

coerce: implies some means of coercion. this would probably be some type of "do harm until they give you info". a subset of get info or has(player,info). if you're free to get the info by any means (bribery vs coercion for example), its just a "get info" quest, if coercion is required by the questor, its would most likely be a get_info quest with a by_what_means modifier. its might be easier to handle with the conversation AI system than quest engine. IE no npc gives info to hostiles until x amount of harm is done to them first. so a has(player,info) quest where has(badguy,info) is the initial condition, would automatically imply coercion of some sort, such as the "attack to subdue" feature in the game i'm working on.

Oblivion has a coercion quest in the fighter's guild campaign. you kidnap a badguy, then you're supposed to damage him some and he talks some, then damage him some more and he spills his guts. last time i played it, i started by bribing the guy to max disposition. never had to throw a single punch at him. got done bribing, and it immediately went to "looks like he's ready to talk now", and then to "looks like he's had enough and will sing like a canary now". sure he's had enough! enough of my gold! <g>.

convert is an influence type action. influence should probably be listed as: influence/convert

give info would be a transport info action, I'd think.

order is a special case of give info. info: what to do (orders). from: superior. to: subordinate.

demand: seems to simply be a step along the way to competing a quest. you don't get mission completion by demanding the enemy remove its troops from your border, you get it when they comply, unless your the ambassador. in that case, you're playing messenger: transport info (demand) to badguy.

bully, similar case. if you're the "muscle", then this would probably be some sort of influence action with harm implied. You're using harm to influence someone's actions. Punch them in the nose and demand their lunch money or you'll do it again. of course another way to look at it is with the more generic has(bully,lunch money).

I really like that Has() condition! it implies and encapsulates so much!

it occurred to me that some conditions will automatically imply others: has(town center,500 wood) implies exists(town center). obviously, exists() will be implied in almost all cases.

blackmail is giving a threat to get an action from someone (such as they give you something, etc). if you don't get the action, you follow through on the threat.

that would probably be classified based on the action your trying to get. if you're blackmailing for money it would be acquire money, with a by_what_means modifier of blackmail. blackmail and coercion are tricky, you have to have something you can hold over them.

swap info is a two part quest: get info + give info.

moving objective modifier:

probably can be assumed. objectives that can move will move. you'll just have to goto(them). i'm kind of thinking that all travel required can be implied and assumed and doesn't need to be specified. except perhaps for the most basic case of at(player,location) IE a simple goto quest.

I guess it's a "Stop X from happening", which is a new quest type.