PSwiki - Recent changes [en]

Quest scripts syntax for AI

Talad — Mon, 06 Apr 2026 16:27:07 GMT

← Older revision		Revision as of 16:27, 6 April 2026
Line 56:		Line 56:
	All lines except comments should always end with a period or a question/exclamation mark. This is how the engine knows that directive is completed.		All lines except comments should always end with a period or a question/exclamation mark. This is how the engine knows that directive is completed.

	We also have the possibility to have multiple questions and answers in the same step, this is done usually when the discussion is about the same topic and doesn't require a separate QuestNote. In this case the structure is P: , then Menu: , then the npc line. The P must be unique so here we append a letter to the end, example 15005a, 15005b, ...		We also have the possibility to have multiple questions and answers in the same step, this is done usually when the discussion is about the same topic and doesn't require a separate QuestNote. In this case the structure is P: , then Menu: , then the npc line. The P must be unique so here we append a letter to the end, example 15005a, 15005b, ... But please note the step number will still be 5. So all Require and Complete will refer to 5, not to 5a or 5b.

	When we move to another NPC it's required to have a separate step.		When we move to another NPC it's required to have a separate step.

Quest scripts syntax

Talad — Mon, 06 Apr 2026 16:23:32 GMT

Untested Prerequisites

← Older revision		Revision as of 16:23, 6 April 2026
Line 719:		Line 719:
	else if (!strncasecmp(block,"equipped",8))		else if (!strncasecmp(block,"equipped",8))

	=== ~~Untested~~ Prerequisites ===		=== More Prerequisites ===
	~~Please contact engine in case you want to use any of these prerequisites, because those are untested.~~


	"time of day" // require time of day starthh-endhh (working)		"time of day" // require time of day starthh-endhh (working)

	~~"trait" //require trait name in place~~

	~~"guild" //NOTE: the both argument is implicitly defined~~

	"active magic" (working)		"active magic" (working)

	"~~known spell~~"		"race" (working)

	"race~~" (working)~~		Example: Require not race Klyros. Require race Kran.

	"gender" (working)		"gender" (working)

	~~"married"~~		Example: Require gender female.

	"possessed" (working)		"possessed" (working)
Line 744:		Line 737:

	"variable" //Require variable name. (working)		"variable" //Require variable name. (working)

			=== Untested Prerequisites ===
			Please contact engine in case you want to use any of these prerequisites, because those are untested.

			"trait" //require trait name in place

			"guild" //NOTE: the both argument is implicitly defined

			"known spell"

			"married"

	= Notes on Creating Quest Files (Rules and Header Information) =		= Notes on Creating Quest Files (Rules and Header Information) =

Quest scripts syntax for AI

Talad — Mon, 06 Apr 2026 16:17:00 GMT

@@ Line 2: / Line 2: @@
 Any line starting with # is a comment. We add at the start of the file the name and prerequisites as comments.
 The quest script is divided in steps. Each one being separated with this line:
-... NoRepeat
+  ... NoRepeat
 This line tells the engine to create a new step. Only the first step does not have the ... line
@@ Line 11: / Line 16: @@
 Every step starting from the second one, start with a comment stating the step number, this is important for readability. Example:
-# Step 2
+  # Step 2
 Each step can have a prerequisite step to be executed, example step 3 will require step 2 to be executed. If you have parallel steps, then the requirement for step 3 and step 4 can all point to step 2.
@@ Line 17: / Line 22: @@
 Requiments are expressed like this, where we substitute <quest name> with the name of the quest:
-Require completion of <quest name> step 2.
+  Require completion of <quest name> step 2.
 Every step must have a P: line with the questid plus a progressive number, which corresponds to the step. Example, assuming our quest number is 1500, and step is 2:
-P: 15002
+  P: 15002.
 Every step must have a Menu: line . This is what the player will select from the possible speak options. Example:
-Menu: Hello, who are you?
+  Menu: Hello, who are you?
 Every step must have a line with the answer from the NPC, which starts with the name of the NPC, example:
-Harnquist: I'm the local blacksmith!
+  Harnquist: I'm the local blacksmith!
 Every step must have a quest note that goes into the player journal summarizing what he accomplished or learned in that step. Example:
-QuestNote You met Harnquist the local blacksmith.
+  QuestNote You met Harnquist the local blacksmith.
-# Quest name
+  ... NoRepeat

Quest scripts syntax for AI

Talad — Mon, 06 Apr 2026 14:54:43 GMT

Created page with "This is the syntax to create a quest script. Any line starting with # is a comment. We add at the start of the file the name and prerequisites as comments. The quest script is divided in steps. Each one being separated with this line: ... NoRepeat This line tells the engine to create a new step. Only the first step does not have the ... line Every step starting from the second one, start with a comment stating the step number, this is important for readability. Exam..."

New page

This is the syntax to create a quest script.

Any line starting with # is a comment. We add at the start of the file the name and prerequisites as comments.

The quest script is divided in steps. Each one being separated with this line:

... NoRepeat

This line tells the engine to create a new step. Only the first step does not have the ... line

Every step starting from the second one, start with a comment stating the step number, this is important for readability. Example:

# Step 2

Each step can have a prerequisite step to be executed, example step 3 will require step 2 to be executed. If you have parallel steps, then the requirement for step 3 and step 4 can all point to step 2.

Requiments are expressed like this, where we substitute <quest name> with the name of the quest:

Require completion of <quest name> step 2.

Every step must have a P: line with the questid plus a progressive number, which corresponds to the step. Example, assuming our quest number is 1500, and step is 2:

P: 15002

Every step must have a Menu: line . This is what the player will select from the possible speak options. Example:

Menu: Hello, who are you?

Every step must have a line with the answer from the NPC, which starts with the name of the NPC, example:

Harnquist: I'm the local blacksmith!

Every step must have a quest note that goes into the player journal summarizing what he accomplished or learned in that step. Example:

QuestNote You met Harnquist the local blacksmith.

# Quest name