before turn script - Axe Software Forums

  Axe Software Forums
  Quest Developer Forum
  before turn script

profile | register | faq

Author Topic:   before turn script

gamer1962 posted 17-06-2003 02:10 BST
Is there a way to stop quest from processing the original command in the "before turn game script"? I want to test for conditions and possibly not process the original command based on the answer.
Alex posted 17-06-2003 11:40 BST
You can't do that in a beforeturn script, but you could do it in at least two other ways:
1. Use an "enter" command (in QDK "Enter next command into string variable"), and then process the input accordingly. If the entered string isn't one you want to "catch", then use the "exec" ("Execute a command as if it were typed by the player") command to send the string to the normal command processor.
2. Set up a user-defined command. If you're feeling brave you could set up a catch-all command "#anything#" (or similar), then use "exec" with the "normal" parameter (the "Built-in command" checkbox in QDK) to run the command normally.
However, I think a nice new feature of Quest would be to allow for a "dontprocess" or similar to be embedded in the "beforeturn" script, which would stop that command being processed normally. So I've added that to my enormous list of things to add.

Hop to:

Contact Us | Axe Software

Powered by: Ultimate Bulletin Board, Freeware Version 2000a
Purchase our Licensed Version- which adds many more features!
© Infopop Corporation (formerly Madrona Park, Inc.), 1998 - 2000.

Author	Topic: before turn script
gamer1962	posted 17-06-2003 02:10 BST Is there a way to stop quest from processing the original command in the "before turn game script"? I want to test for conditions and possibly not process the original command based on the answer.
Alex	posted 17-06-2003 11:40 BST You can't do that in a beforeturn script, but you could do it in at least two other ways: 1. Use an "enter" command (in QDK "Enter next command into string variable"), and then process the input accordingly. If the entered string isn't one you want to "catch", then use the "exec" ("Execute a command as if it were typed by the player") command to send the string to the normal command processor. 2. Set up a user-defined command. If you're feeling brave you could set up a catch-all command "#anything#" (or similar), then use "exec" with the "normal" parameter (the "Built-in command" checkbox in QDK) to run the command normally. However, I think a nice new feature of Quest would be to allow for a "dontprocess" or similar to be embedded in the "beforeturn" script, which would stop that command being processed normally. So I've added that to my enormous list of things to add.