I want the keyword “open” to be used with some words to mean attacking, but not all:
[code]Test is a room.
There is an egg in test.
Understand the commands “crack” and “break” as something new.
Understand the command “crack” as “break”.
Understand “break [something]” as attacking.
Understand “break open [something]” as attacking.
Understand “break [something] open” as attacking.[/code]
Unfortunately, this doesn’t compile unless I remove “break” from the “something new” line.
Now I suppose that wouldn’t be the worst thing, but I don’t really want to interpret ATTACK OPEN EGG as a valid command (unless the egg is already broken, maybe). Should I just allow it, or try to fix this problem? And how?
I figured it out: it’s all about the order. The “something new” has to come before the grammar lines, but the synonym assignment has to come after:
[code]Test is a room.
There is an egg in test.
Understand the commands “crack” and “break” as something new.
Understand “break [something]” as attacking.
Understand “break open [something]” as attacking.
Understand “break [something] open” as attacking.
Understand the command “crack” as “break”.[/code]
You may want to make this a suggestion for a manual update. (Assuming they’re interested in manual updates…)
Agreed w/Jim. If that’s not in the documentation, it should be. I say submit a bug, but leave it open as to whether the compiler or docs need changing.