Quest 5.3 released
Alex
14 Jan 2013, 17:36Quest 5.3 is out now: http://www.textadventures.co.uk/quest/download/
Many thanks to everybody who contributed code, donations or bug reports for this release - please keep them coming!
Many thanks to everybody who contributed code, donations or bug reports for this release - please keep them coming!

The Pixie
20 Jan 2013, 15:23Can I suggest updating the tutorial to include the new map feature?
HegemonKhan
20 Jan 2013, 17:05if I may suggest,
maybe explain more how the game.pov works too
what's the difference between:
game.pov.alias vs game.pov_alias (from wiki, pov_alias.../...etc, http://quest5.net/w/index.php?search=po ... l%3ASearch )
how does the switching of player objects and their attributes/statusattributes get affected?
(such as with a lvlup system, what's the correct coding for it to be done properly? I hope this is related to game.pov.alias vs game.pov.alias, otherwise, this may need explaining or looking into if it causes any bugs or unforeseen problems for people)
(will the game engine remember changed attributes of a player object after switching to a new player object, and then back to the initial player object?)
I presume that the editor_player is what creates an object to be a player object? is there any limit to the number of player objects you can have?
it seems that there's options for setting universal status attributes (for the pov object I guess it called), how would this affect also having individual (for the player objects) status attributes? (or do you just not cross the two options?)
and etc... stuff related or arises from the new game.pov and multiple player objects.
maybe explain more how the game.pov works too
what's the difference between:
game.pov.alias vs game.pov_alias (from wiki, pov_alias.../...etc, http://quest5.net/w/index.php?search=po ... l%3ASearch )
how does the switching of player objects and their attributes/statusattributes get affected?
(such as with a lvlup system, what's the correct coding for it to be done properly? I hope this is related to game.pov.alias vs game.pov.alias, otherwise, this may need explaining or looking into if it causes any bugs or unforeseen problems for people)
(will the game engine remember changed attributes of a player object after switching to a new player object, and then back to the initial player object?)
I presume that the editor_player is what creates an object to be a player object? is there any limit to the number of player objects you can have?
it seems that there's options for setting universal status attributes (for the pov object I guess it called), how would this affect also having individual (for the player objects) status attributes? (or do you just not cross the two options?)
and etc... stuff related or arises from the new game.pov and multiple player objects.
Alex
20 Jan 2013, 17:46POV and map are both in the tutorial already, please feel free to update the wiki though if you think there is anything missing...