Hi all hope you are of good health. Just a quick one hopefully. In 5.2 I could add to the verbs in an object commands like turn;twist;spin;rotate etc etc but in 5.4 for some reason it ignores the other verbs after the first semi-colon and does not place it in the verbs tree list on the left hand side. Can someone explain this please. Thanks terry. Happy Adventuring

I hadn't noticed this but I'll add that it worked fine on Quest 5.3 also and possibly even 5.4, but definitely not now on 5.4.1.

It doesn't seem to affect all verbs, things like siton seem to work fine, it's just newly created or edited verbs that develop the problem. Looking at the attributes I can't find any discernible difference between them.

I just added "smash; bash" to an object and it works for me.

"turn" is a built-in verb though. If you want to add twist/spin/rotate to it, change it in the library to accept those as aliases for it. To do that, Filter, Show Library Elements, select Turn, Copy, and change the command pattern to "turn;twist;spin;rotate".

On my Quest 5.4, it:

[list]
[*] Does allow me to put "smash; bash" in the object pattern[/*:m]
[*] Does not allow me to put "smash; bash" as the object name[/*:m]
[*] Because the object tree on the left lists by name, not by pattern, does not allow me to have "smash; bash" on the object tree[/*:m]
[*] I can however call it with a name of "smash bash" and that will then appear on the left - it just won't allow punctuation for the name[/*:m][/list:u]

psy

One of the errors I have is for "climb" which I had already copied from the library.

My other error is for the new verbs "fold; fold up" which is not a default verb. Deleting the verb (and the entries from the objects that use it) and recreating them does not solve the problem.

It seems to only affect verbs that involve two words in the command pattern.

Derr I must do everything the hard way. I'm like the proverbial ostrich buries it's head in the sand and whistles...oh well never mind about that. Thanks Alex I never thought of that and would explain other strange happenings to other verbs. Now I can go back and sort them out. Millions of thanks once again Terry. Happy Adventuring
Liam 315
Couldn't you use the COMMAND PATTERN for doing that eg:- fold up [OBJECT];fold #text# [OBJECT];fold [OBJECT] #text#;fold #text# [OBJECT] #text#.
At least that way you are sure cover all your bases?
Thanks to all once again

guzmere wrote:Liam 315
Couldn't you use the COMMAND PATTERN for doing that eg:- fold up [OBJECT];fold #text# [OBJECT];fold [OBJECT] #text#;fold #text# [OBJECT] #text#.
At least that way you are sure cover all your bases?

I have used the command pattern to do exactly that. So although any of the following uses of my siton verb command pattern works correctly:
sit on #object#; sit upon #object#; sit down on #object#; sit down upon #object#

My fold verb only uses the first one correctly, not the last.
fold #object#; fold up #object#

Same with my climb verb (which I have copied a new version of).

These had all been tested and were working find when I originally made them.

As far as this goes:

fold #object#; fold up #object#

should it not be reversed to match "fold up X" first? Otherwise, if you type "fold up blanket", then it will match "fold (up blanket)" and say it can't find "up blanket"...

Yeh that works, thanks. I've managed to sort out my climbing verb as well. The rest of my verbs are kept as singular entries so I shouldn't have any more trouble.

I still can't help but feel that Quest should check the whole command pattern for the best match rather than just going with the first partial match and dismissing the rest. Especially when it works when the extra word is not next to the object in the command, i.e. "sit down on #object#" works even though it is listed after "sit on #object#" in the command pattern.

I could have sworn they worked before but maybe I'm going crazy and didn't test as thoroughly as I thought I did.

Anyway, thanks once again.