I am wondering about an update to Quest, and the subtleties of dropping stuff.

Dropping the undroppable

The first issue relates to items you can pick up, but not drop. Perhaps a cursed amulet or a journal the author wants the player to always have. Untick the box, and the player cannot drop them, right? Well, actually she can - by putting them into a container. It seems to me that if the "Can be dropped" box is unticked, the item also cannot be put in a container.

However, that drop attribute can also be a script, for handling custom drops...

Dropping to other places

Suppose the player drops something while up a tree; the item should fall to the ground, rather than stay up in the tree. I would like to add an object attribute to rooms, "dropdestination". Anything dropped in a room with that attribute will automatically end up at the destination, rather than the current room.

However, if the object has a custom script for drop, that will not happen...

So how about if both the DROP and PUT/IN commands set it so your custom drop scripts can use a local variable, "destination", and authors can use that for where the item should end up?

Does this make sense/sound reasonable/break anything?

The ' up a tree ' drop can already be covered by an if/else.
If player is at location up a tree move item to location under tree. Else move item to present location.
I personally think a separate function would very rarely used.

The drop to destination is not a problem, but I have had some serious issues with the drop and put conflict with undroppable objects. I would love a solution to that!