Upgrade Notes
Contents |
Upgrading from Quest 4.x
See separate article Upgrading from Quest 4
Upgrading from Quest 5.0 Beta Versions
Upgrading from 5.0 Beta 4
For Quest 5.0 (Release Candidate 1) and later, each compass exit has its own type. You will get some slightly odd behaviour if you don't update your exits - for example, if you have both north and northwest exits from a room, typing "n" will give you a disambiguation menu. To prevent this, go to each exit in your game and choose the direction from the "Type" dropdown, so it matches the Alias.
Upgrading from 5.0 Beta 2
For Beta 3 and later, the "player" object has been moved out of Core.aslx. This means if you have a game created for Beta 1 or Beta 2, you will need to add the "player" object yourself. You just need to make sure the object name is "player" and that it inherits the "defaultplayer" type.
You can simply copy and paste this code block into your game file:
<object name="player"> <inherit name="defaultplayer" /> </object>
Upgrading from Quest 5.0 to Quest 5.1
You can open and edit your Quest 5.0 games in Quest 5.1 (but note that, once saved, you won't be able to edit your Quest 5.1 game in Quest 5.0).
Please note that a few changes have been made to enable Quest games to be converted to Javascript (so they can run as stand-alone apps on iPhone, Android etc.). This means that some functions have been deprecated - this means that you can still use them, but I would encourage you to use the suggested replacements instead, particularly if you plan to convert your game into an app:
- the ShowMenu function is deprecated - use the new show menu script command instead
- the WaitForKeyPress (and "Wait" request) is deprecated - use the new wait script command instead
- the Ask function is deprecated - use the new ask script command instead
- the + and - operators on lists are deprecated - use the new ListCombine and ListExclude functions instead
Some minor behaviour changes:
- when playing videos with ShowYouTube or ShowVimeo, the video now automatically starts playing
- the static picture frame feature is no longer an optional extra - there is no need to set the useframe option.
New features:
- there is a new "Simple Mode" in the Editor, which can be toggled on and off from the Tools menu. This hides away much of Quest's more advanced functionality, so is useful for beginners, or if you don't need to use the more advanced features.
- you can now add, view and edit comments in the script editor
- walkthrough assertions let you test the value of expressions when a walkthrough is running
- new while script command
- for has a new "step" parameter
- new ObjectLink and CommandLink functions make it easier to output hyperlinks within a script
Other changes:
- "changedXXXX" script attributes can now access "oldvalue" to get the previous value of the attribute they're watching
- richer set of attributes for use...on... and give...to...: useanything, giveanything, selfuseon, selfuseanything, giveto, givetoanything
- new onexit script can be run when leaving a room
- new GetAllChildObjects function, and the related GetDirectChildren function has been moved from Core.aslx to become a Quest function
- new IsDefined function
- the create exit script command now lets you specify a name for the exit object
- new IsGameRunning function
- new request types RequestSave and SetPanelContents
- new optional cacheID parameter for regex functions IsRegexMatch, Populate, GetMatchStrength