Author Topic: common dialog parser.  (Read 1065 times)

Prolix

  • Guest
common dialog parser.
« on: January 25, 2009, 07:33:40 pm »
It would be nice if the server had a parser which converted polite expressions into base meanings.
For instance "Please can i have" could be equated with "give me". With a number of such conversions there would be one lookup table that passes the appropriate flag to indicate a correct trigger response.

Having said that, if you are going to go with the tree menu dialog this is moot. If the current system is to be kept it would simplify things because scripts would not have to individually trap for specific sequences of words and interaction with the npcs would allow for more player characterization.

Caarrie

  • Forum Addict
  • *
  • Posts: 3369
  • We want no UNFIXED bugs!!!!!!!!!!!!!
    • View Profile
    • PlaneShift3dMods
Re: common dialog parser.
« Reply #1 on: January 25, 2009, 07:37:01 pm »
as far as i know ps already has a system like that ingame and they are working on a tree dialog system

Prolix

  • Guest
Re: common dialog parser.
« Reply #2 on: January 25, 2009, 07:46:48 pm »
I kind of thought so but it appears they never got too deep into developing their lookup table. Either that or their parser did not get much use or output a specific phrase instead of a meaningful token.

anyway I got stuck by needing to say "give me" and trying "can I have" or "I need" all of which could be serviced with the same token.

No big deal, my idea is worth every penny that was paid for it ;)

Caarrie

  • Forum Addict
  • *
  • Posts: 3369
  • We want no UNFIXED bugs!!!!!!!!!!!!!
    • View Profile
    • PlaneShift3dMods
Re: common dialog parser.
« Reply #3 on: January 25, 2009, 08:10:26 pm »
No big deal, my idea is worth every penny that was paid for it ;)

it sounds like you want settings to use more triggers in their quests more then anything ;)

Prolix

  • Guest
Re: common dialog parser.
« Reply #4 on: January 25, 2009, 08:33:23 pm »
It just seems to me that  triggers are set individually for each quest. if the quest is set up such that it is looking for a programmatic token instead of particular phrase then more things could produce that token. In the case above that token could be "require" so the quest would look for require + item, the parser would take any of the three inputs and output the require token.

Since they are working of the tree it is kind of moot though as I previously suggested.