verbs and commands confuse me
Ceresbane
01 Feb 2013, 15:16what is the difference and how do you customise and assign them?
All I can do is delete existing ones and add new ones that... I can't really customise and define what they do since I don't see or am not given the option to do so.
e.g. I want my player to start a sitting/lying state (which you can't for some reason).
As such he is immobile. and I want the character to stand.
there's a command for sitting. But none for standing. I try to create one but I can't define stand as the normal state. Just name a command stand.
Plus I can't define sit as an immobile state nor can I have the player start in that state.
All I can do is delete existing ones and add new ones that... I can't really customise and define what they do since I don't see or am not given the option to do so.
e.g. I want my player to start a sitting/lying state (which you can't for some reason).
As such he is immobile. and I want the character to stand.
there's a command for sitting. But none for standing. I try to create one but I can't define stand as the normal state. Just name a command stand.
Plus I can't define sit as an immobile state nor can I have the player start in that state.
HegemonKhan
01 Feb 2013, 16:12verbs are local, you have to assign them to each object, unless you are assigning them to an object type.
commands are verbs, but they can be universal, as you're typing in what you want for that command when you're playing the game, but more powerfully commands can act like ' Call Functions ' for when you're playing a game too.
basically (to say it another way), commands are just verbs, but when you play the game, you can type in the command instead of clicking on the hyperlink option or instead of the buttons on the right panes.
Read through my "Help Noob HK" thread, as I had the same problem, in trying to understand how commands work and how to use them, and their correct syntax~formatting too. Albiet there's a lot of posts to read... but it's good for noobs, as you can follow me along, learning what I've learned, hehe.
commands are verbs, but they can be universal, as you're typing in what you want for that command when you're playing the game, but more powerfully commands can act like ' Call Functions ' for when you're playing a game too.
basically (to say it another way), commands are just verbs, but when you play the game, you can type in the command instead of clicking on the hyperlink option or instead of the buttons on the right panes.
Read through my "Help Noob HK" thread, as I had the same problem, in trying to understand how commands work and how to use them, and their correct syntax~formatting too. Albiet there's a lot of posts to read... but it's good for noobs, as you can follow me along, learning what I've learned, hehe.
Ceresbane
01 Feb 2013, 17:01ugh... is that all their difference was?
I wish they were given more appropriate names.
Like primary action and secondary action.
that makes more sense right?
But yeah I'll look up that thread. Reading the tutorial doesn't really get into the detail I need.
I wish they were given more appropriate names.
Like primary action and secondary action.
that makes more sense right?
But yeah I'll look up that thread. Reading the tutorial doesn't really get into the detail I need.

jaynabonne
01 Feb 2013, 22:34Verbs are specialized commands, and they're always in the context of an object. You implement commands with scripts, but verbs have built-in support in the Quest engine, which invokes named script attributes on objects.
So a command might be "help" implemented directly with a script.
But a verb would be like "drop key" or "wear hat" or "kill troll", which would be implemented as (respectively) a "drop" script on the "key" object, a "wear" script attribute on the "hat" object, and a "kill" script attribute on the "troll" object. When you create a verb, you can specify which attribute you want to use on the target object. Then that attribute will be invoked on the object when the verb is executed on that object (and you also specify what text to display when the attribute doesn't exist.)
If you want to directly implement a "command" as a single script, use a command. If you want a "command" to operate on objects and have the behavior be determined by each object, use a verb.
So a command might be "help" implemented directly with a script.
But a verb would be like "drop key" or "wear hat" or "kill troll", which would be implemented as (respectively) a "drop" script on the "key" object, a "wear" script attribute on the "hat" object, and a "kill" script attribute on the "troll" object. When you create a verb, you can specify which attribute you want to use on the target object. Then that attribute will be invoked on the object when the verb is executed on that object (and you also specify what text to display when the attribute doesn't exist.)
If you want to directly implement a "command" as a single script, use a command. If you want a "command" to operate on objects and have the behavior be determined by each object, use a verb.