Looking for Testers - Quest 5.8 Bug-Fix Update

Hi all,

Quest 5.8 has a few issues, and we are currently seeking a few people to test our bug-fix build.

We have the desktop version for Windows, and we have the web player running on a testing server.

Reply here or send me a message if you'd like to take part.

Thanks, and happy gaming!


Gng

Hello

I like to participate 👋


Thanks, Gng!

I sent you a DM.


sure


Thank you, @Woodhouse3D.

You should now have the required info in your inbox.


This update doesn't really add anything new. It is just a bug-fix update.

There were a few new things in Quest 5.8 that either didn't work at all or completely crashed games when used. This update should fix all of that.

AllRooms() Function

We added a new function named AllRooms to return an object list of all the rooms in a game.

This worked in the editor during play-testing, but it did not work in a Published game.

Pertex has contributed code to fix this.


Enter Verb

We added a way to easily add an enter verb to an object, but I didn't add the new code to the proper files. So, the command returned an error during play.

mrangel posted code in the forum which I have stolen and applied to this update, and this is now fixed.


The Log Feature

Quest 5.8 removed the functionality of the desktop player's built-in window which displayed any log entries created via Quest's Log() function.

That has been restored in this update.

Other tidbits concerning the log:

  • If game.useconsolelog is set to true, the Log function will pass the text along via JS.console.log() (game.useconsolelog is false by default)

  • If game.writelogtofile is set to true, each log entry will be written/appended to a text document in "Documents\Quest Logs" (game.writelogtofile is false by default)


The Transcript Feature

I did all sorts of thing wrong when submitting code to add the transcript feature.

In the desktop player, enabling the transcript during play breaks all turn scripts. No turn scripts will fire while the transcript is enabled.

In the online player, enabling the transcript completely crashes the game.

All of the transcript related issues should be resolved in this update.


Clearing the Screen

Quest 5.8 also introduced the option to hide the text when the screen is cleared rather than deleting it each time (which was how it previously worked).

The JavaScript variable saveClearedText was set to true by default. So, without the authors knowing it would happen, any cleared text was saved rather than deleted. This proved problematic in games which printed a good amount of text during play. This is because most of those games clear the screen quite often, which would delete all that text from the document each time. In Quest 5.8, that text is not actually deleted, and the document gets bigger and bigger, which negatively effects browser performance.

In this update, saveClearedText is false by default. So, that should resolve those issues.


Background Color

There has been a bug for a while when using a code like #CCC for the background color.

This has been resolved, and Quest will convert #CCC to #CCCCCC properly now.


Resuming Play Online

When saving the progress during play online, it sometimes does not restore the existing on-screen text when you resume play.

This is fixed in this update. (This can only be tested by using the web player on the testing website.)


DictionaryRemove error message

The error message for DictionaryRemove prints "DictionaryAdd" by mistake.

This has been fixed.


The One New Thing

Pertex submitted code which allows us to set a custom location bar background image, if we wish to do so.

He even went above and beyond and contributed the code for the editor (both desktop and online). So, you should be able to easily find how to do this in the GUI.


Things in the testing build that will not be in the final version

Logo and Buttons

This build of the desktop version of Quest has a different logo and the images for the buttons have been modified.

Pertex contributed this, too. I think it looks much better! But I don't know if it will end up in the actual release or not.

Syntax Highlighting

The Code View text-boxes in the GUI have syntax highlighting in this testing build of the desktop version.

I don't know if that will end up in the actual release, either.


This topic is now closed. Topics are closed after 14 days of inactivity.

Support

Forums