Stendhal Quest Coding - Part 2

• Play
  • Manual
  • Beginner's Guide
  • FAQ
  • Ask for Help
  • Events
  • Videos
  • Rules
  • Groups
• World
  • Atlas
  • Dungeons
  • NPCs
  • Levels
  • Creatures
  • Items
  • Quests
  • Games
  • History
  • Achievements
  • Houses
• GMs
  • Administration
  • How to be a GM
  • Scripts
  • Guide for admin
• Contribute
  • Chat
  • Bugs
  • Testing
  • Graphics
  • Sound
  • Item Ideas
  • Atlas
  • Creature Ideas
  • Quest Ideas
  • NPC Ideas
  • Events Ideas
  • Achievement Ideas
  • Open Tasks
• |
• Extend
  • How to add items
  • How to add Creatures
  • How to add quests
  • How to add NPCs
  • How to create maps
• Develop
  • CVS (Source Code)
  • Bugs
  • Meetings
  • Testing
  • Code Design
  • Jenkins
  • Ideas
  • Open Tasks
  • Patches
  • API Reference

• Build & Host
  • Building
  • IDEs
  • Hosting
• |
• Misc.
  • Third Party Projects

Stendhal Quests

• Contributor's Guide
• Existing Quests
• New Quest Ideas
• Coding Quests
• Testing Quests
• Quest Histories

This page is currently reworked. You can find the old content on the talk page

You may want to read the first part of the Stendhal Quest Coding tutorial first.

If you have ideas for new quests or are interested in helping to refine quest ideas, please have a look at the Quest Contributor's Guide or the Stendhal Quest Ideas.

Teaching the NPC to ask the players whether they will do the quest

Now we want Hayunn to ask the player whether he is going to help:

• quest: My mouth is dry, but I can't be seen to abandon this teaching room! Could you bring me some beer from the tavern?
  • yes: Thanks! I'll be right here, waiting. And guarding, of course.
  • no: Oh, well forget it then. I guess I'll just hope for it to start raining, and then stand with my mouth open.

As a little exercise you can code this part to check whether you understood the first part of this tutorial.

There is, however, a small problem with the current solution: There can only be one reply for "yes" and "no". So the NPC can only ask one single question in order to be able to process the answers.

Fortunately there is a solution: The NPCs needs to remember the state of the conversation:

Currently our NPC knows two states: IDLE for walking around and ATTENDING for talking to a player. You can change between states by talking to the NPC. So if the NPC is IDLE, it will accept "hi" and move on to the ATTENING state. If you say "hi" again, nothing will happen because "hi" is unknown in this state. The NPC, however, will now reply to "job" and "help". You can end the conversation with "bye" which will cause the NPC to return to IDLE (and start walking around again).

So, lets return to our example. We want the NPC to reply to "yes" and "no" but only after the quest question was asked. So we add a third state called QUEST_OFFERED. When the player says "quest", the NPC goes to that state. On "yes" or "no" it returns to ATTENDING.

You may have noticed in the above diagram that there is something called "ANY". This is a special "state" which allows the triggers associated with the outgoing arrows to be triggered in any state. You should not use this except for "bye" which should always work.

TODO:

• code
• point to ConverstationStates
• View Transitions with Graphviz

Teaching the NPC to remember the player

TODO:

• ChatAction
• ChatCondition

Rewarding the player

TODO:

• MultiAction

Quest Documentation

TODO:

• should be done much earlier usually
• content should be done earlier (see contributor's guide

Further Reading

TODO: