One problem I have is in having to repeat my steps when I want to go to a certain location in the game to test that something at that location works.
Is there anything built into Quest that can take me to locations with out the usual 'GO EAST, GO NORTH', etc.
Maybe a text file containing the text that the player would normally type to get to a certain part of the game which would be read and replace the player typing in each command would be useful in an Quest upgrade.

The only way I can think of to do this is to have test commands such as TEST LAKESIDE, TEST GARDEN, etc and have the script take the player directly to a location.

Just found out about the walkthroughs in Quest which will come in useful.
Apart from a walkthrough file Is there a way of going directly to a location in Quest when testing?

Don't forget about Devmode. if you active that can type in a dev command to telepeort to a room. then again walkthough would help with activing triggers needed if said exit requires somethign.

Don't forget about Devmode. if you active that can type in a dev command to telepeort to a room. then again walkthough would help with activing triggers needed if said exit requires somethign.

Thanks Zubric.

The Devmode sounds useful, I must find out more about it.

for in-game testing, you can always create your own "cheat" Commands (looks like the devmode does this for you):

though, be aware, of the rest of the mechanics of your game, you need to account for anything that needs to be accounted for

(for an example: it doesn't do any good to cheat to goto a later locked room in the game without a key to escape it)

for example:

in my example, you'd have to create and add the 'room_type' as an Object-Type/Type/Inherited-Attribute to the Objects that you want to be rooms that you can goto in the game, as unfortunately the 'editor_room' Object-Types/Types/Inherited-Attributes are for the GUI/Editor's use only, they're destroyed once you start the game

// for example, you'd type in:

cheat goto dungeon99

-------------------

<command name="goto_cheat_command">

  <pattern>cheat goto #object_parameter#</pattern>

  <script>
    if (GetObject (object_parameter) = null) {
      msg ("Wrong input, your typed-in input is not an existing Object in the game, try again")
    } else if (DoesInherit (object_parameter, "room_type")) {
      player.parent = object_parameter
    } else {
      msg ("Wrong input, your typed-in input is not an Object that you can goto, try again")
    }
  </script>

</command>

<object name="dungeon99">
  <inherit name="room_type" />
</object>

<type name="room_type">
</type>

Thanks hegemonkhan for the suggestion.