1. an "it" command: whenever a player concludes a command, whatever first object he used would enter a string, so when the player would like to reuse it with a different action, the program would still recognize it.

example:

player types "examine book".
program types "this is an old, inviting book".
player types "take it".
program types "you take the book".

I found a way of doing it, with caculating the number of characters followed by the object in quest.command, and up to the first space character.

here is how i worked it out (I'll write in QDK reference, so all could understand):

in the "Game Properties" section, go to the "Global settings", to the "custom player commands".

ADD THE FOLLOWING:

command <#quest.command# it> exec <#quest.command# #usedobject#>

In the "Game Properties", in the "Actions" button, ADD THIS IN THE 'AFTER TURN ACTIONS':

setstring <objectcount;$instr(#object#;_)$>

if is <#objectcount#;0> then {
setstring <usedobject;#object#> }
else { setstring <usedobject;$mid(#object#;1;#objectcount#)$> }

this should do it.

2. the "again" command: when a player types "again", the program acts as if he retyped his last command.

example:

player types "examine book".
command types "this is an old book".
player types "again".
program types "this is an old book".

The way i found to do it is:

add a global user defined command:

command <again> exec <#last_action#>

then add a global after turn conditional:

if is not <quest.command;again> then <last_action;#quest.command#>

this means that if the player types "again", the program will run the string last_command as if it the string quest.command was retyped by the player.

3. the unspecified object command:

if a player types an action without specifying an object after it, the program asks him what does he want to execute this command on, and when the player types the name of the object, the program uses it as if the player type the whole command properly.

example:

player types "examine".
program types "what do you want to examine?"
player types "book".
program types "this is an old book".

I havnen't still figured out a way to do it.

Please help me with this, and also answer to the possibility of all the above commands appearing in the next Quest version.

I've sent you an email with code for making an "examine" command to work on its own, but for the benefit of other forum readers, here it is:

command <examine> {
msg <What do you want to examine?>
enter <examineobject>
exec <examine #examineobject#>
}

Though true only in a sense of unrecognised commands. If the program associates the command (for example, "examine") with a built-in command ("look at", in this case), it wouldn't work.

I didn't realize you have to apply the exact specific original command, and that in that case - synoyms won't do.

I'm currently working on the "get all" command, which is supposed to give you all the avaiable objects in the room to carry, but it's quite complicated, so I'll have to get back to you on this...

BTW, what of all the above will the next verion have? When will the next version come out? And why can't I upload a game I wrote to work with the 3.0 version of Quest Player? I uploaded the nessacery libraries and all...

Thanx,

I'm hoping to implement the "it" feature at least for Quest 3.0. The unspecified object command may be a possibility but I'm not really sure how useful it will be. There's already a keyboard shortcut that does much the same as "again" - if you hit F12 the last command typed will be re-entered into the command box, and from there you can either edit it or hit ENTER to execute the command again (although again, I'm not sure how useful executing the same command twice could be).

> When will the next version come out?

I started my studies at university two weeks ago which means I don't have as much time available for developing Quest as I previously did have. I might make some small progress over the next few weeks, but hopefully I'll be able to put more serious amounts of time into it come mid-December. But then there's Christmas and all... I wouldn't expect anything much more than a few smallish updates over the next few months. I still can't say when the final Quest 3.0 will be released, as I really have no idea at all.

> And why can't I upload a game I wrote to work with the 3.0 version of Quest Player? I uploaded the nessacery libraries and all...

I'm not sure what you mean - where did you upload the game?