How to test NPC Parser

• 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

After you designed a new NPC conversation, you have to implement it in the server code and test if the NPC understands all user input like you planed.

You can launch it with the script runpte.sh or runbte.bat on windows. This will compile the server and tools part, then launch the java dialog It may be even easier to run it from Eclipse by launching the class games.stendhal.tools.npcparsertestenv.TestEnvDlg .

It displays how the parser interprets user input and gives a hint about not yet known words. You can choose one of the predefined example sentences or write your own text into the input field. The whole thing is meant to support developers to design their NPC conversations and test how the parser reacts on user input. One important thing is for example the trigger expression displayed in the right bottom field.

It says that buy 3,000 cookie matches buy 3 cookies yes this matches when using the standard mathing method the expressions match, the njumber is just an attribute. if you use exact mathcing, it does not match.

Currently the most important output field for developers may be the "trigger" field. Looking at this you can see which trigger expression is used in the state machine.