I think it would be very cool if the echo for unlock included the name of the key, so:

With a *click*, you unlock a red door.

... becomes ...

With a *click*, you unlock a red door with an iron key.

Plz?

I thought it would be pretty simple...until I realized that we don't ever really have the key object to reference. We just do a check to see if you're actually carrying the key and allow the unlock. I'm not against the change, I'd just have to do a re-write of our unlock code, which isn't very high pri at the moment.

So long, and thanks for all the fish!

Perhaps we could make it so that just using unlock automatically checks all the keys in your inventory (but not containers) against a lock, so you don't have to specify which key?

I appreciate that there are implications for game balance (in that you would lose the ability to run down people who fumble with the wrong keys) but I don't see that as a major issue.

Since when have you needed to specify the key?

It's been just unlock <direction|container> as long as I can remember.

I was using "grep" on my old logs to try and map keys to doors for my notes.

In areas with lots of keys, it can be hard to tell without really digging into the logs which of the keys in my inventory was unlocking a particular door.

I don't think the change I proposed would really help me much in-game so much as it would help folks like me who tend to explore and then review the logs later to take notes, make maps, etc.

As long as the right key is in your inventory, anywhere, you unlock the door.

I believe the OP pointed out why he wanted this change. To me, it makes sense. Also, it'd be nice for areas like jade vaults or Kteng's when you have 17 keys by the time you're done and you just don't have the inventory for them all. I know that by now, I've got a system of putting items into containers and knowing what to pull out, etc., but newer players might not.

Not saying this change will happen, but I can definitely understand the reasoning for it.