Hi everyone,

I have an object that I don't want the player to be able to take, so I went to its inventory and typed a custom message into the edit field, telling the player that it would be pointless to carry that object around with them. I left the "take" box unchecked.

Next, I unchecked the "drop" box, and typed in a message like, "You cannot drop something you are not carrying."

When I ran the game, my custom "take" message appeared, but when I entered "drop," I got Quest's default response, "You are not carrying them."

Any ideas why this would happen? I've tried it both with the "drop" option selected and unselected, with "take" always unchecked.

This sounds like the correct behavior. After doing the TAKE, you presumably do not have the object in your inventory, because TAKE is not allowed. So when you do the DROP, you get the message that you are not carrying it. Quest does not even get as far as checking if it can be dropped or not; you are not carrying, and that is that.

I'm the kind of person who will type commands I know won't work, just to see what response I'll get from the game. I guess I was thinking of players out there who might be like me in that regard, and trying to set up responses for as many random things as I could picture somebody trying to do, including trying to drop something they aren't carrying. That is why I wanted to change the response that would be displayed if somebody did happen to type "drop." I'm just eccentric, I suppose. But it doesn't really make sense or serve a purpose to mess with it.

The drop message is only shown when you drop the object (kind of logical!), not when you drop something you don't have. In fact that is true of every time you reference an object: if it isn't there, you will get a generic message, not an object-specific one.

You can change the default responses by editing templates (I think), for example change the default response to dropping something you don't have to "You cannot drop something you are not carrying.", but how to do that is above my pay grade. You can find it somewhere in the documentation (I am so helpful today!).