I'm using Quest 4.02...

Any idea what would cause "speak to object" to default to 'standard invalid command message' when a 'speak message or script' is tied to an object? When I attempt to 'speak to an object' where there is no 'speak to message or script' attached, the 'standard invalid command message' displays, although I have a 'standard default speak to message' ready to go... ?

The ASL is from a game created first on v3.53, and I had no trouble with this until continuing programming using 4.02.

Any ideas?

You're too vague.

Without knowing the code, there's no way anyone can provide help.
This just sounds like you're expecting Quest to do something while it actually does something else.

I'm just trying to get some ideas that could cause "Speak to" to not work and print the "invalid command" message. I've checked my synonyms for 'speak' or 'speak to,' I have no Game verbs listed, and no Game Command or Room Command uses the word 'speak' or 'speak to'; therefore, there's no confliction occurring with the term 'speak' or 'speak to.'

Ok, here's the code for an object I've been testing "Speak to" on... I don't think you'll find anything wrong here, but to list code for my whole game would not coincide with a proper post length... Object name, alias name, and procedure name are dumbed up for quick viewing... Also, it should be mentioned, the look message executes perfectly, along with the procedures listed below....

	define object <Object_Name>
		alias <Alias_Name>
		look msg <Text here!>
		take do <Take_Procedure>
		speak <Text here!>
		displaytype <display_text>
		article <it>
		gender <it>
		drop do <Drop_Procedure>
	end define

Can't see anything wrong there - can you please email me your ASL file and I'll take a look into what's happening.

Yah, I know it has to do with my code somewhere. When I set up a simple test-game, the speak command works fine, but when I try it in my game after switching to 4.02, it breaks down.

I've been searching through my code trying to find a hint of a problem that would cause the err, and I think this combing-through helps me learn. I'm gonna keep on trying to locate the problem myself right now, because there's a few things I've thought to look into, but if any ideas concerning what it might be appears in your mind, I'd sure like to read them. Thanks again.