PSwiki - User contributions [en]

Quest scripts syntax

2026-06-04T10:02:06Z

Katu: /* Quest Timeout (Passing of time) */ Fixing formatting error

== Structure of a quest script ==
Quests are written out in chunks called steps. Each step covering the requirements of the previous one.

== Things to know before you start ==

* Quest scripts should written ideally in a text editor and now in MS Word or similar so that no illegal characters make it into the quest dialog which would result in errors when viewed in game.
* Quotes are usually the ones which break the scripts and :
* Only ' " should be used
* ‘ ’ ” “ … These should not be present in the text at all.
* Any line of text in the script which begins with a ‘#’ character is ignored by the server and only acts as a comment by the author so that they can leave explanations as to what is happening, or, give information about the step number.
* The start of a ‘step’ is defined by a series of three dots ‘...’ Everything after this text up until the next ‘...’ is included in the step. The only unique case is the first step, this does not need ‘...’ and includes all the text before the first ‘...’

== Important rules concerning steps ==

* Every step in the quest should be explicitly completed or locked correctly. Example: "Complete Quest Name Step #" before the Quest is completed.
* A step can require the completion of another step by the command: "Requires completion of Quest Name Step #"
* Step 1 does not exist, step 1 is part of the start script (where you use the command "give me a quest") and cannot be used as a require completion of step number.
* You may have multiple Require Completes at the beginning of a step.
* A step may also require another step NOT to have been completed with the command: "Require no completion of Quest Name Step #".
* The Quest name must be exact! It is case sensitive. The same goes for NPC names.
* Each step should be commented like this: "# Step 2 - A description of actions of this step". # Marks it as a comment not processed by the engine.
* You can also check for statements with this syntax: "Require <no/not> operator1 | <no/not> operator2 | ...| <no/not> operatorN." Where operator is a prerequisite (see below the prerequisite chapter), from completion of to time of day etc. The | represents the OR. ''Example: "Require completion of Questname Step 3 | completion of Questname Step 7."''

Let's see an example before beginning the explanation. The following example is made of two steps.

'''Example: Structure 1'''
P: Short Trigger.

Menu: Do you have any work for me to do?

NPC Name: Yes I do. Just breathe one time.

Assign Quest.

...

P: Ok, I did it!

NPC Name: Great, your quest is completed.

== Syntax Basics ==

=== Comments ===
To create a comment line you must start the line with a "#". These lines are not evaluated by the engine as things that need to be done. These comment lines show what is going on and what are the intentions of the quest writer. This is important because more than one person are often working on a quest script, or eventually for laterbug fixing it will be easier to find the exact problem without reading the entire quest.

Each step in a quest should be started by a comment like this "#Step 2 - Description of step.". You can use comments to more that just noting the step number. Any where within the script you can add comments to help your fellow scripters understand the code. We will use comments to explain things within the scripts here.

=== Trigger and Menu ===
The trigger is for the engine, while the menu is what shows up in the player quest menu. The trigger is defined by a "P:".

P: use to be what the player typed to trigger the step, but with the menu system are now used as a description of what step the player is choosing, for example P:yeshelp. (slide 3). The only time you must use exact text is when a player types the answer to a question you pose them

Because you are talking to the engine it must be exact a colon after the "P:" and a period at the end of the sentence. This is also true of the Menu in every case in which the player (P) says something to the NPC in question "P: Short Trigger." comes first, then below comes the "Menu:" line, with exactly the same requirements.

"Menu": Text is what the player sees when they look at the quest menu.

Please remember that the engine does not think, it reacts to the written cues, so the syntax MUST be exact. The first player statement gives the engine the quest name. The Menu allows the player to ask for the quest from the NPC.

Having the two "P:" and two "Menu:" on the same line informs the engine that the player has two different options. It is standard that the "P:" line is above the "Menu:" line and the "No." answer comes first.

These lines trigger the NPC response. In more elaborate quests the "Menu:" line may have variations on the No. or Yes. response. However remember KISS (Keep It Simple Stupid) is generally a good thing to keep in mind when you are beginning. You can have many options, but remember each "P:" must have a matching "Menu:" and they must be put in the same order

In order to include a free textfield, you will have to include a quotation mark after the menu. The <?> has to be followed by <=> and a text. This will produce a printout of the text and the user will be able to enter a free text. E.g. "Menu: ?=What shall Jardet do?" This will result in the text "What shall Jardet do?" being printed, followed by free form input.

P: *. P: rock pick.
Menu: ?=Please tell me your answer.
Smith: No, you didn't get the right answer.
Smith: Yes, it's a rock pick!.

P: Nothirstyinterst. P: Yesthirstyintrest.
Menu: No, sounds like work. Menu: Sure, I can get it for you.
Serana Tuvi: Alright. I will see you around then, stranger.
Serana Tuvi: Ah, good good.
<blockquote>'''Note:''' Remember the ": " after the P and Menu are important, as is the "." at the end of the line.

'''Note:''' For triggers used to start quests, never use NPC names into it, because this will confuse the engine, and the trigger will not be recognized.

'''Note:''' Every P: used in one step must be on the same line

'''Note:''' Every Menu: used in one step must be on the same line

'''Note:''' Every NPC: used in one step must be on different lines.</blockquote>

=== NPC Response ===
Aono Rikas: here you can add a response.

The line above is interpreted as an answer from the NPC and the engine will extract the name before the colon (:) + space as the NPC involved in this step of the quest. From now on, we will call this a response.

The full name of the NPC is required, just the first name will not work. If it is only one name e.g Harnquist use that, and if your NPC somehow ends up with three names use all of them.

In the first step of a quest the NPC statement will end in a question mark and is triggered by the first 2 lines. Responses are linked to each of the Triggers and Menus. So if you have two triggers you need two menu options and two NPC responses. All arranged in the same order.

=== Dialogues ===
The dialogues are the most important part of the quest for a player to get immersed. So let us talk about how to make the dialogue.

* Every punctuation, exclamation mark and question mark will create a short pause in the dialogue and create a new line.
* To create actions all you have to do is to use square brackets within the dialogue like this "Blablabla [NPC Name picks his nose] Bla bla blabla"
You may use also these commands:

* $playerrace can be used in an impersonal and a personal manner in terms of context, consider its usage carefully.

* $sir which gives you "Sir" or "Madam" or "Gemma" depending on the gender of the player's character. Again, this can be used to positive and negative effect. Be mindful of the NPCâ€™s tone. (Gemma is the honorific for Kran.)
* $playername clearly not to be used in newbie quests, have NPC establish rapport use this in second quest or even the third time a player works with a given NPC.

=== Quest Notes ===
Every step must have a quest note that goes into the player journal summarizing what he accomplished or learned in that step. Make sure to leave a hint of where to go next.

Example:
QuestNote You met Harnquist the local blacksmith.

== A sample quest script ==

=== The first step ===
As previously mentioned Step 1 does not exist, it is just the start of the quest, and can not be required by subsequent steps. The Start of the Quest will look something like the example at the beginning (Structure 1).

The same example can also be scripted like this:

'''Example: Structure 2'''
P: Short trigger.

Menu: Initial question, give me a quest.

NPC Name: Yes, I do have a quest for you. I need you to give Item of Importance to NPC2 Name.

P: Yes P: No.

Menu: Yes, I will do that. Menu: No way stupid.

NPC Name: This is the response from the NPC if answer is Yes.

Give 1 Item of Importance.

Assign Quest.

NPC Name: This is the response from the NPC if answer is No.

In Structure 2 the answers "No" and "Yes" are inverted, like the two "Menu:" commands, so it will give the same result as Structure 1. (Answer No: nothing happens. Answer Yes: the player will get 1Item of Importance and the Quest.)

Now, let us use a more detailed example. We will make a very simple quest: Aono wants to deliver a bottle of milk to Orchibaly. The player can choose the quest from Aono's quest menu. Orchibaly will then give the player 2 pies and a receipt to give back to Aono. The first step will be the step that assigns the quest. The P: tells the engine that this line represents something the player will say to the NPC, but what you must pay extra attention to is the "Menu:" This will be what the player will see as an option in the quest menu. If there are several options you will have to create one "P:" and a "Menu:" for each of them.

Here we firstly gives the player the option to ask for the quest. Then Aono describes the nature of the quest and the player can choose yes or no. Right after the "Menu:" line the NPC responsewill be put. In this example Aono will reply: "Well, I will get someone else to do it for me." if the player says no or "That's great. Here is the milk. Be sure not to spill it. TellOrchibaly I sent you.", give the player 1 Milk Bottle and assign the quest.

'''Example: Assign Quest'''
# Quest: Delivery for Aono Rikas

# Quest Description: Sample Quest.

# The rest of the header will not be covered here.

# Step 1 Aono Rikas in Hydlaa needs someone to deliver milk to Orchibally Gurpleferd in Ojaveda.

P: Delivery for Aono Rikas.

Menu: Are there any jobs you need done?

Aono Rikas: Well, yes. I need some milk delivered to Orchibaly in Ojaveda. Can you do this for me?

P: No. P: Yes.

Menu: No. Menu: Yes.

Aono Rikas: Well I will get someone else to do it for me.

Aono Rikas: That's great. Here is the milk. Be sure not to spill it. Tell Orchibaly I sent you.

Give 1 Milk Bottle.

Assign Quest.

A quest can be automatically assigned or there can be a step at the beginning of the quest to ask the player if he accepts it.

If you want to assign it automatically use this format:

P: give me a quest. Or any quest trigger.
Menu: what the play sees go here.
NPC: What the NPC says goes here.
Assign quest.

If you want to ask the player use this format:

P: give me a quest. Or any quest trigger.
Menu: what the play sees go here.
NPC: What the NPC says goes here, with the question if you want to help.
P: nohelp. P: yeshelp.
Menu: I don't want to. Menu: Yes I will help.
NPC: Fine... Go away.
NPC: Good great.
Assign quest.
<blockquote>'''Note:''' The “Assign quest.” command will only trigger after the second NPC: dialogue line is triggered, nothing happens if the first is triggered.</blockquote>

=== The next step ===
To separate the step we use "..." and then a comment on what step it is and what the step is about. If you don't want this step to be repeatable you will also have to add "NoRepeat" after the "...". The second step does not need a completion of Step 1, because Step 1 does not exist so to speak. The structure will be more or less the same as for the initial step.

Let us continue our Delivery for Aono Quest. We have assigned the quest and the player has been given 1 Milk Bottle to give to Orchibaly. Now the player must give that milk to Orchibaly. Either by using the give GUI or by using the quest menu. The first thing we have to do here is to set up the give trigger. If the player gives Orchibaly the milk, he will answer "Oh, yes the milk. Please give it to me. Now i need you to deliver these two pies and this receipt back toAono.", Give the player 2 pies and a Receipt from Orchibaly. The step is then completed.

In this example although the player is given two pies no "s" is added to the line. This is important, especially because most writers tend to add a plural automatically to plural items. Remember the engine does not. An item is designated in the singular, the engine always interprets it in the singular regardless of the number included. The numbers are again not spelt out and Arabic numerals used. Remember that each "Player gives"-command must have menu option in the next line.

'''Example: Step 2'''
... NoRepeat

# Step 2 - Player gives the milk to Orchibaly

Player gives Orchibaly Gurpleferd 1 Milk Bottle.

Menu: Aono asked me to give you this bottle of milk.

Orchibaly Gurpleferd: Thanks, please give it to me. Now deliver two pies and a receipt back to Aono.

Give 2 Pie. Give Receipt from Orchibaly.

Complete Delivery for Aono Rikas Step 2.

Completing a step

At the end of a step remember to insert the line:

"Complete Delivery for Aono Rikas Step 2."
<blockquote>
Note the use of Capitals, the use of the quest name, the use of the appropriate numeral and the period at the end of the sentence. The line marks the step as complete and allows the player and the quest to move forward.</blockquote>

=== Last step ===
To make sure the player has completed the previous step we start with "Require completion of delivery for Aono step 2.". Then we move on to the trigger which is the player giving 2 pies and the receipt to Aono. Aono answers "Ah, pie. Thank you. Please accept this for your time.", gives the player a pie and 100Tria. The step is closed and so is the quest with "Complete Delivery for Aono Rikas."

'''Example: Last Step'''
...NoRepeat.

# Step 3 - Player has now returned to Aono in Hydlaa. Player must now give Aono the 2 Pies and 1 Receipt.

Require completion of delivery for Aono step 2.

Player gives Aono Rikas 2 Pie, 1 Receipt.

Menu: Here are your pies and your receipt.

Aono Rikas: Ah, pie. Thank you. Please accept this for your time.

Give 100 Tria. Give 1 Pie.

Complete Delivery for Aono Rikas.
<blockquote>
'''NOTE:''' If you use multiple options in the last step of a quest you have to explicitly complete the quest with a command for the first option.</blockquote>
'''Example: Last step with multiple options'''

P: No. P: Yes.

Merchant: Quest doesn't complete automatically so make sure you have added a complete line for this response.

Complete Harnquist Needs Gold Step 2. Complete Harnquist Needs Gold.

Merchant: Quest completes automatically because it is the last line in quest so no complete line is required.

Complete Harnquist Needs Gold Step 2.

If you omit the Complete Step and Complete Quest line, the quest will not end properly when choosing "no".

=== Branches of a quest (Non exclusive) ===
Some times you want to have several different outcomes for a quest. Let us use the Delivery quest once again. If the first NPC says that you must NOT give the milk to some one else... specially NPC3. Then you should also add the option for the player to actually give the milk to NPC3 . This will complicate your script a bit, but is not as hard as it might seem. Most of the job is done by placing the right "Require completion of" and "Require no completion of" commands.

Let us take a look at that Delivery Quest again. Now we want to add an option for the player to give the milk to Reffitia instead. Reffitia will shake the milk until it becomes butter and this will make Orchibaly angry and demand a new bottle of milk. To do that we will have to add a few more steps and we will start from step 2 as step 1 will be the same as above.

The Third step will be our previous Step 2. And the last step will be the same. Though Aono should mention something like: "Make sure you don't give that milk toReffitia." in Step 1.<blockquote>
IMPORTANT NOTE: This is a non exclusive branching, meaning that the first branch is available also when executing the second one.

IMPORTANT NOTE: We will not add an additional step for the player to get milk again from Aono, but the player have to figure out another way to get hold of it (Buy from an NPC).</blockquote>

'''Example: Branching'''
... NoRepeat

# Step 2 - Alternative is to give the milk to refittia

Player gives 1 Milk Bottle to Reffitia

Menu: Here Reffitia, take this milk.

Reffitia Thamal: Ah! Orchibaly's milk. Here, now you can give the bottle to Orchibaly.

Give 1 Bottle of Butter.

Complete Delivery for Aono Rikas Step 2.

... NoRepeat

# Step 3 - Player gives bottle of butter to Orchy.
# The player then have to find another way of getting a bottle of milk (buy from NPC?)

Require completion of Delivery for Aono Rikas Step 2.

Player gives Orchibaly Gurpleferd 1 Bottle of Butter.

Menu: Um, here is the milk from Aono.

Orchibaly Gurpleferd: Milk? This is butter. You better get me another bottle of milk, fast!

Complete Delivery for Aono Rikas Step 3.

... NoRepeat

# Step 4 - Player gives the milk to Orchibaly

Player gives Orchibaly Gurpleferd 1 Milk Bottle.

Menu: Aono asked me to give you this milk.

Orchibaly Gurpleferd: Oh, yes the milk. Now i need you to deliver these two pies and this receipt back to Aono.

Give 2 Pies. Give Receipt from Orchibaly.

Complete Delivery for Aono Rikas Step 4.

... NoRepeat

# Step 5 - Player has now returned to Aono in Hydlaa. Player must now give Aono the 2 Pies and 1 Receipt.

Require completion of Delivery for Aono Rikas Step 4.

Player gives Aono Rikas 2 Pie, 1 Receipt.

Menu: Here take these pies and the receipt.

Aono Rikas: Ah, pie. Thank you. Please accept this for your time.

Give 100 Tria. Give 1 Pie.

Complete Delivery for Aono Rikas.

=== Alternative outcome ===
If we wanted the quest to have a different outcome if the player gives the milk to Reffitia than to Orchibaly we would need to get creative with the require commands. Let us say that if the player gives butter to Orchibaly he will give "bad pies" so when Aono receives them and takes a taste he will be very angry and no reward is given. To do this we will have to add just one more step. Let us start with step 3. Here we will have to change only the NPC response a bit to something like "Milk? This is butter. Have you been shaking the bottle all the way over here? This is completely useless to me, butter I have more than enough of. Any way someMenki came with another bottle just before you. Here takes these pies to Aono . Oh, and don't forget this receipt.". Step 4 will be the step where the player gives the bad pies to Aono, this step will complete the quest. Step 5 and 6 are the outcome if the player gives the milk directly toOrchibaly. Notice that Step 5 require a NO completion of Step 4. This is actually not necessary for this script, because the previous the other branch of the quest, ending in step 4 closes the quest it self.

'''Example: Alternative Outcome'''
# Step 3 - Player gives bottle of butter to Orchy. And receives 2 pies and a receipt

Require completion of Delivery for Aono Rikas Step 2.

Player gives Orchibaly Gurpleferd 1 Bottle of Butter.

Menu: Um, here is the milk from Aono.

Orchibaly Gurpleferd: Milk? This is butter. You better get me another bottle of milk, fast!

Give 2 Pie. Give 1 Receipt from Orchibaly.

Complete Delivery for Aono Rikas Step 3.

... NoRepeat

# Step 4 - Player gives the "bad" pies and the receipt to Aono. Receives gunk as reward and Quest is completed.

Require completion of Delivery for Aono Rikas Step 3

Player gives Orchibaly Gurpleferd 2 Pie, 1 Receipt from Orchibaly.

Menu: Here take these pies and the receipt.

Aono Rikas: Ah, pie. Thank you. [Aono takes a bite at the pie] You have tricked me!

Give 1 Gunk.

Complete Delivery for Aono Rikas Step 4.

Complete Delivery for Aono Rikas.

...
# Step 5 - Player gives the milk directly to Orchibaly.

Require no completion of Delivery for Aono Step 4.

Player gives Orchibaly Gurpleferd 1 Milk Bottle.

Menu: Aono asked me to give you this milk.

Orchibaly Gurpleferd: Oh, yes the milk. Now i need you to deliver these two pies and this receipt back to Aono.

Give 2 Pies. Give Receipt from Orchibaly.

Complete Delivery for Aono Rikas Step 5.

... NoRepeat

# Step 6 - Player has now returned to Aono in Hydlaa. Player must now give Aono the 2 Pies and 1 Receipt.

Require completion of Delivery for Aono Rikas Step 4.

Player gives Aono Rikas 2 Pie, 1 Receipt.

Menu: Here take these pies and the receipt.

Aono Rikas: Ah, pie. Thank you. Please accept this for your time.

Give 100 Tria. Give 1 Pie.

Complete Delivery for Aono Rikas.

=== Quest Timeout (Passing of time) ===

If you want to allow a certain part of the quest to wait a certain amount of time before it can be a executed, you can use this script:
Run script give_quest_timeout <<'Time until Harnquist is ready',6>>
this will create a temporary active magic with name 'Time until Harnquist is ready' which will last for 6 minutes.

Then in the prerequisite of the step have this:
# Step 12.
Require active magic Time until Harnquist is ready.
P: swordnotready.
Menu: Is Vresa's sword ready yet?
Harnquist: No, not yet.

...
# Step 13.
Require no active magic Time until Harnquist is ready.
P: about Vresa sword.
Menu: Is Vresa's sword ready?
Harnquist: Yes, Vresa's sword is done.

=== Important commands and expressions used ===

=== Assign Quest. ===
This line tells the engine to assign the quest to the player and generally results in the "YOU GOT A QUEST". and placing the quest in the player's quest log, under "uncompleted". Again remember to be exact here, Capitalize the two words and put a "." at the end. It cannot be emphasized enough that the engine only interprets what it sees and the way it sees it. If you are not precise the quest will NOT happen or in the cases of the next steps move forward.

=== ... ===
The three dots mark the beginning of a new step. Better, the three dots create a new step. So you need a "three dots" line before every "Complete Quest Name Step #"

=== NoRepeat. ===
This line means that the quest step cannot be done over and over. Note that there are three periods "..." a space and 'NoRepeat.' is one word not two. Each part of this sentence is required in exactly this form.

Basically "..." tells the engine that some time can pass before the next lines are used.

NoRepeat allows this quest step to be only done one time. This also applies to actions as seen in later steps. (in reality NoRepeat is a synonym for Require no completion of "this step")

=== Require completion of Quest Name Step #. ===
This command is like a closed door. To open it and enter in the current step the player needs to complete the step number #. You can also refer to a future step (for example, you're on step 4 and add "Require completion of Quest Name Step 8.")

=== Require no completion of Quest Name Step #. ===
This command is like an open door. The player is free to continue the quest and entering the current step, UNLESS he completed the step number #. Completing the step number # will close the door. Forever! You can also refer to a future step.

=== Complete Quest A Step. ===
You can complete one step in another one. But remember to insert one "..." line for every "Complete Quest Name Step #." line.
Complete Delivery for Aono Rikas Step 2.

=== Complete Quest Name. ===
This command will end the quest. After this the quest will be deleted from the uncompleted quest list and appear in the Completed quest list.
Complete Delivery for Aono Rikas.

=== P: ===
The trigger is actually a ghost from the previous scripting system, but it is still needed (for now). Before the player had to type the exact trigger stated after the "P:". Now they click the option from "Menu:". Triggers must be four words or less. Triggers must end with a period, no other punctuation is allowed (question marks especially are known to break aquest on the server).

If you want multiple phrases to activate the same trigger, you can just separate the phrases by a period; for example: "P: about guards. about hydlaa guards. about hydlaa militia." In this case the NPC's response will be fired on any of the three options. This technique can be used also when you have multiple choices: "P: one. two. P: more.". Both 'one' and 'two' will trigger the first response, while 'more' will trigger the second.

WARNING: Triggers cannot contain any of the following words: a, am, an, and, any, anything, are, do, I, is, isnâ€™t, please, that, the, this, to, too.

They also may not contain the name of the NPC you're talking to as that'll be stripped.

These words just take up space in a trigger as they are dropped by the engine when evaluating player response. To make the best use of your word counts ignore them when writing your triggers.Example: If you wanted the player to say 'please help Levrus' the trigger would become 'help' as please would be an ignored word and Levrus would confuse the server.

WARNING: If a player needs to write "NPC needs this" syntax it as "NPC wants this".

=== Menu: ===
After this command you can add the sentence said by the player in game. This sentence will appear on the screen and could be selected when one talks to the NPC.

Remember that for every menu line you need to create a response from the NPC.

=== Give ===
Give is a very useful command. It tells the engine to give the player items. Be it rewards or special items needed for the quest. When you reward a player, you can basically give items and/or experience. The syntax to award 1500 experience points would be: "Give 1500 Exp." Note that "Exp" is case-sensitive. You can also reward items AND experience, using this syntax: "Give Leather Gloves. Give 1500 Exp." Remember that you can only have two give commands on the same line, but you can have multiple lines, Remember to keep a clean style, it is prefered to only have one item per line.

'''Example: Give more than two items'''
Give 1 Leather Gloves.
Give 1500 Exp.
Give 1 Apple.

You can also add a number if you need to give more than one item (like you do for experience) example: "Give 5 Iron Ingot." It is not necessary in the case of one item to include the numeral, however it is good practice to do so as numerals tell the engine how many and should be written as a numeral, a word will NOT work as the engine cannot interpret it as such. Remember that all special items must be declared in the script header.

Another option you have is to give one item OR another. The following will pop up a window in which the player has to choose just one item:

'''Example: Give the player a choice between items'''
Give Cold or Arrow or Energy.
'''WARNING:''' At this time, don't use the following in an OR option: Tria, hexa, octa, circles, or items without a graphic. Also, for now, do NOT put quantities in front of items that are given using the "OR" parameter. An example of what NOT to do: "Give 1 Cold or 1 Arrow or 1 Energy." This will lock the server right up. An example of what SHOULD be done: "Give Cold or Arrow or Energy." (Check this statement if it is correct. --Katu)

=== Player gives NPC Name 1 Item ===
This can be used as a trigger (instead of the "P:"). It tells the engine to trigger the NPC dialogue when one or any fixed amount of a special item.

When a player have to give multiple items just add them to the original line using a comma:

'''Example Player gives item'''
Player gives Harnquist Water Pouch, 1 Pie.

'''WARNING:''' Item name rules must be followed at all times.

=== Item Name Rules ===

* Notice that the item name is "Iron Ingot", so "Iron Ingots" will not work, even if itâ€™s the correct plural form. Keep all names singular.
* Also, do not use a number (3, 14, etc) in the name of an item. An item called 3 Circles Receipt will probably generate problems when we script "Give 3 Circles Receipt." It is better named "Three Circles Receipt."
* Numbers should be spelled out everywhere unless you are referring to the quantity given or dealing with a trigger (give me 5 apples. give me five apples.) as both would be correct in a trigger.
* Character limit for an item name is 60 characters.
* Do not use an s' in an item name, like "Levrus' Left Shoe," use "Left Shoe of Levrus" or a similar substitute instead.

=== Set and unset a variable and Require a variable ===
You can set a variable to be later used by the quest or other quests. Variables are set on the character and visible from all quests.
Variables here are only boolean, so the only valid value is 1. The requirements only checks if the variable is set or not.

Use a prefix for all variables, so they don't get confused with other variables: "Quest_questname_variablename".
Smith: Here is your winch access
Setvariable Quest_Winch_Access 1

You can then require a variable to be set as prerequisite of a quest step.
Require variable Quest_Winch_Access.
P: access.
Menu: I have access
Bobaus: Ok, good.

If you want to unset a variable use the "Unsetvariable" command:
Unsetvariable Quest_Alchemy_Winch_Access.

=== Rewards at the end of the quest ===
When completing a quest, the player usually gets experience and money, or some items. In particular for experience and money you should use the following scripts. This allows us to split the rewards on a scale from 1 to 10 and then to tweak the actual values in the engine. The values in brackets indicate the complexity of the quest. The more complex the more rewards the player will get.

Run script give_quest_money <<3>>.
Run script give_quest_exp <<2>>.
You can also award faction points by using "give_quest_faction" , the number given is multiplied by 5 so if you want +5 point, you need 1 on the second parameter:
Run script give_quest_faction <<'Essential Trail', 1>>.
We have script also to push the faction point up to a given value, if you are already higher, this script will do nothing.
Run script give_quest_faction_level <<'Essential Trail', 2>>.

* value = 1-> max faction points = 10;
* value = 2-> max faction points = 20;
* value = 3-> max faction points = 35;
* value = 4-> max faction points = 55;
* value = 5-> max faction points = 75;
* value = 6-> max faction points = 100;
* value = 7-> max faction points = 125;
* value = 8-> max faction points = 150;
* value = 9-> max faction points = 200;

If you want to assign a faction title you can use this script. In the example it will assign the second title.
Run script give_quest_faction_title <<'Essential Trail', 2>>.

== The Quest Header ==
The header should contain a lot of information. All the information is commented out by a "#". The example below is from one of the mount quests.
First section is information about the quest itself. Name of the quest, a short description and category. Categories will be discussed in detail later on.

The next sections are for unique items used in the quest, name of the item followed by the description.

The third section is for recording versions of the script and all naming authors. Also who last edited the quest should be noted.

The last section is for additional metadata which will be added to the quest in the database (not part of the db) and will be used by the engine to determine lockouts and prerequisites. Here it locks all players from doing the quest again and locks all other players to take the quest with 60 seconds.

Lastly we tell the engine that the player have to complete the Ring of Familiar quest before this one. Note that these comments aren't taken by the engine; it's the duty of who loads the quest to fill the correct entries with the data found in the header: so it's just a way to keep all data together on the script.

'''Example: Header'''
# Quest name: Drifting for a Drifter
# Quest Description: Taemian wants to sell you a mount
# Quest Category: General
# ----------------------
# Quest Items: Item name/Item description
# Taemian's Pouch: - Pouch with all sorts of coins
# Green Gem of the Drifter - A magical gem with a green glow
# Unsigned Drifter Permit - A permit that still needs to be signed by Datal
# Signed Drifter Permit - A permit that has been signed by Datal
# ----------------------
# Variables used in this quest
# ----------------------
# Quest specific variables used in this quest
# ----------------------
# Author(s): Ravna, Katu, weltall
# Current Version: 1.01
# Player lockout: -1
# Quest lockout: 60
# Prerequisites: <nowiki><pre><completed quest="Ring of Familiar"/></pre></nowiki>
# Variables used: Quest_Variable_Name used to do.....
# ----------------------
# Version history and change log
# Last edited by: weltall
# Version 1.00: Initial draft - 05/01/2010 - Katu.
# Version 1.01: Added extra steps - 1/22/2011 - Venalan.
# ----------------------

==== Quest Lockouts ====
Each quest has two different lockout types:

* Player lockout: When this parameter is set, the engine will wait the specified amount of seconds before allowing the same player to redo the same quest. If you want a quest to be available to each player only one time, then set the lockout to -1. Setting it to 600 will have the engine wait 10 minutes before unlocking the quest again.
* Quest lockout: When this parameter is set, the engine will wait the specified amount of seconds before reactivating the quest for ALL players. This means no one can start the same quest during this period, but the ones that had it already active can complete it.

Usually we want quests to be unique to players, so most have a player lockout -1, except the very simple ones. Try always to think if itâ€™s meaningful for that player to redo it. (For example, Harnquist can require iron ore more than once, but won't need to teach you how to make a sword more than once.)

=== Prerequisites ===
'''Example: Prerequisites'''

A sample of the coding used to set prerequisites for a quest (All on one line):
<nowiki><pre><and></nowiki>
<completed quest="Test Quest One"/>
<completed quest="Test Quest Two"/>
<completed quest="Test Quest Three"/>
<assigned quest="Test Quest Four"/>
<not><completed quest="Delivery for Aono Riskas"/></not>
<not><completed quest="Gorbiak Disease"/></not>
</and><nowiki></pre></nowiki>

This sample requires that the player have completed Test Quests 1 through 3, have Test Quest 4 assigned (not completed) and have NOT completed Fancy Dancing and High-Class Aspirations. To get these arranged correctly can take some practice if one is not familiar with working with booleans, so it is best to include a plain-English comments of what you wish your pre-requisites to be in addition to the one with the "pre" coding statements.

== Requirements and Prerequisites ==
You can have as many requirements as you wish for a step, but again we remind you to keep it as simple as possible, so thing thoroughly through your choices here.

=== Multiple Requirements with OR ===
You can have an "or" statement between requirements by using "|":
Require Completion of Quest Winch Access | Completion of Harnquist is Hungry.
This needs all to be on one line.

=== Require Compendium ===
You can require the player to have a certain knowledge in the Compendium.
Require compendium creature StoneHammer.
P: comps
Menu: I know everything about the StoneHammers!
Fighter3: WOW
...
Require no compendium creature StoneHammer.
P: nocomps
Menu: Sorry I dont know anything about StoneHammers!
Fighter3: Ah, study more!
The syntax is: compendium <creature/plant/mineral> <name>

Another more complex version of the prerequisites is the: REQUIRE MIN <number>: this tells the engine that there are specific requirements to be fulfilled before the player is able to get the quest. This script indicated it requires a minimum number of quests to be completed in a given list.

=== Require min and Require Category Min ===
Example:
require min 2 of Quest1, Quest2, Quest3.
To match this prerequisite the player can complete Quest1 and Quest3 or 2 and 3, or all 3. The request is minimum 2 in the given list.

CATEGORY MIN <number>: quests have an attribute called "category", we use it to identify the difficulty of quests, but can be used of any other purpose, for example one can say that a group of quests is "Evil" or "Laanx related" or " Newbie". Just one category is allowed per quest. This prerequisite allows you to specify the category and the minimum number of quests completed in that category.

=== Require Time of Day ===
Requires the time of day to be at a specific point. The in game time has 24 hours.

Example:
Require time of day 1-2.
This example will trigger when the game time is between 1 and 2.

=== Require Active Magic ===
Checks if the player character has active magic.
Require active magic Weakness.

=== Require Race ===
"race" (working)
Require not race Klyros. Require race Kran.

=== Require Gender ===
"gender" (working)
Require gender female.

=== Require Possessed ===
Checking if the player character possesses an item/ has it in their inventory:
Require possessed item Ruby Crystal.
You can also check the amount of items as well as the quality of the items:
Require Possessed amount 3 200-300 item Steel Falchion.
it works also with money, as we handle this specifically. It will convert any currency, and check player total money for it.
Require no possessed amount 500 item Tria.

=== Require Skill ===
Require skill <buffed> name <skillmin>-<skillmax>.

=== Require Variable ===
Require variable Quest_Winch_Access.

=== Require Trait ===
Check if the player character has certain traits.
Require trait Black in HAIR_COLOR.
The different traits are: "NONE","FACE","HAIR_STYLE","BEARD_STYLE","HAIR_COLOR","SKIN_TONE","ITEM", "EYE_COLOR"

=== Require Guild ===
Unknown if this works.

=== Require Known Spell ===
Check if the character knows a spell.
Require known spell Nature Intuition.

=== Require Equipped ===
Checks if the player has a certain item equipped.
Require equipped category Armor - Helms.

Require no equipped category Armor - Helms.

Require equipped item Sword Handle.

Require not equipped item Sword Handle.

=== Require Married ===
This is untested and unknown if it works.

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

* The quest documents you submit should always be in notepad format: this is to avoid special characters added by Word or other text editors, most notably "smart quotes" which will appear as squares in game. Notepad++ is recommended, HIGHLY recommended.
* Use only ANSI encoding.
* The file name when saving the quest should begin with 'Quest' , then have the name of the quest. For example: Quest Hinoserri Cannot See.txt
* Titles of quests should follow some scheme of capitalization. There are many sets of rules, but a quick and easy format is to capitalize the first word and then all other words, except a, an, the, at, by, for, in, of, on, to, up, and, as, but, it, or, and nor.
* Each quest script begins with the title and a one or two sentence description; this is what the player reads so keep that in mind. The proper way to do this is to "comment out" your description and quest title, this is done by beginning a line with the number sign or pound symbol (#). Also, any quest item created for your quest should have a description written into the quest. Notes on quest items should also be commented out. Lastly, there should also be a "Quest Category" line that must be commented out as well. Approved quest categories are: Alchemy, Black Flame, Chain (don't use this one unless told), Cooking, Death Realm, Easy, Gugrontid, Magic Ways, Medium, Metal Working, Newbie, Repeatable. This is a work in progress, so if you have any questions ask an associate dev or developer. No quest can have more than one category - pick one and ONLY one. New quest categories must be approved by the associate devs/devs before use.

Quest scripts syntax

2026-06-04T09:59:33Z

Katu: Large update. Updated a lot of info, restructured some of the page and fixed the text formats for sections.

== Structure of a quest script ==
Quests are written out in chunks called steps. Each step covering the requirements of the previous one.

== Things to know before you start ==

* Quest scripts should written ideally in a text editor and now in MS Word or similar so that no illegal characters make it into the quest dialog which would result in errors when viewed in game.
* Quotes are usually the ones which break the scripts and :
* Only ' " should be used
* ‘ ’ ” “ … These should not be present in the text at all.
* Any line of text in the script which begins with a ‘#’ character is ignored by the server and only acts as a comment by the author so that they can leave explanations as to what is happening, or, give information about the step number.
* The start of a ‘step’ is defined by a series of three dots ‘...’ Everything after this text up until the next ‘...’ is included in the step. The only unique case is the first step, this does not need ‘...’ and includes all the text before the first ‘...’

== Important rules concerning steps ==

* Every step in the quest should be explicitly completed or locked correctly. Example: "Complete Quest Name Step #" before the Quest is completed.
* A step can require the completion of another step by the command: "Requires completion of Quest Name Step #"
* Step 1 does not exist, step 1 is part of the start script (where you use the command "give me a quest") and cannot be used as a require completion of step number.
* You may have multiple Require Completes at the beginning of a step.
* A step may also require another step NOT to have been completed with the command: "Require no completion of Quest Name Step #".
* The Quest name must be exact! It is case sensitive. The same goes for NPC names.
* Each step should be commented like this: "# Step 2 - A description of actions of this step". # Marks it as a comment not processed by the engine.
* You can also check for statements with this syntax: "Require <no/not> operator1 | <no/not> operator2 | ...| <no/not> operatorN." Where operator is a prerequisite (see below the prerequisite chapter), from completion of to time of day etc. The | represents the OR. ''Example: "Require completion of Questname Step 3 | completion of Questname Step 7."''

Let's see an example before beginning the explanation. The following example is made of two steps.

'''Example: Structure 1'''
P: Short Trigger.

Menu: Do you have any work for me to do?

NPC Name: Yes I do. Just breathe one time.

Assign Quest.

...

P: Ok, I did it!

NPC Name: Great, your quest is completed.

== Syntax Basics ==

=== Comments ===
To create a comment line you must start the line with a "#". These lines are not evaluated by the engine as things that need to be done. These comment lines show what is going on and what are the intentions of the quest writer. This is important because more than one person are often working on a quest script, or eventually for laterbug fixing it will be easier to find the exact problem without reading the entire quest.

Each step in a quest should be started by a comment like this "#Step 2 - Description of step.". You can use comments to more that just noting the step number. Any where within the script you can add comments to help your fellow scripters understand the code. We will use comments to explain things within the scripts here.

=== Trigger and Menu ===
The trigger is for the engine, while the menu is what shows up in the player quest menu. The trigger is defined by a "P:".

P: use to be what the player typed to trigger the step, but with the menu system are now used as a description of what step the player is choosing, for example P:yeshelp. (slide 3). The only time you must use exact text is when a player types the answer to a question you pose them

Because you are talking to the engine it must be exact a colon after the "P:" and a period at the end of the sentence. This is also true of the Menu in every case in which the player (P) says something to the NPC in question "P: Short Trigger." comes first, then below comes the "Menu:" line, with exactly the same requirements.

"Menu": Text is what the player sees when they look at the quest menu.

Please remember that the engine does not think, it reacts to the written cues, so the syntax MUST be exact. The first player statement gives the engine the quest name. The Menu allows the player to ask for the quest from the NPC.

Having the two "P:" and two "Menu:" on the same line informs the engine that the player has two different options. It is standard that the "P:" line is above the "Menu:" line and the "No." answer comes first.

These lines trigger the NPC response. In more elaborate quests the "Menu:" line may have variations on the No. or Yes. response. However remember KISS (Keep It Simple Stupid) is generally a good thing to keep in mind when you are beginning. You can have many options, but remember each "P:" must have a matching "Menu:" and they must be put in the same order

In order to include a free textfield, you will have to include a quotation mark after the menu. The <?> has to be followed by <=> and a text. This will produce a printout of the text and the user will be able to enter a free text. E.g. "Menu: ?=What shall Jardet do?" This will result in the text "What shall Jardet do?" being printed, followed by free form input.

P: *. P: rock pick.
Menu: ?=Please tell me your answer.
Smith: No, you didn't get the right answer.
Smith: Yes, it's a rock pick!.

P: Nothirstyinterst. P: Yesthirstyintrest.
Menu: No, sounds like work. Menu: Sure, I can get it for you.
Serana Tuvi: Alright. I will see you around then, stranger.
Serana Tuvi: Ah, good good.
<blockquote>'''Note:''' Remember the ": " after the P and Menu are important, as is the "." at the end of the line.

'''Note:''' For triggers used to start quests, never use NPC names into it, because this will confuse the engine, and the trigger will not be recognized.

'''Note:''' Every P: used in one step must be on the same line

'''Note:''' Every Menu: used in one step must be on the same line

'''Note:''' Every NPC: used in one step must be on different lines.</blockquote>

=== NPC Response ===
Aono Rikas: here you can add a response.

The line above is interpreted as an answer from the NPC and the engine will extract the name before the colon (:) + space as the NPC involved in this step of the quest. From now on, we will call this a response.

The full name of the NPC is required, just the first name will not work. If it is only one name e.g Harnquist use that, and if your NPC somehow ends up with three names use all of them.

In the first step of a quest the NPC statement will end in a question mark and is triggered by the first 2 lines. Responses are linked to each of the Triggers and Menus. So if you have two triggers you need two menu options and two NPC responses. All arranged in the same order.

=== Dialogues ===
The dialogues are the most important part of the quest for a player to get immersed. So let us talk about how to make the dialogue.

* Every punctuation, exclamation mark and question mark will create a short pause in the dialogue and create a new line.
* To create actions all you have to do is to use square brackets within the dialogue like this "Blablabla [NPC Name picks his nose] Bla bla blabla"
You may use also these commands:

* $playerrace can be used in an impersonal and a personal manner in terms of context, consider its usage carefully.

* $sir which gives you "Sir" or "Madam" or "Gemma" depending on the gender of the player's character. Again, this can be used to positive and negative effect. Be mindful of the NPCâ€™s tone. (Gemma is the honorific for Kran.)
* $playername clearly not to be used in newbie quests, have NPC establish rapport use this in second quest or even the third time a player works with a given NPC.

=== Quest Notes ===
Every step must have a quest note that goes into the player journal summarizing what he accomplished or learned in that step. Make sure to leave a hint of where to go next.

Example:
QuestNote You met Harnquist the local blacksmith.

== A sample quest script ==

=== The first step ===
As previously mentioned Step 1 does not exist, it is just the start of the quest, and can not be required by subsequent steps. The Start of the Quest will look something like the example at the beginning (Structure 1).

The same example can also be scripted like this:

'''Example: Structure 2'''
P: Short trigger.

Menu: Initial question, give me a quest.

NPC Name: Yes, I do have a quest for you. I need you to give Item of Importance to NPC2 Name.

P: Yes P: No.

Menu: Yes, I will do that. Menu: No way stupid.

NPC Name: This is the response from the NPC if answer is Yes.

Give 1 Item of Importance.

Assign Quest.

NPC Name: This is the response from the NPC if answer is No.

In Structure 2 the answers "No" and "Yes" are inverted, like the two "Menu:" commands, so it will give the same result as Structure 1. (Answer No: nothing happens. Answer Yes: the player will get 1Item of Importance and the Quest.)

Now, let us use a more detailed example. We will make a very simple quest: Aono wants to deliver a bottle of milk to Orchibaly. The player can choose the quest from Aono's quest menu. Orchibaly will then give the player 2 pies and a receipt to give back to Aono. The first step will be the step that assigns the quest. The P: tells the engine that this line represents something the player will say to the NPC, but what you must pay extra attention to is the "Menu:" This will be what the player will see as an option in the quest menu. If there are several options you will have to create one "P:" and a "Menu:" for each of them.

Here we firstly gives the player the option to ask for the quest. Then Aono describes the nature of the quest and the player can choose yes or no. Right after the "Menu:" line the NPC responsewill be put. In this example Aono will reply: "Well, I will get someone else to do it for me." if the player says no or "That's great. Here is the milk. Be sure not to spill it. TellOrchibaly I sent you.", give the player 1 Milk Bottle and assign the quest.

'''Example: Assign Quest'''
# Quest: Delivery for Aono Rikas

# Quest Description: Sample Quest.

# The rest of the header will not be covered here.

# Step 1 Aono Rikas in Hydlaa needs someone to deliver milk to Orchibally Gurpleferd in Ojaveda.

P: Delivery for Aono Rikas.

Menu: Are there any jobs you need done?

Aono Rikas: Well, yes. I need some milk delivered to Orchibaly in Ojaveda. Can you do this for me?

P: No. P: Yes.

Menu: No. Menu: Yes.

Aono Rikas: Well I will get someone else to do it for me.

Aono Rikas: That's great. Here is the milk. Be sure not to spill it. Tell Orchibaly I sent you.

Give 1 Milk Bottle.

Assign Quest.

A quest can be automatically assigned or there can be a step at the beginning of the quest to ask the player if he accepts it.

If you want to assign it automatically use this format:

P: give me a quest. Or any quest trigger.
Menu: what the play sees go here.
NPC: What the NPC says goes here.
Assign quest.

If you want to ask the player use this format:

P: give me a quest. Or any quest trigger.
Menu: what the play sees go here.
NPC: What the NPC says goes here, with the question if you want to help.
P: nohelp. P: yeshelp.
Menu: I don't want to. Menu: Yes I will help.
NPC: Fine... Go away.
NPC: Good great.
Assign quest.
<blockquote>'''Note:''' The “Assign quest.” command will only trigger after the second NPC: dialogue line is triggered, nothing happens if the first is triggered.</blockquote>

=== The next step ===
To separate the step we use "..." and then a comment on what step it is and what the step is about. If you don't want this step to be repeatable you will also have to add "NoRepeat" after the "...". The second step does not need a completion of Step 1, because Step 1 does not exist so to speak. The structure will be more or less the same as for the initial step.

Let us continue our Delivery for Aono Quest. We have assigned the quest and the player has been given 1 Milk Bottle to give to Orchibaly. Now the player must give that milk to Orchibaly. Either by using the give GUI or by using the quest menu. The first thing we have to do here is to set up the give trigger. If the player gives Orchibaly the milk, he will answer "Oh, yes the milk. Please give it to me. Now i need you to deliver these two pies and this receipt back toAono.", Give the player 2 pies and a Receipt from Orchibaly. The step is then completed.

In this example although the player is given two pies no "s" is added to the line. This is important, especially because most writers tend to add a plural automatically to plural items. Remember the engine does not. An item is designated in the singular, the engine always interprets it in the singular regardless of the number included. The numbers are again not spelt out and Arabic numerals used. Remember that each "Player gives"-command must have menu option in the next line.

'''Example: Step 2'''
... NoRepeat

# Step 2 - Player gives the milk to Orchibaly

Player gives Orchibaly Gurpleferd 1 Milk Bottle.

Menu: Aono asked me to give you this bottle of milk.

Orchibaly Gurpleferd: Thanks, please give it to me. Now deliver two pies and a receipt back to Aono.

Give 2 Pie. Give Receipt from Orchibaly.

Complete Delivery for Aono Rikas Step 2.

Completing a step

At the end of a step remember to insert the line:

"Complete Delivery for Aono Rikas Step 2."
<blockquote>
Note the use of Capitals, the use of the quest name, the use of the appropriate numeral and the period at the end of the sentence. The line marks the step as complete and allows the player and the quest to move forward.</blockquote>

=== Last step ===
To make sure the player has completed the previous step we start with "Require completion of delivery for Aono step 2.". Then we move on to the trigger which is the player giving 2 pies and the receipt to Aono. Aono answers "Ah, pie. Thank you. Please accept this for your time.", gives the player a pie and 100Tria. The step is closed and so is the quest with "Complete Delivery for Aono Rikas."

'''Example: Last Step'''
...NoRepeat.

# Step 3 - Player has now returned to Aono in Hydlaa. Player must now give Aono the 2 Pies and 1 Receipt.

Require completion of delivery for Aono step 2.

Player gives Aono Rikas 2 Pie, 1 Receipt.

Menu: Here are your pies and your receipt.

Aono Rikas: Ah, pie. Thank you. Please accept this for your time.

Give 100 Tria. Give 1 Pie.

Complete Delivery for Aono Rikas.
<blockquote>
'''NOTE:''' If you use multiple options in the last step of a quest you have to explicitly complete the quest with a command for the first option.</blockquote>
'''Example: Last step with multiple options'''

P: No. P: Yes.

Merchant: Quest doesn't complete automatically so make sure you have added a complete line for this response.

Complete Harnquist Needs Gold Step 2. Complete Harnquist Needs Gold.

Merchant: Quest completes automatically because it is the last line in quest so no complete line is required.

Complete Harnquist Needs Gold Step 2.

If you omit the Complete Step and Complete Quest line, the quest will not end properly when choosing "no".

=== Branches of a quest (Non exclusive) ===
Some times you want to have several different outcomes for a quest. Let us use the Delivery quest once again. If the first NPC says that you must NOT give the milk to some one else... specially NPC3. Then you should also add the option for the player to actually give the milk to NPC3 . This will complicate your script a bit, but is not as hard as it might seem. Most of the job is done by placing the right "Require completion of" and "Require no completion of" commands.

Let us take a look at that Delivery Quest again. Now we want to add an option for the player to give the milk to Reffitia instead. Reffitia will shake the milk until it becomes butter and this will make Orchibaly angry and demand a new bottle of milk. To do that we will have to add a few more steps and we will start from step 2 as step 1 will be the same as above.

The Third step will be our previous Step 2. And the last step will be the same. Though Aono should mention something like: "Make sure you don't give that milk toReffitia." in Step 1.<blockquote>
IMPORTANT NOTE: This is a non exclusive branching, meaning that the first branch is available also when executing the second one.

IMPORTANT NOTE: We will not add an additional step for the player to get milk again from Aono, but the player have to figure out another way to get hold of it (Buy from an NPC).</blockquote>

'''Example: Branching'''
... NoRepeat

# Step 2 - Alternative is to give the milk to refittia

Player gives 1 Milk Bottle to Reffitia

Menu: Here Reffitia, take this milk.

Reffitia Thamal: Ah! Orchibaly's milk. Here, now you can give the bottle to Orchibaly.

Give 1 Bottle of Butter.

Complete Delivery for Aono Rikas Step 2.

... NoRepeat

# Step 3 - Player gives bottle of butter to Orchy.
# The player then have to find another way of getting a bottle of milk (buy from NPC?)

Require completion of Delivery for Aono Rikas Step 2.

Player gives Orchibaly Gurpleferd 1 Bottle of Butter.

Menu: Um, here is the milk from Aono.

Orchibaly Gurpleferd: Milk? This is butter. You better get me another bottle of milk, fast!

Complete Delivery for Aono Rikas Step 3.

... NoRepeat

# Step 4 - Player gives the milk to Orchibaly

Player gives Orchibaly Gurpleferd 1 Milk Bottle.

Menu: Aono asked me to give you this milk.

Orchibaly Gurpleferd: Oh, yes the milk. Now i need you to deliver these two pies and this receipt back to Aono.

Give 2 Pies. Give Receipt from Orchibaly.

Complete Delivery for Aono Rikas Step 4.

... NoRepeat

# Step 5 - Player has now returned to Aono in Hydlaa. Player must now give Aono the 2 Pies and 1 Receipt.

Require completion of Delivery for Aono Rikas Step 4.

Player gives Aono Rikas 2 Pie, 1 Receipt.

Menu: Here take these pies and the receipt.

Aono Rikas: Ah, pie. Thank you. Please accept this for your time.

Give 100 Tria. Give 1 Pie.

Complete Delivery for Aono Rikas.

=== Alternative outcome ===
If we wanted the quest to have a different outcome if the player gives the milk to Reffitia than to Orchibaly we would need to get creative with the require commands. Let us say that if the player gives butter to Orchibaly he will give "bad pies" so when Aono receives them and takes a taste he will be very angry and no reward is given. To do this we will have to add just one more step. Let us start with step 3. Here we will have to change only the NPC response a bit to something like "Milk? This is butter. Have you been shaking the bottle all the way over here? This is completely useless to me, butter I have more than enough of. Any way someMenki came with another bottle just before you. Here takes these pies to Aono . Oh, and don't forget this receipt.". Step 4 will be the step where the player gives the bad pies to Aono, this step will complete the quest. Step 5 and 6 are the outcome if the player gives the milk directly toOrchibaly. Notice that Step 5 require a NO completion of Step 4. This is actually not necessary for this script, because the previous the other branch of the quest, ending in step 4 closes the quest it self.

'''Example: Alternative Outcome'''
# Step 3 - Player gives bottle of butter to Orchy. And receives 2 pies and a receipt

Require completion of Delivery for Aono Rikas Step 2.

Player gives Orchibaly Gurpleferd 1 Bottle of Butter.

Menu: Um, here is the milk from Aono.

Orchibaly Gurpleferd: Milk? This is butter. You better get me another bottle of milk, fast!

Give 2 Pie. Give 1 Receipt from Orchibaly.

Complete Delivery for Aono Rikas Step 3.

... NoRepeat

# Step 4 - Player gives the "bad" pies and the receipt to Aono. Receives gunk as reward and Quest is completed.

Require completion of Delivery for Aono Rikas Step 3

Player gives Orchibaly Gurpleferd 2 Pie, 1 Receipt from Orchibaly.

Menu: Here take these pies and the receipt.

Aono Rikas: Ah, pie. Thank you. [Aono takes a bite at the pie] You have tricked me!

Give 1 Gunk.

Complete Delivery for Aono Rikas Step 4.

Complete Delivery for Aono Rikas.

...
# Step 5 - Player gives the milk directly to Orchibaly.

Require no completion of Delivery for Aono Step 4.

Player gives Orchibaly Gurpleferd 1 Milk Bottle.

Menu: Aono asked me to give you this milk.

Orchibaly Gurpleferd: Oh, yes the milk. Now i need you to deliver these two pies and this receipt back to Aono.

Give 2 Pies. Give Receipt from Orchibaly.

Complete Delivery for Aono Rikas Step 5.

... NoRepeat

# Step 6 - Player has now returned to Aono in Hydlaa. Player must now give Aono the 2 Pies and 1 Receipt.

Require completion of Delivery for Aono Rikas Step 4.

Player gives Aono Rikas 2 Pie, 1 Receipt.

Menu: Here take these pies and the receipt.

Aono Rikas: Ah, pie. Thank you. Please accept this for your time.

Give 100 Tria. Give 1 Pie.

Complete Delivery for Aono Rikas.

=== Quest Timeout (Passing of time) ===

If you want to allow a certain part of the quest to wait a certain amount of time before it can be a executed, you can use this script:
Run script give_quest_timeout <<'Time until Harnquist is ready',6>>
this will create a temporary active magic with name 'Time until Harnquist is ready' which will last for 6 minutes.

Then in the prerequisite of the step have this:
# Step 12.
Require active magic Time until Harnquist is ready.
P: swordnotready.

Menu: Is Vresa's sword ready yet?

Harnquist: No, not yet.

...
# Step 13.
Require no active magic Time until Harnquist is ready.

P: about Vresa sword.

Menu: Is Vresa's sword ready?

Harnquist: Yes, Vresa's sword is done.

=== Important commands and expressions used ===

=== Assign Quest. ===
This line tells the engine to assign the quest to the player and generally results in the "YOU GOT A QUEST". and placing the quest in the player's quest log, under "uncompleted". Again remember to be exact here, Capitalize the two words and put a "." at the end. It cannot be emphasized enough that the engine only interprets what it sees and the way it sees it. If you are not precise the quest will NOT happen or in the cases of the next steps move forward.

=== ... ===
The three dots mark the beginning of a new step. Better, the three dots create a new step. So you need a "three dots" line before every "Complete Quest Name Step #"

=== NoRepeat. ===
This line means that the quest step cannot be done over and over. Note that there are three periods "..." a space and 'NoRepeat.' is one word not two. Each part of this sentence is required in exactly this form.

Basically "..." tells the engine that some time can pass before the next lines are used.

NoRepeat allows this quest step to be only done one time. This also applies to actions as seen in later steps. (in reality NoRepeat is a synonym for Require no completion of "this step")

=== Require completion of Quest Name Step #. ===
This command is like a closed door. To open it and enter in the current step the player needs to complete the step number #. You can also refer to a future step (for example, you're on step 4 and add "Require completion of Quest Name Step 8.")

=== Require no completion of Quest Name Step #. ===
This command is like an open door. The player is free to continue the quest and entering the current step, UNLESS he completed the step number #. Completing the step number # will close the door. Forever! You can also refer to a future step.

=== Complete Quest A Step. ===
You can complete one step in another one. But remember to insert one "..." line for every "Complete Quest Name Step #." line.
Complete Delivery for Aono Rikas Step 2.

=== Complete Quest Name. ===
This command will end the quest. After this the quest will be deleted from the uncompleted quest list and appear in the Completed quest list.
Complete Delivery for Aono Rikas.

=== P: ===
The trigger is actually a ghost from the previous scripting system, but it is still needed (for now). Before the player had to type the exact trigger stated after the "P:". Now they click the option from "Menu:". Triggers must be four words or less. Triggers must end with a period, no other punctuation is allowed (question marks especially are known to break aquest on the server).

If you want multiple phrases to activate the same trigger, you can just separate the phrases by a period; for example: "P: about guards. about hydlaa guards. about hydlaa militia." In this case the NPC's response will be fired on any of the three options. This technique can be used also when you have multiple choices: "P: one. two. P: more.". Both 'one' and 'two' will trigger the first response, while 'more' will trigger the second.

WARNING: Triggers cannot contain any of the following words: a, am, an, and, any, anything, are, do, I, is, isnâ€™t, please, that, the, this, to, too.

They also may not contain the name of the NPC you're talking to as that'll be stripped.

These words just take up space in a trigger as they are dropped by the engine when evaluating player response. To make the best use of your word counts ignore them when writing your triggers.Example: If you wanted the player to say 'please help Levrus' the trigger would become 'help' as please would be an ignored word and Levrus would confuse the server.

WARNING: If a player needs to write "NPC needs this" syntax it as "NPC wants this".

=== Menu: ===
After this command you can add the sentence said by the player in game. This sentence will appear on the screen and could be selected when one talks to the NPC.

Remember that for every menu line you need to create a response from the NPC.

=== Give ===
Give is a very useful command. It tells the engine to give the player items. Be it rewards or special items needed for the quest. When you reward a player, you can basically give items and/or experience. The syntax to award 1500 experience points would be: "Give 1500 Exp." Note that "Exp" is case-sensitive. You can also reward items AND experience, using this syntax: "Give Leather Gloves. Give 1500 Exp." Remember that you can only have two give commands on the same line, but you can have multiple lines, Remember to keep a clean style, it is prefered to only have one item per line.

'''Example: Give more than two items'''
Give 1 Leather Gloves.
Give 1500 Exp.
Give 1 Apple.

You can also add a number if you need to give more than one item (like you do for experience) example: "Give 5 Iron Ingot." It is not necessary in the case of one item to include the numeral, however it is good practice to do so as numerals tell the engine how many and should be written as a numeral, a word will NOT work as the engine cannot interpret it as such. Remember that all special items must be declared in the script header.

Another option you have is to give one item OR another. The following will pop up a window in which the player has to choose just one item:

'''Example: Give the player a choice between items'''
Give Cold or Arrow or Energy.
'''WARNING:''' At this time, don't use the following in an OR option: Tria, hexa, octa, circles, or items without a graphic. Also, for now, do NOT put quantities in front of items that are given using the "OR" parameter. An example of what NOT to do: "Give 1 Cold or 1 Arrow or 1 Energy." This will lock the server right up. An example of what SHOULD be done: "Give Cold or Arrow or Energy." (Check this statement if it is correct. --Katu)

=== Player gives NPC Name 1 Item ===
This can be used as a trigger (instead of the "P:"). It tells the engine to trigger the NPC dialogue when one or any fixed amount of a special item.

When a player have to give multiple items just add them to the original line using a comma:

'''Example Player gives item'''
Player gives Harnquist Water Pouch, 1 Pie.

'''WARNING:''' Item name rules must be followed at all times.

=== Item Name Rules ===

* Notice that the item name is "Iron Ingot", so "Iron Ingots" will not work, even if itâ€™s the correct plural form. Keep all names singular.
* Also, do not use a number (3, 14, etc) in the name of an item. An item called 3 Circles Receipt will probably generate problems when we script "Give 3 Circles Receipt." It is better named "Three Circles Receipt."
* Numbers should be spelled out everywhere unless you are referring to the quantity given or dealing with a trigger (give me 5 apples. give me five apples.) as both would be correct in a trigger.
* Character limit for an item name is 60 characters.
* Do not use an s' in an item name, like "Levrus' Left Shoe," use "Left Shoe of Levrus" or a similar substitute instead.

=== Set and unset a variable and Require a variable ===
You can set a variable to be later used by the quest or other quests. Variables are set on the character and visible from all quests.
Variables here are only boolean, so the only valid value is 1. The requirements only checks if the variable is set or not.

Use a prefix for all variables, so they don't get confused with other variables: "Quest_questname_variablename".
Smith: Here is your winch access
Setvariable Quest_Winch_Access 1

You can then require a variable to be set as prerequisite of a quest step.
Require variable Quest_Winch_Access.
P: access.
Menu: I have access
Bobaus: Ok, good.

If you want to unset a variable use the "Unsetvariable" command:
Unsetvariable Quest_Alchemy_Winch_Access.

=== Rewards at the end of the quest ===
When completing a quest, the player usually gets experience and money, or some items. In particular for experience and money you should use the following scripts. This allows us to split the rewards on a scale from 1 to 10 and then to tweak the actual values in the engine. The values in brackets indicate the complexity of the quest. The more complex the more rewards the player will get.

Run script give_quest_money <<3>>.
Run script give_quest_exp <<2>>.
You can also award faction points by using "give_quest_faction" , the number given is multiplied by 5 so if you want +5 point, you need 1 on the second parameter:
Run script give_quest_faction <<'Essential Trail', 1>>.
We have script also to push the faction point up to a given value, if you are already higher, this script will do nothing.
Run script give_quest_faction_level <<'Essential Trail', 2>>.

* value = 1-> max faction points = 10;
* value = 2-> max faction points = 20;
* value = 3-> max faction points = 35;
* value = 4-> max faction points = 55;
* value = 5-> max faction points = 75;
* value = 6-> max faction points = 100;
* value = 7-> max faction points = 125;
* value = 8-> max faction points = 150;
* value = 9-> max faction points = 200;

If you want to assign a faction title you can use this script. In the example it will assign the second title.
Run script give_quest_faction_title <<'Essential Trail', 2>>.

== The Quest Header ==
The header should contain a lot of information. All the information is commented out by a "#". The example below is from one of the mount quests.
First section is information about the quest itself. Name of the quest, a short description and category. Categories will be discussed in detail later on.

The next sections are for unique items used in the quest, name of the item followed by the description.

The third section is for recording versions of the script and all naming authors. Also who last edited the quest should be noted.

The last section is for additional metadata which will be added to the quest in the database (not part of the db) and will be used by the engine to determine lockouts and prerequisites. Here it locks all players from doing the quest again and locks all other players to take the quest with 60 seconds.

Lastly we tell the engine that the player have to complete the Ring of Familiar quest before this one. Note that these comments aren't taken by the engine; it's the duty of who loads the quest to fill the correct entries with the data found in the header: so it's just a way to keep all data together on the script.

'''Example: Header'''
# Quest name: Drifting for a Drifter
# Quest Description: Taemian wants to sell you a mount
# Quest Category: General
# ----------------------
# Quest Items: Item name/Item description
# Taemian's Pouch: - Pouch with all sorts of coins
# Green Gem of the Drifter - A magical gem with a green glow
# Unsigned Drifter Permit - A permit that still needs to be signed by Datal
# Signed Drifter Permit - A permit that has been signed by Datal
# ----------------------
# Variables used in this quest
# ----------------------
# Quest specific variables used in this quest
# ----------------------
# Author(s): Ravna, Katu, weltall
# Current Version: 1.01
# Player lockout: -1
# Quest lockout: 60
# Prerequisites: <nowiki><pre><completed quest="Ring of Familiar"/></pre></nowiki>
# Variables used: Quest_Variable_Name used to do.....
# ----------------------
# Version history and change log
# Last edited by: weltall
# Version 1.00: Initial draft - 05/01/2010 - Katu.
# Version 1.01: Added extra steps - 1/22/2011 - Venalan.
# ----------------------

==== Quest Lockouts ====
Each quest has two different lockout types:

* Player lockout: When this parameter is set, the engine will wait the specified amount of seconds before allowing the same player to redo the same quest. If you want a quest to be available to each player only one time, then set the lockout to -1. Setting it to 600 will have the engine wait 10 minutes before unlocking the quest again.
* Quest lockout: When this parameter is set, the engine will wait the specified amount of seconds before reactivating the quest for ALL players. This means no one can start the same quest during this period, but the ones that had it already active can complete it.

Usually we want quests to be unique to players, so most have a player lockout -1, except the very simple ones. Try always to think if itâ€™s meaningful for that player to redo it. (For example, Harnquist can require iron ore more than once, but won't need to teach you how to make a sword more than once.)

=== Prerequisites ===
'''Example: Prerequisites'''

A sample of the coding used to set prerequisites for a quest (All on one line):
<nowiki><pre><and></nowiki>
<completed quest="Test Quest One"/>
<completed quest="Test Quest Two"/>
<completed quest="Test Quest Three"/>
<assigned quest="Test Quest Four"/>
<not><completed quest="Delivery for Aono Riskas"/></not>
<not><completed quest="Gorbiak Disease"/></not>
</and><nowiki></pre></nowiki>

This sample requires that the player have completed Test Quests 1 through 3, have Test Quest 4 assigned (not completed) and have NOT completed Fancy Dancing and High-Class Aspirations. To get these arranged correctly can take some practice if one is not familiar with working with booleans, so it is best to include a plain-English comments of what you wish your pre-requisites to be in addition to the one with the "pre" coding statements.

== Requirements and Prerequisites ==
You can have as many requirements as you wish for a step, but again we remind you to keep it as simple as possible, so thing thoroughly through your choices here.

=== Multiple Requirements with OR ===
You can have an "or" statement between requirements by using "|":
Require Completion of Quest Winch Access | Completion of Harnquist is Hungry.
This needs all to be on one line.

=== Require Compendium ===
You can require the player to have a certain knowledge in the Compendium.
Require compendium creature StoneHammer.
P: comps
Menu: I know everything about the StoneHammers!
Fighter3: WOW
...
Require no compendium creature StoneHammer.
P: nocomps
Menu: Sorry I dont know anything about StoneHammers!
Fighter3: Ah, study more!
The syntax is: compendium <creature/plant/mineral> <name>

Another more complex version of the prerequisites is the: REQUIRE MIN <number>: this tells the engine that there are specific requirements to be fulfilled before the player is able to get the quest. This script indicated it requires a minimum number of quests to be completed in a given list.

=== Require min and Require Category Min ===
Example:
require min 2 of Quest1, Quest2, Quest3.
To match this prerequisite the player can complete Quest1 and Quest3 or 2 and 3, or all 3. The request is minimum 2 in the given list.

CATEGORY MIN <number>: quests have an attribute called "category", we use it to identify the difficulty of quests, but can be used of any other purpose, for example one can say that a group of quests is "Evil" or "Laanx related" or " Newbie". Just one category is allowed per quest. This prerequisite allows you to specify the category and the minimum number of quests completed in that category.

=== Require Time of Day ===
Requires the time of day to be at a specific point. The in game time has 24 hours.

Example:
Require time of day 1-2.
This example will trigger when the game time is between 1 and 2.

=== Require Active Magic ===
Checks if the player character has active magic.
Require active magic Weakness.

=== Require Race ===
"race" (working)
Require not race Klyros. Require race Kran.

=== Require Gender ===
"gender" (working)
Require gender female.

=== Require Possessed ===
Checking if the player character possesses an item/ has it in their inventory:
Require possessed item Ruby Crystal.
You can also check the amount of items as well as the quality of the items:
Require Possessed amount 3 200-300 item Steel Falchion.
it works also with money, as we handle this specifically. It will convert any currency, and check player total money for it.
Require no possessed amount 500 item Tria.

=== Require Skill ===
Require skill <buffed> name <skillmin>-<skillmax>.

=== Require Variable ===
Require variable Quest_Winch_Access.

=== Require Trait ===
Check if the player character has certain traits.
Require trait Black in HAIR_COLOR.
The different traits are: "NONE","FACE","HAIR_STYLE","BEARD_STYLE","HAIR_COLOR","SKIN_TONE","ITEM", "EYE_COLOR"

=== Require Guild ===
Unknown if this works.

=== Require Known Spell ===
Check if the character knows a spell.
Require known spell Nature Intuition.

=== Require Equipped ===
Checks if the player has a certain item equipped.
Require equipped category Armor - Helms.

Require no equipped category Armor - Helms.

Require equipped item Sword Handle.

Require not equipped item Sword Handle.

=== Require Married ===
This is untested and unknown if it works.

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

* The quest documents you submit should always be in notepad format: this is to avoid special characters added by Word or other text editors, most notably "smart quotes" which will appear as squares in game. Notepad++ is recommended, HIGHLY recommended.
* Use only ANSI encoding.
* The file name when saving the quest should begin with 'Quest' , then have the name of the quest. For example: Quest Hinoserri Cannot See.txt
* Titles of quests should follow some scheme of capitalization. There are many sets of rules, but a quick and easy format is to capitalize the first word and then all other words, except a, an, the, at, by, for, in, of, on, to, up, and, as, but, it, or, and nor.
* Each quest script begins with the title and a one or two sentence description; this is what the player reads so keep that in mind. The proper way to do this is to "comment out" your description and quest title, this is done by beginning a line with the number sign or pound symbol (#). Also, any quest item created for your quest should have a description written into the quest. Notes on quest items should also be commented out. Lastly, there should also be a "Quest Category" line that must be commented out as well. Approved quest categories are: Alchemy, Black Flame, Chain (don't use this one unless told), Cooking, Death Realm, Easy, Gugrontid, Magic Ways, Medium, Metal Working, Newbie, Repeatable. This is a work in progress, so if you have any questions ask an associate dev or developer. No quest can have more than one category - pick one and ONLY one. New quest categories must be approved by the associate devs/devs before use.

Technical Questions

2026-06-04T06:43:38Z

Katu: Tagged as outdated

{{Outdated|The info here is severely outdated. Remove old info and see if there is anything left to keep, merge that with other FAQ doc.}}
===The game is crashing every now and then, what should I do?===
Try disabling sound from PlaneShift Setup application.

===Where I can report critical bugs, or submit ideas, wishes or future requests?===
Submit them to the {{Bugtracker}}. Make sure to search for duplicate bugs on the new and the old trackers
to [http://www.hydlaa.com/bugtracker/query.php?op=query&form=advanced "Query Bugs"] on the old tracker "Go to the Advanced Query Page" and make sure that your request isn't already submitted.
===The server goes link dead, what should I do?===
The developers are fixing bugs so they have to restart it from time to time. It should be up in within few minutes after restart.

===Where to get my lost password?===
You can have your password reset by using the last link on http://www.planeshift.it/account/change-password

===Client tells me it's old. I just downloaded it?===
After downloading the full binary, use the PlaneShift Updater program to check if there are new updates available. You can find the Updater in the PlaneShift Program group (on Windows: Start>Plane Shift>Updater). It will update your client to the latest version.

===I can't type the @ for my username in the game!===
For those using AZERTY keyboards who are unable to type the @ character, try Alt + Ctrl + 2. If it fails, go to the PlaneShift directory and open 'planeshift.cfg'. Edit the line that looks like "Planeshift.Connection.User = m_y@email.blah" to include your email address.

===The Game is not displaying, black screens or video driver crashes, what to do?===
Try turning off Vertex Buffer Objects in the PlaneShift Setup application.

===The PlaneShift Updater crashes when trying to update, what's this?===
Try running the PlaneShift Updater(Recover Mode) icon if you are on Windows, otherwise run the Updater in non-GUI mode; with the -auto command line option.

===How can I become a member of the PS Team?===
First go to http://www.planeshift.it/Join%20Us. Choose a certain department that you would most like to and be able to help out in. If you wish to apply fill out an application [http://laanx.fragnetics.com/nexus/newapplicant.php here] You must submit a sort of portfolio and a resume.

===What does a W.T.B. member mean?===
It means Want To Be member. You become a WTB after passing a first test to prove your skills and after contributing some good assets. After a period of dedication and contribution to the PS Team, the WTB can become Official members at discretion of the leader of that department.

===If you are a Public Relations Member, what are you?===
A Public Relations Member means that you advertise the site and other things about PlaneShift and you get information out and get everyone excited about Plane Shift. It includes dealing with press, writing short informative articles, giving news to the community.

===Another player is verbally abusing me, what can I do?===
Use the /petition <what you are petitioning here> command to request a GM to deal with that person. In the meantime, use the /ignore <name> command to block the person from contacting you.

===Can I use the art for my game?===
No you can not use it sorry. You need to make your own art for your own game.
[[Category: FAQ]]

Category:Outdated

2026-06-04T06:39:29Z

Katu: Created page with "This category holds documents that need an update."

This category holds documents that need an update.

Gameplay FAQ

2026-06-04T06:38:20Z

Katu: Tagged as outdated

{{Outdated|There is considerable info that need an update in this doc.}}
This is the Gameplay FAQ

=Navigation=
===How do I move and look around?===
The arrow keys on the keyboard control movement and the direction you are facing. Hold down the forward and backward keys to move at a walking pace. Simultaneously holding down the Shift key and the arrow key will change you to a running pace. If there is an obstacle that you cannot go around, you may try running up to it and then pressing Spacebar to jump. With practice you can vault over obstacles.

===How do I change camera angles?===
The "Page Up" and "Page Down" keys control the camera angle. You can also press the M key to change the camera angle until you find one you like.

=Location Questions=
===Where are the sewers?===
Go left from the [[Smithy|blacksmith]] in [[Hydlaa]] and follow the city walls until you find a large hole in the ground. There is also a second entrance behind the [[Kada-El Tavern|tavern]].

===Where is the tavern?===
Starting from Hydlaa Plaza, look to the left of the large red temple for a ramp/street in the direction of the taller brown tower. Take that street and then go up the first staircase on your left. Follow its curve, and you'll see the tavern on your left eventually. Can't miss the sign of mugs above Kada-El's doors.

===Where is the town of Ojaveda?===
Exit Hydlaa from the [[East Gate]], in the same sector as Jayose's [[library]], and follow the [[Ojaveda Road]], through the Korogan Passage, the river and past the hill. It's a long walk, but eventually you will find the [[Dsar of Akkaio]], one of many dsars that make up [[Ojaveda]] city.

===Where is the Magic Shop?===
Exit Hydlaa from the north gate - from the centre plaza with the [[Laanx]] Statue, look toward a tall brown tower and make your way towards it. After exiting through the gate, continue through the forest path and then take the right fork as soon as you see it.

===Where are the Bronze Doors?===
Exit Hydlaa the same way, but take the left fork instead of the right. The way is long. Just follow the road.

===Where is Gugrontid?===
[[Gugrontid]] is the home city for the [[Kran]]. To find it you need to head out in the same direction as for the [[Bronze Doors]]. This time in the first map you get to head over the hills to your left and you will find a path to it in the edge of the map. You can also go down the right hand side of the Laanx (red/iron) [[Iron_Temple|temple]] and find the [[Pterosaur|pterosaur]] handler and pay to fly there.

===Where is Amdeneir?===
[[Amdeneir]] is the home city for [[Klyros]]. The only way currently to get there is to head to the pterosaur trainer to the right of the red Iron Temple of Laanx and fly there.

=Death Realm Questions=

===What happens when I die?===
There are two stages concerning what will happen to you when you die. First, if you are new to the game then when you die you will just find yourself moved to the main city.

Once you have been playing a while you will find when you die you are whisked away to the [[Death Realm]], where you must escape it to return to the realm of the living. The Death Realm is currently very small compared how it would be if it was real, but it will be expanded later.

===I can't find the exit from the Death Realm!===
Your best bet is to ask for aid from your fellow fallen. If they know of the exit, they will help you - and there is no shame at asking for help in a social game. If you can't seem to type fast enough while they're running by, you may wish to consider following them.

You can always type '/die' to be taken back to the beginning if you get thoroughly lost, or stuck (and the /unstick command doesn't help).

=Character Questions=
===What significance do the the character background options chosen during character creation have?===
The background choices that you make will affect starting [[Players_Guide#Stats_and_Skills|stats]] and [[Players_Guide/Skills|skills]] of the character. Also, the text of your selections will appear in your characters description, which you can edit after character creation. The different races' abilities have not yet been implemented. One tip would be to set your background so that it reflects the character's [[:Category:Races|race]] 's background. There is no effect on anything you can or can't do based on any choices you make.

===What are each of the religions choices about, and do they have any gameplay significance?===
Lookouts on this front are unclear. Estimates have been told. Religion will probably have a much bigger impact on gameplay then today.

===What is my character's experience level?===
PlaneShift does not have an overall experience level of a character, like some other games. However, you can estimate your character's strength by taking into account things like stats, armour skill, and primary weapon skill.

=Training Questions=
===What do I train?===
There are two aspects to skills which are theoretical knowledge and practical knowledge. You use progression points to train and obtain theoretical knowledge from a trainer NPC. Once you have obtained the theoretical knowledge to use the skill properly, you can then train your practical knowledge by actually using the skill.

===What are progression points, how do I get them and how do I use them?===
Progression Points (PPs) are the points you get from using skills (such as fighting, mining, crafting etc.). They are used along with money to pay for training, the theoretical part of skills with NPC trainers or to train statistics like Strength, Agility, etc.

===Yeah, but HOW do I train?===
You must first find a trainer that can train you in the theoretical knowledge of the skill. Trainers may be located in different locations in different cities. A big hint that an NPC has the ability to train you is the presence of the training icon when you click on the NPC to interact with him.

After finding the trainer that can train the skill(s) you wish to gain or improve, select him or her and type "/train". Then select the skill you want to train and click on the "Buy Skill level" icon.

You have to train until the yellow bar turns green completely. This part of training uses the progression points. To finish acquiring the skill at that level, you go out and complete the practical training by using the skill. When you have gotten enough additional experience using that skill, the skill will be leveled up.

===How do you increase HP or Mana?===
Training the physical stats (strength, endurance, and agility) and the skill 'body development' will increase max HP. Training the mental stats (intelligence, will, and charisma) will increase mana.

=Inventory Questions=
===What can I do with animal parts (that aren't used in a quest)?===
There are many things to do with animalparts these days. Initily, animal parts can be sold for tria to specific NPCs ingame. You should ask people (best in RP-manner) where to find them. They can also be used in armour making (hides), cooking (things like meat), alchemy (things like teeth and claws). You can also sell the items to players directly who can yes then for crafting.

===Where can I find weapons?===
Daggers, swords, axes, hammers, maces, knives, and bows can be collected as loot off of an occasional ruffian if you kill and loot the right ones crafted. Many but not all weapons can be crafted and asking crafters about what they make is a good place to find some good weapons. Maces and hammers can be bought from some merchants but are not always easy to find. The remaining weapon types do not yet exist in the game.

===How strong do I need to be to use heavier equipment?===
The strength requirement depends on the specific piece of equipment. Certain armour and weapon types have a specific requirement before you can use the item. Many magical blades have stat requirements before you can hold them as well.

===How do I use an item?===
Either type the command, "/use ''nameofitem''", or drag the item onto the doll in the inventory window.

===How do I drop or destroy an item?===
An item can be dropped by clicking its icon to pick it up and then moving it to outside of the inventory window and clicking in the game world to drop it. There is no built in functionality to destroy an item, right now, although it can be accomplished by placing the item in a furnace, and waiting.

=Trading/Working/Crafting Questions=
===How can I make some money?===
[[Players_Guide#Economy|Trias]] are the currency of PlaneShift.
The usual source of income is hunting and crafting however, so find yourself some rats (Hydlaa's sewers and the warehouse of Akkaio have plenty) and hunt there for a while, selling their parts to merchants (NPC or player). Another choice is mining or harvesting, but you will need a pick or sickle or other suitible tool and some training provided by Harnquist at the [[Smithy|blacksmith]]'s to begin. You can also learn how to [[Players_Guide/Crafting|Craft]], you might be lucky to sell your crafted items to other players for more then you can to NPCs.

===How do I mine or harvest?===
Buy a pick sickle or other suitable tool, equip it in your right hand, find the right spot to mine and type "/dig" which will let you mine gold, silver, platinum, iron, coal, tin, zinc, copper, luminim, cinnabar, diamond, emerald, ruby, or sapphire. You can do the same with "/harvest", you can use this at any point in the game where to you see plants growing. Ask in-game for help in finding the right spots. If you explore and notice others successfully mining using a pick, make a note of that location for future use.

===What do I need in order to train a skill?===
First you need some Progression Points and [[Players_Guide#Economy|Trias]]. Second you need to find the trainer that can help you in the skill you want - ask around in-game for further help in finding them.

===How many progression points do I need to train 1 point in a certain skill or stat?===
Open your "Skills and stats" window and look at the desired skill you want to train. You'll notice there are 3 coloured bars on the right of the skill name. If the blue bar above is longer than the yellow bar, you have enough progression points to train a level. The amount of progression points and [[Players_Guide#Economy|Trias]] required for this action will increase though as you progress, so for a higher level in a certain skill, you will require more progression points and money.

=Quest Questions=
===Why will nobody tell me quest solutions?===
The quests are far more rewarding to complete yourself, rather than have people telling you the answers. This applies even more so during the early stages of CB, where there is little content to keep you occupied. The developers wish people to not post quest answers in the forums or on web sites - telling friends or guild-members privately, however, is generally okay. But think again before asking the solution to a quest. The greatest reward you can get from completing the quest is the satisfaction of solving it all by yourself.

There is also one other important benefit for most people - when you learn how to solve quests on your own, you will get better at it. Of course, this is true for many things in real life as well. Do not feel discouraged at having challenges.

===Talking to NPCs is confusing. How do I get a quest?===
Previous version of PlaneShift had free text triggers to starts quests where you were required to ask them something along the lines of 'give me a quest'. Nowadays all you need to do is approach an NPC, right click them and select the 'talk' button. When you do this if the NPC has any active quest options then things you can say to an NPC with appear on screen. There might be cases when a quest can be triggered but there are no menus available, in those cases you should read the 'NPC tab' in the chat window. When you see an NPC say something new it might well be because he/she/kra is trying to get your help for a quest.

===How do I find out if an NPC is a questgiver?===
Most NPCs in PlaneShift have quests. As we add new NPCs those will have fewer if any options but given enough time quests will be added. The best way to find out if an NPC has a quest for you is to trigger the 'talk' button and see if any options appear on screen. If they do, there is a quest you can start with that NPC.

===How do I complete a quest once I've brought an item to the questgiver?===
Giving items to NPCs is usually very easy. If you are asked to get "3 apples", or "two steel stocks and two sabres" then all you need to do is find the items some how, make them, buy them, get given them from other players. Then once you have the items you are asked to get you return to the NPC and click on the talk button again and quest options will appear on screen. There should be an option that says something like 'Here are your items' or '[You give X the items]', in either case you click that option and the items will be given to that NPC and the quest will continue.

As you continue to play PlaneShift you will collect items and may end up where you get a message 'you do not have the right amount of X' but you have the items in your inventory. When this happens it is because you either have to few in which case you need to get some more, or you have too many. When you have more of a specific type of item than the NPC wanted you have to right click them and select the 'give' option. Once you have opened that you can move the items from your inventory to the window and give them manually to the NPC.

There is one other case when you might get stuck. If an NPC wants two apples, and you have two apples but they are not 'stacked' which means you have one apple in one inventory slot and one apple in another slot. When this is the case the server is currently unable to take one apple and one apple, it can only take a stack of two apples. In this case you can either stack the apples and use the quest menu or you can give the apples to the NPC manually.

===What are quest notes?===
A recent addition to the PlaneShift quest system is the addition of 'automatic quest notes'. When you are in game select the quest window from the main tool bar and then select a quest you have open or closed. When you do this a list of notes will appear in the right hand window with information for most of the steps you have completed and should give you information on what you are suppose to do next. If you have been away from PlaneShift and don't remember what you have to do this is a great place to look for tips or reminders on where to go next.

===I know there is a quest, but I can't get it!===
This question often comes up. A player knows there is a quest given by a specific NPC but they can't get it. There are a few things to think about when answering this question. Many PlaneShift quests are in 'chains' so you have to do a series of quests in order. So this means that if there is a quest you can't get then then it is likely that there are quests before it in the chain you need to do. There are two other conditions, one, that you don't have a skill requirement needed. Many crafting quests be it for cooking or armor making require you to have a minimum skill level before starting the quest. This is generally because the crafting book you get in that quest has a minimum requirement to use, so the quest matches it. The second possibility is that you need to have a specific item in your inventory, there are very very few quests that use this, but its something to be aware of.

===How do I get steel stock?===
This question comes up because it is possible to get a quest requiring steel stock as a new player, but a new player is nowhere near ready to make steel stock. The short answer is that you either get steel stock from another player, or you craft it yourself. In order to craft steel stock, you must be able to dig ore (mining skill), and make steel stock from it (metallurgy skill).

=Colors and GUI Questions=
===What do the label colors mean?===
{| cellpadding="2" cellspacing="1" border="0"
| style="background:#404040; color:#4080ff" | '''Blue''' || style="background:#efefef" | normal players in the same group
|-
| style="background:#404040; color:#00ffff" | '''Cyan''' || style="background:#efefef" | computer controlled characters (NPCs)
|-
| style="background:#404040; color:#80ff80" | '''Light Green''' || style="background:#efefef" | normal players
|-
| style="background:#404040; color:#00cf00" | '''Green''' || style="background:#efefef" | new GMs and certain testing characters
|-
| style="background:#404040; color:#ffff00" | '''Yellow''' || style="background:#efefef" | Game Masters
|-
| style="background:#404040; color:#ff8080" | '''Light Red''' || style="background:#efefef" | Developers
|-
| style="background:#404040; color:#ff0000" | '''Red''' || style="background:#efefef" | items and dead characters
|}
The colours separate different type of characters like NPCs, GMs, Players, ..

===What do the yellow, green, red, and blue bars near the skills mean?===
{| style="background-color:#efefef;" | border="0" cellpadding="2" cellspacing="0"
| '''Skill Bar''' ||
{| style="width:160px" border="0" cellpadding="0" cellspacing="0"
| colspan="3" style="background-color:#4040ff; height:5px; width:120px" | || style="background-color:#ff4040; width:40px" |
|-
| style="background-color:#00ff00; height:10px; width:40px" | || style="background-color:#ffff00; width:40px" | || style="background-color:#ff4040; width:40px" | || style="background-color:#ff4040; width:40px" |
|}
|}
:*;Yellow
:: Amount of theoretical knowledge (training) needed before you start the practical part (working with that skill).
:*;Green
:: Amount of theoretical knowledge achieved (when training) or amount of practical experience (when practising)
:*;Red
:: Amount of practical experience required up to next level
:*;Blue
:: Your current progression points. (If the blue bar is longer than the yellow bar, you can complete the theoretical training for the skill in question.)

===What do the coloured bars in my status window represent?===
{| style="background:#404040; color:#ffffff" border="0" cellpadding="2" cellspacing="0"
|+ style="background:#404040; color:#ffffff" | '''Status Window'''
| align="right" | HP
|
{| width:160px; border="0" cellpadding="2" cellspacing="0"
| bgcolor="#ff0000" width="160px" height="7px"|
|}
| align="right" | 150/150
|
|-
| align="right" | Phys. Stamina
|
{| width:160px; border="0" cellpadding="2" cellspacing="0"
| bgcolor="#00ff00" width="160px" height="8px"|
|}
| align="left" | 500/500
|
|-
| align="right" | Mana
|
{| width:160px; border="0" cellpadding="2" cellspacing="0"
| bgcolor="#bf40ff" width="160px" height="8px"|
|}
| align="left" | 10/10
|
|-
| align="right" | Ment. Stamina
|
{| width:160px; border="0" cellpadding="2" cellspacing="0"
| bgcolor="#B0B0B0" width="160px" height="8px"|
|}
| align="left" | 200/200
|}

:*;HP (red)
:: Health Points are associated with blood
:: This is an indicator of your Health and is a combination of Strength + Agility + Endurance
:*;Phys. Stamina (green)
:: Physical Stamina is associated with walking on earth
:: This is an indicator of your Endurance walking long distances
:*;Mana (violet)
:: Mana (from Hawaiian word for might) is associated with mysticism
:: This is the spellpower or amount of magical energy used to cast spells
:*;Ment. Stamina (grey)
:: Mental Stamina is associated with brain
:: This is an indicator of your Fitness of digging ore or fighting

=Targeting/Fighting Questions=
===There are too few monsters, and other people always kill them too fast!===
You'll have to be patient on this one. The developers will add more spawns soon, but for now, please try to not cause tension by stealing other people's kills if they got to it first, unless necessary by RP. If a monster is "camped" by somebody and you can't find any other free monster to kill, you can always approach the person and ask him/her politely to group with you so you can share the loot and progression points. Please use /tell to clear up any misunderstandings.

===In which hand should I put my weapon?===
It doesn't matter in which hand you are holding the weapons. You will hit with both hands as long as you have fighting items equipped (that includes fists). If you equip a non fighting/defensive item (mug/shield) you will only hit with one hand. The only thing you MUST equip in the proper (Right) hand is the rock pick. Equip it on the Left and you can't mine.

===Does having two weapons help?===
Yes, you hit with both hands so it helps. However, the offense does come at the cost of not being able to use a shield. Shield use is a defensive combat skill that some may prefer at the cost of the offensive use of two weapons.

===Why am I getting the message "'''''<<NPC name>>''''' is impervious to attack" when I try to attack a monster?===
If you are getting this message that means that the program controlling the NPC's behaviour (npcclient) has either crashed or it has been shut down by a developer in order to improve/fix something. Nobody knows when the program will be restarted, so don't ask.

===Why isn't my NPC opponent attacking back?===
The program controlling NPC behaviour (npcclient) on the server isn't always functioning (see the question above about "impervious to attack"). Without it, NPCs will not fight back. Consider this a freebie, until it comes back on, again.

===How do I loot a defeated foe? I can't find the place to click anywhere on the body.===
For some of the NPC models, the place to click is a very small spot, usually located around the crotch. In such cases, it is more effective to loot by using the "/loot" command.

=Miscellaneous=

===How do I recognize a GM?===
'''GMs''' and developers are in the [[Game Master|Game Masters]] Guild. You can use the command "/who game" to list the ones online for you.
See also [[#What do the label colours mean?|What do the label colours mean?]]

===How can I avoid fall damage?===
As a young character, it is all too easy to die through fall damage. The general advice is this: don't jump from objects, don't run down staircases, and take care when travelling across dangerous paths where it may be easy to slip. Sometimes bugs do occur and your character will plummet to his or her doom from a height that looks no more than four feet - unfortunate, but try to be as safe as you can. Also, because of certain graphics bugs, your character can fall through the floor to the end of the world. Try to avoid the spots that can trigger this event and find some alternative routes.

If your camera angle doesn't let you see something clearly such as the edge of a pit or where steps going down or up are, press "Page Up" or "Page Down" keys to adjust the camera angle to your liking.

===Y DOES EVRY1 H8TE ME!??===
Stop shouting at them! Using capslock and chatspeak all the time makes you sound loud, rude, and immature. It's also an eyesore, and not roleplay-compliant, so please type normally.

===How do I open doors?===
Most doors that appear shut cannot be opened.

There are a very few exceptions and these can only be opened when your character has completed a quest or group of quests. You can attempt to open a door by right clicking on it. If you are able to open it, you will see a door handle in the context menu. Click on that and you will be taken to the far side of the door.

===My map is too dark! I can't see where I'm going.===
If adjusting the brightness/gamma settings of your monitor doesn't work, try running the game with the -fullbright command. It will eliminate lighting completely (and thus be warned: the game won't appear as pretty and you won't be able to tell night from day). Right-click on your PlaneShift shortcut, hit Properties, find the Target line and add a space and -fullbright at the very end.

===How do I create a macro?===
Right-click on one of the free slots in the macro list (which is found down the left side of your screen by default - it already has buttons like Attack, Sell, Tell, Say, etc.) and click the button. You can then set the name for the macro, and then the chat command you wish it to type when the button is pressed. You can also queue 2 or more commands (i.e for creating an attack shortcut you can use the following combo: /target clear, /target next npc, /attack <<1-5>> placing each command on a new row and without the <<>> signs).

===I'm stuck in a place I can't get out from and I can't move!===
Type "/unstick" - that will move you to a safe spot.

===How do I get magic?===
You will need to buy a glyph from the magic shop or get one from a quest, purify it, and learn the spell. You will also need to find a trainer that teaches the magic Way (or school) your spell is in.

===How can I buy a house?===
Player-owned buildings are very rare at the moment.

So far only a few houses have been sold as "Guild houses". These sales were by auction and were advertised, in advance, on the main PS web site.

There is no feature that allows a player to simply buy a house from an NPC or a shop yet.

===What does "roleplay" mean?===
PlaneShift is a Massive Multiplayer Online Role Playing Game (M.M.O.R.P.G). That means that your character lives in a virtual world, has a background story and interacts with other characters. Role playing means that you adjust your chat in concordance with the setting of the game, with your character's background and with the other characters you meet ingame. Talking out of character (ooc) is prohibited in the normal chat but you can act ooc when whispering to another player using the command "/tell". The background story of your character is decided by you and, as long as it fits in the setting of the game, there is no limit to it but your imagination.

===I can't see certain players or NPCs===
That is caused by the fact that you lagged when entering a sector of the map. Changing sector and returning or reloading the client will help you.

===Is there a way to make the client load the new regions faster?===
Yes, checking the "Keep maps loaded" option in pssetup will help because if you already loaded a certain map you won't have to load it again when you return there. However, this will take a good amount of memory.

===I read the Player Guide and the Gameplay FAQ, but I still need help in-game===
Use the help channel (the tab on the right in your communications window). An advisor will answer your question.

===I don't like my character creation choices, will you change my gender/race/etc?===
The choices you have made for your character during the creation process are final; you can change them only by remaking your entire character. No developer or Game Master will make such changes for you.

===How do you play Groffeltoe?===
TODO

===What are those things that people can summon as pets?===
There are two kinds of pets, right now. The one with the tiny wings is called a groffel. The other one, that looks somewhat like a brownish lizard, is called a yulbar.

[[Category:FAQ]]

General Questions

2026-06-04T06:34:38Z

Katu: Tagged with Outdated

{{Outdated|There is some info here that needs an update.}}

===Why have all the crystals gone?===
There are no crystals in the Steel Blue release like in the previous Molecular Blue release. The new currency is now Tria. Anyway you may still find Emeralds and Crystals down in the [[Laanx Dungeon]].

===Can I gain experience other than by fighting?===
Yes, experience points are also awarded when you mine minerals and complete quests.

===Can I buy a house?===
Yes. There are now guild houses.

===What's a GM?===
GMs are Game Masters, they have special powers depending on their rank that they use to keep peace and help people in PlaneShift.

===Can I be a GM?===
GMs are picked by developers for being useful advisers. When you become a knowledgeable and experienced player, you can become an advisor using /advisormode on command. Then use /advice player_name to answer problems and earn advisor points. Don't look forward to being a GM until you worked a long time and regularly as an Advisor in the help channel.

===How can I avoid fall damage?===
Don't run down staircases, don't jump from high places and be careful when travelling dangerous paths where it may be easy to slip.

===How do I open doors?===
Doors that are shut cannot currently be opened.

===How can I make money?===
Money can be gained from looting dead monsters and selling what you find, mining ore, completing quests or selling the proceeds of your crafting.

===How do I crouch?===
The default key to crouch is [''Right-Shift'']. Hold down to make your character creep slowly while moving.

===Why do I always die if I go into the well in the temple; there used to be a dungeon there?===
The [[Laanx Dungeon]] still exists; however the fall from the temple well might be fatal depending on your Health and Armour. There is a secret entrance to the dungeon somewhere else in Hydlaa.

===Where are the sewers?===
There are two entrances to the [[Hydlaa Sewers|sewers]]. One is near the [[Kada-El Tavern|Tavern]]. You will have to find them yourself.

===What happens when I die?===
You are thrown away into the Death Realm, which you must escape in order to return back to normal world. Don't worry it's not hard.

===How can I change my hotkeys?===
You can change almost any hotkey from the Options Window.

===How can I create shortcuts (macros)?===
Right click on any button in the Shortcuts Window in game to change its name and assign commands to it.

===How can I create an account to play?===
The accounts in PlaneShift are free of charge. You can create an account with a valid email address at http://laanx.fragnetics.com/register/. See Section 1.5, “Creating An Account” for more information.

===Where can I mine?===
Minerals can usually be found at rocky outcrops. Exploring to find ore veins is part of the fun of PlaneShift!

===How do I mine?===
While standing on an appropriate dig site use /dig for mineral_to_dig command, e.g. for gold you'll use /dig for gold.

===Where can I buy weapons?===
You can buy them from Harnquist the smith in Hydlaa or the dwarf in first shop to the left in Ojaveda.

===Where can I buy mining tools?===
You can buy them from Harnquist the smith in Hydlaa.

===I am having no success mining, what's wrong?===
Be patient, everything is hard to begin with. Your success in mining depends on your skill and quality of pickaxe used. Try raising your mining skills or buy a more expensive pickaxe.

===Where's the new city called Ojaveda?===
You will need to find the Hydlaa gate and explore far, far from the city of Hydlaa to find Ojaveda.

===All players having same race look exactly same, is it possible to look different?===
Not At the moment. Character customization is currently not available in Steel Blue.

===Can only skills like sword, axe, etc. be bought or can you buy strength, endurance, will, etc.?===
You can also buy training for strength, endurance and other stats, you just have to find the right trainer.

===Are there Guilds in Plane Shift?===
Yes, everyone can create or join a guild in the game. You need to use the Guild Window.

===What are Guilds?===
Guilds are pretty much another name for clans. Characters with a good amount of (in-game) money and a number of followers can build a new guild. They can invite friends to be part of it, giving them titles. A guild is normally associated to a job in Yliakum society, like merchants, weapon smithy, etc. But a guild can be also created for other reasons, knowledge, defence, and politics.
[[Category: FAQ]]

PSwiki:Links

2026-06-03T11:30:21Z

Katu: Tagged Outdated

{{Outdated|Most of the links here are dead}}
== Official Sites==
===Planeshift main site===
*[http://www.planeshift.it/ The PS homepage]
*[http://planeshift.teamix.org/myplane/ MyPlane]

===Server===
* [http://planeshift.teamix.org/ Server Status]
* [http://planeshift.teamix.org/index.php?page=char_stats Players Online]
* [http://planeshift.teamix.org/register/ Forgot your password?]

===Forum===
* [http://www.hydlaaplaza.com/smf/ Hydlaa Plaza] (Official PS Forum)

===Development===
*{{bugtracker}}
*[http://planeshift.svn.sourceforge.net/viewvc/*checkout*/planeshift/trunk/docs/history.txt SVN history]
*[http://www.crystalspace3d.org/main/Main_Page The mainpage of Crystal Space], the graphics engine of PS
*[http://planeshift.svn.sourceforge.net/viewvc/*checkout*/planeshift/trunk/docs/compiling.html Compiling Guide]
*[http://62.173.168.9/nexus/ Nexus] (Dev Website)

== Unofficial ==
===Communities===
* [http://www.psde.de German PlaneShift Community]

=== Guilds ===
[[:Category:Guilds|Guilds in Planeshift]]
{{guildline|name=Bloodstone Brethren|site=http://www.guildportal.com/Guild/332879|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=32536.0}}
{{guildline|name=Brotherhood of Talad|site=http://bot.psde.de/}}
{{guildline|name=Daughters of Xiosia|site=http://daughtersofxiosia.info/|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=34498.0}}
{{guildline|name=Diamond Claw|site=http://diamondclaw.freeforums.org/ucp.php?i=pm&folder}}
{{guildline|name=Elemental Light|site=http://elementallight.org/|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=26262.0}}
{{guildline|name=Explorers|site=http://www.explorersguild.org/|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=28172.0}}
{{guildline|name=Gifts of the Dome|site=http://giftsofthedome.guildlaunch.com/|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=39682.0}}
{{guildline|name=House Cheshire|site=http://z10.invisionfree.com/PSHoC/index.php|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=36720.0}}
{{guildline|name=Klyros Junction|site=http://www.rienow.net/KlyrosJunction}}
{{guildline|name=Masters of Move}}
{{guildline|name=Opalescence|site=http://opalescence.spruz.com/|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=40467.0}}
{{guildline|name=Prophets of Chaos|site=http://poc.myfreeforum.org/}}
{{guildline|name=The Acrobats Family}}
{{guildline|name=The Adani Order|site=http://www.theorderps.myfreeforum.org/|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=38961.0}}
{{guildline|name=The Bounty Hunters|site=http://bountyhunters.zapto.org/|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=35569.0}}
{{guildline|name=The Dark Warmongers|site=http://darkwarmongers.forocatalan.com/}}
{{guildline|name=The Elite Reign|site=http://elitereign.myfreeforum.org/|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=40287.0}}
{{guildline|name=The One|site=http://psthe1guild.proboards.com/|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=40352.0}}
{{guildline|name=The Outlaws|site=http://www.theoutlaws.ath.cx/|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=34899.0}}
{{guildline|name=The Royal House of Purrty|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=23952.0}}
{{guildline|name=The Stillwater Peace Corps|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=40370.0}}
{{guildline|name=The Warriors|site=http://thewarriorsguild.org/|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=25520.0}}
{{guildline|name=The Way of the Hammer|site=http://inter-link.ath.cx/forum/index.php|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=24480.0}}
{{guildline|name=Wayward Kingdoms|site=http://waywardkingdoms.bigforumpro.com/}}
====Clans====
{{guildline|name=Kore Irka-kor Clan|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=35317.0}}
====Organisations====
{{guildline|name=The Dark Empire|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=15005.0}}
====Groups====
{{guildline|name=Guilds & Traders Journal|site=http://gtjeditor.hostei.com/|plaza=http://www.hydlaaplaza.com/smf/index.php?topic=38318.0}}
====Currently Offline====
These are either offline or haven't been updated in ages.
* [http://flare.slyip.com/ Felines Lair] (last update : 4th-Nov-'08)
* [http://knights.yliakum.de/ The Knights of the Crystal] ("Back online soon"/"In Kürze wieder Online!")

===Content/Mods===
* [http://psmods.stufftoread.com/ PS 3d Mods repro hosted by SourceForge]

General FAQ

2026-06-03T11:27:39Z

Katu: Tagged Outdated

{{Outdated|Much of the data is written pre Steel Blue and links are old}}
=Game=
==Where can I create an account to play?==

The accounts in PlaneShift are free of charge, you can create an account associated with a valid email address from the [http://www.planeshift.it/account/create registration] page.

==I forgot my password!==

You can reset your password by using the last link on the [http://http://www.planeshift.it/account/change-password password recovery] page.

==Client tells me it's old, I just downloaded it==

After downloading the full binary package and installing it, use the updater program to check if there are new updates available. You can find the updater in the PlaneShift Program group (on Windows: Start>PlaneShift>Updater). It will update your client to the latest version.

==Client tells me it's newer than server==

This may happen in rare cases where we performing certain types of maintenance on servers. You should wait a few hours and try again to connect.

==Client crashes or updater crashes on start-up==

If client crashes on start-up the best thing is to run the updater again.

If the updater crashes on start-up, try to open a command shell (on Windows select Start>Run, then type cmd or search Shell Prompt icon), then move to the directory where you have PS installed and type

<code>
updater --auto
</code>

This will start the updater is a non-graphical mode that is a bit more stable. If you still get errors, you can check the [http://forums.hydlaa.com forums] to see if there is an alternate updater available. To force a full update, you can delete the file version.dat which makes the updater download all the updates again. Alternatively, you can also try deleting the folder '''UpdaterTemp''' in your planeshift directory.

If nothing else here fixes your issues, as a last resort try completely uninstalling and reinstalling PlaneShift, then running the updater again.

==When will the next release of PlaneShift be made?==

The next minor release of PlaneShift is named Steel Blue. We will reach that release by adding pieces to the current public one, so you will get it piece by piece. The date by which we will reach all objectives set for Steel Blue is not available yet.

==How big is the client for the demo?==

To play the game, you will first need to download a client for your operating system (Windows, Linux, etc...). The client for the current tech demo is about 250 Megabytes. It will increase in size in subsequent releases. It contains an auto-update program that can download necessary new software when you start the game.

==Can you give us a release date for the final product?==

PlaneShift is a free and non-profit project, and so our release dates are difficult to define. We are now working for next minor release, but we cannot yet give you release date for the final product.

==How big is the client for the final release?==

We really don't know yet, but it may be as large as 500-800Mb. The size consist mainly of models and textures. The game may continue to expand beyond but that is years away!

==Which are the minimum hardware requirements to run the game?==

The hardware requirement are connected to our 3D engine, [[CrystalSpace]]. The engine is continuously evolving and so the requirements are not written in stone. A PIII 600Mhz with 512Mb of RAM and a Geforce 2 card is probably the minimum. The most important aspect is RAM at the moment, so if you have a very good machine, but 256Mb of RAM, PlaneShift will probably run badly.

For best results you need a PIII 1ghz with 512 RAM and a GeForce3 or equivalent card. More ram is recommended, especially if you want to keep many maps loaded to avoid having to zone.

In game there are settings to reduce visual quality and improve performances on lower machine. Check the options menu. Setting '''Adaptive Camera''' may help improve performance.

==Will PlaneShift run on Windows, Mac, Linux, etc...?==

We have tested PlaneShift under Windows (NT, 2000, XP), various Linux distributions and MacOS. We plan to keep these three platforms for now.

==Will there be regular updates? When is the next update?==

Yes! We continuously work on adding content. You can expect to see something new each month, but really depends on internal development plans, so we cannot guarantee a precise time.

==Where can I download the game?==

You can download our current demo release in the [http://www.planeshift.it/Download Download section].

==The game doesn't work properly on my machine, how do I report the "bug"?==

Go to the {{Bugtracker}} to submit a new bug. Read other reported bugs FIRST, to avoid submitting a duplicate. Also do a search of the [http://hydlaa.com/bugtracker old bug tracker] Be sure to fill the information provided below or your message will be discarded:

<pre>
Time of test:
OS:
Processor:
RAM:
Video Card:
Video Card Memory:
PS Client Version:
Description of the bug:
</pre>

Example:

<pre>
Time of test: 3 May, 12:00 AM EST
OS: Windows 98, First Edition
Processor: AMD Athlon 800 Mhz
RAM: 384 Mb
Video Card: Voodoo 3 3000
Video Card Memory: 16 Mb
PS Client Version: 0.3.005

Description of the bug: Title screen and menu screen are experiencing graphical glitches.
As soon as I move the mouse on a button is flickers.
</pre>

==How many player races will there be in PlaneShift?==

Twelve altogether.

Humans: Ylian

Dwarves: Stonehammers. (You can roleplay the Clans: Stonebreaker & Hammerwielder)

Elves: Nolthril & Dermorians

Other: Kran, Klyros, Enkidukai, Lemurs, Diaboli, & Ynnwns

Not all are available in game right now, but they will be added soon.

==Will there be more races, or are there only 12?==

The 12 specified are all of the players races. You will find a lot more amongst monsters and NPCs.

==What skills will there be in PlaneShift?==

Skills will include; Weapons, Armours, Stealth, Locksmithing, Martial Arts, Body development, and many more.

==Will there be Player vs. Player combat in PlaneShift?==

Yes, you can challenge someone to a duel and fight. One can use PvP mode anywhere, but it is customary to fight in stadiums and/or arenas.

==What will you do to prevent unwanted PvP?==

All PvP activity requires the approval in some fashion of both parties (setting which can be changed from the Options menu), whether it is stepping into an arena, agreeing to a duel, or participating in a guild war. If the other player doesn't agree and the first player attacks, guards and gods will stop that fight in such a way that attackers will be scared even to think to attack someone else.

==How large will the PlaneShift world be?==

There will be eight underground levels to explore. Each level is like a region, it has cities and dungeons. Beyond that our world will expand in the Stone Labyrinths and through portals you will reach different world/dimensions.

==What will be modifiable at Character creation?==

At character creation you can define basic stats (strength, agility, will, etc...), skills, advantages, jobs. Later on you will be able to define also the look of your character (Hair style, hair colour, skin colour, Body type (thin, built, heavy)

==The screenshots on the "Pics" page are of different quality, some really nice others not. Is that what the game will look like?==

The pictures posted on the screenshots sections do not represent the final look of the game. Those should be considered only as a reference of the current status of development.

==May I buy a house or castle in PlaneShift?==

If your character has a good amount of (in-game) money it can buy a house, a shop or even a castle. This feature will be added in future releases. You will be able to lock your house and store your items there.

==Will each city be different such as races/alignment/shops/items found there?==

Yes, each city will have a predominant race and a different architecture. You will find different economy, prices and items.

==What are guilds?==

Guilds are pretty much another name for clans. Characters with a good amount of (in-game) money and a number of followers can built a new guild. They can invite friends to be part of it, giving them titles. A guild is normally associated to a job in Yliakum society, like merchants, weaponsmithy, etc. But a guild can be also created for other reasons, knowledge, defence, politics.

==Will there be guilds in PlaneShift?==

Most definitely, there will also be special powers for associated with each guild. Everyone can create a guild right now in game, and start to search for members.

==What will be the benefit of owning/being in a guild?==

Besides being a focal point for cooperative activity, a guild will be able to have a building as a headquarters. Guilds have also social usefulness: there are nutrition guilds, cloth making guilds, artists guild, etc. You can also form cooperative alliances with other guilds. Individuals in a guild may also find it easier to find people to regularly meet with in fighting monsters.

==Does PlaneShift client contains any spyware or ads?==

Absolutely not. PlaneShift client does not read any personal info, does not pop up any ads and does not contain any spyware. The source code is open for anyone to see, so even if we wanted to do that, we could not hide anything. All the operations performed on your PC are clearly visible from the source code.

==Who is the overall "leader" of PlaneShift? Who ensures quality and progress of this project?==

Atomic Blue is led by the board of directors that includes Keith "Vengeance" Fulton, Andrew "acraig" Craig and Luca "Talad" Pancallo. The board of directors ensures quality and progress as well as it determines the direction of the development.
The project leader of PlaneShift is Luca Pancallo.

==How can I become a member of the PS Team?==

First go to the [http://www.planeshift.it/Join%20Us HELP US!] section. Choose a certain department that you would most like to and be able to help out in. E-mail the department leader asking to join. You must submit a sort of portfolio and a resume. You will get more information from the person you e-mailed after that.

==What does a W.T.B. Member mean?==

It means Want To Be Member. You become a WTB after passing a first test to prove your skills and after contributing some good asset. After a period of dedication and contribution to the PS Team, the WTB can become Official members at discretion of the leader of that department.

==If you are a PR Member, what are you?==

A Public Relations Member means that you advertise the site and other things about PlaneShift and you get information out and get everyone excited about PlaneShift. It includes dealing with press, writing short informative articles, giving news to the community.

==When connecting to the game, must my name be "role-playing style"?==

Yes, absolutely. We will not allow names like "1m C001" or "Sw33t Ch33ks" or any other non RPG-related name. We do encourage the Role-Playing side of the game in all its aspects.

==Are there in-game moderators to avoid bad behaviour, racism, sexism, harassment, etc. ?==

Yes, there are moderators, so called [[Game Master|Game Masters]] (GMs) who ensure safety and enjoyment of all players. We will not tolerate any bad behaviour.

==What happens if your character in game dies?==

After [[Death]] your character will travel in the Death Realm, and you should try to find a way out of it. This will bring you back to the world of the living.

=Forums=
==How do I access the official PlaneShift forums?==
The forums can be accessed via the PlaneShift community section here: [http://www.planeshift.it/Forum?utm_source=planeshift.top-ix.org/pswiki planeshift.it/Forum] . 
It contains the relevant info on the Community forums. 
 
Anyone may read the posts, but to post messages, you will need to register a forum account on the main forum page. 
'''Registration for forums is separate from registration of character accounts.''' 
''Note: The forums may also be accessed via clicking on the "Community" link, located on most of the [https://PlaneShift.it?utm_source=planeshift.top-ix.org/pswiki Planeshift.it] website pages.'' 

==What are the rules for the PlaneShift forums?==
The forum rules are located here [https://www.hydlaaplaza.com/PlaneShift/smf/index.php?topic=35709.0 hydlaaplaza.com/PlaneShift/smf/] 
(also linked on the [http://www.planeshift.it/Forum planeshift.it/Forum]. page) 

=Chat=
==What is the PlaneShift chat?==
For online chat about the game, we have an IRC ('''I'''nternet '''R'''elay '''C'''hat) channel (or "room") on the [http://www.freenode.net freenode] network. [[Freenode]] is a network created for opensource projects. To join the channel, you need to get an IRC client. There are many clients available, but reviewing each one is beyond the scope of this FAQ. For more information, see [http://freenode.net/using_the_network.shtml Using The Network] on the freenode website.

==How do I join the PlaneShift IRC channel?==
If you know how to use your client, here is the info you are looking for:
Server: irc.freenode.net
Channel: #planeshift
Port: 6667

If you use the popular and widely-used mIRC IRC client, you might be able to click on [irc://irc.freenote.net/planeshift irc://irc.freenote.net/planeshift] to automatically open your mIRC client to the #planeshift channel.

==What public PlaneShift-related channels are there?==
* #planeshift -- General Fan Channel
* #planeshift-build -- Help building the PlaneShift client
* #planeshift-gmtalk -- The point of contact for players needing GM assistance
* #planeshift-wiki -- Discussion about the PlaneShift wiki

= Archived information =
<div class="mw-collapsible mw-collapsed">
'''Archived content (outdated)'''
=MyPlane=
==What is MyPlane?==
A page where you can see information about your planeshift characters and their achievements.
==Where do I find MyPlane? ==
[http://planeshift.teamix.org/myplane MyPlane]
</div>

[[Category:FAQ]]

Template:Outdated

2026-06-03T09:36:04Z

Katu: Created the template for outdated documents. Takes on argument: Details.

{| align="center" style="border:#ff0000 5px solid; background:#ffff00;"
| align="center" | [[Image:07.png|left]]
| align="center" | This page has '''outdated information'''. 
'''Details''': {{{1|none given}}}
|}
<includeonly>[[Category:Outdated]]</includeonly>
<noinclude>[[Category:Administrative template]]</noinclude>

User:Katu

2026-06-03T07:29:57Z

Katu: Added department

Settings

PSUnreal Client logs and configs

2026-06-02T13:56:23Z

Katu: Added info on the Mac issue where chat log files were not saved due too a missing Folder.

=== Windows ===

Logs are located in %localappdata%\PSUnreal\Saved\Logs

Configs are located in %localappdata%\PSUnreal\Saved\Config\WindowsClient

Just copy the string above to your windows explorer address bar and %localappdata% will become a real path.

Musicalsheets are located in: %localappdata%\PSUnreal\Saved\musicalsheets

=== Linux ===

Logs are located in ~/.config/Epic/PSUnreal/Saved/Logs

Configs are located in .config/Epic/PSUnreal/Saved/Config/LinuxClient/

=== Mac ===

Logs are located in /Users / <user name> /Library/Logs/PSUnreal/PSUnreal.log

Configs are located in /Users / <user name> /Library/Preferences/PSUnreal/MacClient/

Saved games are in /Users/ <user name> /Library/Application Support/Epic/PSUnreal/Saved

'''On my Mac Mini:'''

* ./Library/Containers/com.YourCompany.PSUnrealClient/Data/Library/Application Support/Epic/PSUnreal/Saved/Config/MacClient/GameUserSettings.ini
* ./Library/Containers/com.YourCompany.PSUnrealClient/Data/Library/Logs/PSUnreal/PSUnreal.log

==== Issue with saving Logs on Mac ====
There is an issue where the game is unable to save the chat logs because the "Logs" folder is missing. One fix is to create the folder.
cd /Users/{yourusername}/Library/Containers/com.YourCompany.PSUnrealClient/Data/Library/Application_Support/Epic/PSUnreal/Saved/
You might find the folder at a totally different location. The best way is to use the Terminal app to find the right folders, as Finder can't see into the packages.
mkdir Logs
Now the logs will be saved in that folder.

=== Overriding a config ===

Override the scalability setting, you need to edit PSUnreal\Saved\Config\WindowsClient\Scalability.ini and add:
[PostProcessQuality@0]
r.RenderTargetPoolMin=100
then in the game setting panel you should use the "Low" for post-processing setting, which corresponds to "0"

Low = 0, Medium = 1, High = 2, Epic = 3

=== Overriding a log ===
You can override a log set by PlaneShift by adding the corresponding line to the file Engine.ini found in the configs directory.

In general as a PlaneShift player you should not be using any of this, but maybe useful in case a developer asks you to enable or disable some logs for testing.

Log settings should be inside a section defined with:
[Core.Log]