What's new in Quest 5.8.0
Aug 2, 2018
- Updated interface and many other new features.
New in Quest 5.8.0 Beta 0 (Dec 31, 2017)
- The major changes are to the interface, and are by SoonGames, with enhanced language support.
New in Quest 5.7.0 (Apr 5, 2017)
- More options for customising the user interface via the editor, such as a cursor instead of a box for the command bar, different colour schemes for the game panes and background blending from one colour to another.
- Enhanced text processor for coloured text, pop-up text, complicated conditions or indeed processing any Quest code.
- Clothing.
- Icelandic.
- Numerous other small changes.
New in Quest 5.6 Beta (Jan 31, 2015)
- updated embedded version of Chromium to v37
- updated various other dependencies to their latest versions, e.g. jQuery and jQuery UI
- warn when creating a large .quest file
- various bug fixes
New in Quest 5.5.0 (Mar 3, 2014)
- To prevent so many tabs from showing when editing a game, some of Quest's features can now be toggled on and off - on a per-game basis, and on a per-object basis. When upgrading, some features in the Editor may be hidden until you turn the feature on again.
- Per-game features - set these by selecting "game" and then go to the Features tab. Turning these options on will cause the relevant tabs and script commands to be shown.
- hyperlinks
- map and custom drawing grid
- static picture frame
- score
- health
- inventory limits
- light and dark
- ask and tell
- in-room descriptions
- Per-object features - set these by selecting the object and then go to the Features tab. Turning these options on will cause the tab to be displayed for the object.
- use and give
- container
- switch on/off
- edible
- player
- Other changes:
- The "Pause" request is no longer supported. Use the SetTimeout function instead.
- The game title and author name are now displayed by default when a game begins. You can turn this option off from the game Setup tab.
- In gamebook mode, the new default style is to not clear the screen between different pages. You can revert to the old behaviour by clicking game, then go to the Display tab and tick "Clear screen between each page".
New in Quest 5.4.1 (May 7, 2013)
- If you have any exits that run scripts instead of automatically moving the player, you will need to tick a new checkbox on the exit editor "Run a script (instead of moving the player automatically)".
New in Quest 5.4 (Mar 29, 2013)
- the old synchronous functions Ask, ShowMenu, GetInput and synchronous Wait request are now unsupported, and will raise an error if used in a game with ASL version set to 540 or above.
- ASLX attribute type name changes:
- "list" becomes "simplestringlist"
- "stringdictionary" becomes "simplestringdictionary"
- "objectdictionary" becomes "simpleobjectdictionary"
- new "stringlist" format
- new "stringdictionary" format
- new "objectdictionary" format
- new "list" format
- new "dictionary" format
- new functions NewList and NewScriptDictionary
- new text processor
- GetTaggedName is removed from Core.aslx
- GetDisplayNameLink no longer takes a verbs parameter
- new function SetAlignment
- the insert script command is obsolete, as you can directly write HTML with msg
- the old text formatting XML is no longer relevant - use HTML instead. The only breaking change is there is no "color" tag in HTML.
- new "JS." calling method for JavaScript functions
New in Quest 5.3 Stable (Jan 15, 2013)
- Display verbs are now automatically generated by default. If you want the old behaviour (manually specifying display verbs for each object), go to the game Room Descriptions tab and turn off "Automatically generate object display verbs list".
New in Quest Stable 5.2 (May 14, 2012)
- Quest has been completely rewritten. It is now free and open source, and much more powerful.
New in Quest Stable 5.1.1 (Feb 14, 2012)
- Quest has been completely rewritten. It is now free and open source, and much more powerful.
New in Quest Stable 5.1.0 (Jan 12, 2012)
- Quest has been completely rewritten. It is now free and open source, and much more powerful.
New in Quest 5.1 (Oct 14, 2011)
- Quest has been completely rewritten. It is now free and open source, and much more powerful.
New in Quest 5.0 Beta 4 (Sep 1, 2011)
- 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.
New in Quest 5.0 Build 5.0.4259.15119 (Aug 31, 2011)
- Quest has been completely rewritten. It is now free and open source, and much more powerful.
New in Quest 4.1.5 / 5.0 Beta 2 (Jun 30, 2011)
- Loading QSG (save game) files is now faster.
- Fixed a QDK bug with the “create corresponding exit” checkbox, which would become re-checked if it was turned off.
New in Quest 4.1.4 (Jan 4, 2011)
- Quest is now free - make games as large as you want, with no limitations
New in Quest 4.1.2 (Jan 18, 2010)
- New Quest Packager lets you create stand-alone games
New in Quest 4.1.1 (Sep 6, 2009)
- Fixed bugs:
- Some expressions were being calculated incorrectly. Quest would always perform addition before subtraction, leading to erroneous results. It now performs division and multiplication first, left-to-right, then addition and subtraction, left-to-right.
- Dynamically created directional exits without scripts would cause a run-time error.
- Entering a dynamically created room would cause a run-time error.
- If an object's parent tag did not match the exact case of the parent object, it wouldn't be listed in the contents.
New in Quest 4.1 (Jul 20, 2009)
- Object prefixes and suffixes are now used when disambiguating objects, so if object apple has a prefix of "an", the player can type "look at an apple" or "x an app" etc.
- New quest.doorways string variable replaces the old quest.doorways.* variable, with a complete formatted list of exits from the current room.
- When disambiguating an object name, extra spaces are now ignored, so e.g. "look at banana" now works properly.
- Significantly improved performance when loading and saving QSG files.
- A new variable #quest.error.object# is now populated when disambiguation of an object fails. This could be used in a "badthing" error message to display which object name failed to be resolved.
- New "alreadytaken" error displays "You already have that" if the player tries to take an object which they already have in their inventory (previously Quest displayed a misleading badthing "I can't see that here").
- Quest could previously crash if there was a loop of object parents, e.g. if A's parent was B, and B's parent was A. This no longer occurs, and Quest now logs an error message if a loop is detected in an object parent hierarchy.
- Fixed bugs:
- $lengthof(...)$ function was returning an incorrect length for strings that started on ended with space characters.
- Comment lines were incorrectly being checked for opening and closing brackets and variable characters.
- If the last object in a room had a prefix or suffix containing a comma, the word "and" would be added in the wrong place in the object list.
- Brackets in strings passed to functions would truncate the list of parameters. Quest now checks for the closing bracket nearest the end $ character.
- Typing a command followed by a space would bring up a disambiguation menu of all objects.
- Resources in CAS files using nested folders didn't work.
- Putting something in a container implicitly makes thatcontainer "seen", for games with ASL version 410 and later.
- Previously, if the player put something in a container that they had not looked at, they wouldn't be able to look at that item until they looked at the parent, as the parent was not marked as "seen".
New in Quest 4.05 (Apr 27, 2009)
- Redesigned visual editor QDK so it is now even easier to create your own games
New in Quest 4.04 Build 4.0.88 (Dec 1, 2008)
- Fixed bugs:
- fixed run-time error displaying collectables in Quest 2.x games.
- a run-time error occurred if a game's default font name was invalid.
- a run-time error could occur if variables were accessed using different cases.
- CAS files with resources which used "define menu" blocks wouldn't load correctly.
- verbs defined with capital letters wouldn't work correctly.
- an object inside a container which was itself inside a closed container could still be taken. The container logic has been improved to recurse properly through the parent containers of an object before allowing it to be taken, opened, closed, added or removed.