z2

hi again! which toolkit has keys & locks that are robots in disguise???
-smilymzx

Transformers! Robots in disguise!

Was that supposed to be a joke, or did you really mean that? (the toolkit with the robot thing.)

@key
#end
:touch
#set key
#die

@door
#end
:touch
#if key #do
/i
Locked!
#end
:do
Unlocked!
#clear key
#die

Or some variation on that.

Yeah, it was like Morekeys or something stupid like that.

The Mystical Winds Encyclopedia had an object library of immitation robots. I don't remember if I made key/door immitations, but Commodore's code is about as close as you can get. Objects don't have any way of setting real keys, nor can they be "captured" by the player like ammo, torches, gems, etc., unless you do some freaky stuff that you probably don't want to do (which requires multiple objects).

You could make an object put out or turn into a key, though that's boring.

If you're really bored, you could have a yellow object for yellow key code like so:
Hence, to give the illusion that a yellow key was there all along. Since this is practically pointless in itself, have a green key-like object make a yellow key.

"#become yellow key" would be better.

I remember in 1 game I made on ZZT I made the program to atomaticly giv you the key in 1 secend. This is how, from west to est (all ar color dark red on dark red):

(1) Object: (2) Key

(3) Fake

(4) Duplicator: Dir=W Speed=fast speed

(5) Extra Player No Stats

Put a red solid wall around all uv this.

Damnit, I always miss something ridiculously obvious.

For a similar engine to zzo38's, check out the Give Anything engine in the MW Encyclopedia.

If you want a door that is a real door but displays a different message when you don't have the key, do the following:

Key
Door
You can use whatever color of key or door you want.

There is a problem with that code. If the player already has a key and stands next to the key, you would see:

You already have a key of this kind!

You already have a key of this kind!

You already have a key of this kind!

etc. in a text box. Similar situation if you stand next to the door and don't have a key. You can fix this by adding "/i" before "#loop", but then the message at the bottom of the screen would rapidly refresh. I recommend adding another loop that it stay in as long as the player is in contact with the object before returning to the original loop. This would ensure that it doesn't display the message again until the player at least steps away and returns.

I wouldn't use real keys in conjunction with flags because that uses up both flag and key space. If you're doing something simple like that last example, I would just use real keys and door, but if you're doing something that absolutely requires them to be objects, I would probably use flags. One flag can easily represent three keys using a "piggy-back" technique. Basically, the following flags could represent "key 1" being set: key100, key101, key110, key111. Whereas flag 2 would be: key010, key011, key110, key111. Instead of just checking if "flag1" is set, check if one of the four are set. Setting the flag is a little more complicated, so here's a snippet:
For doors, you would just switch the 'clear's and 'set's and switch the flag names in the two groups of 'if' commands.

Christ people IT'S FUCKING KEYS. WHO CARES?