Oh, mea maxima culpa; I copied the code from a thread on RAIF (to make sure you were getting the version Al had, not the one with the tweaks I’d made) and didn’t bother to eliminate the line breaks. I wonder if some of his issues came from things he did to tweak non-compiling code. Of course this is a case where pretty much any tweak you make will work, because while you’re tweaking you’ll eliminate the hard line break.
Yes. I think I’ve found the underlying issue; I added this to the end of the “After reading a command”:
say X;
say "[line break]".
and steps 8 and 9 produced:
[code]>[8] x mike’s hat
x mike 's hat
Which do you mean, the bright red hat or the bright blue hat?
[9] bright blue hat
x bright blue hat mike 's hat
I only understood you as far as wanting to examine the bright blue hat.[/code]
A little more experimentation shows that what you enter in response to the disambiguation prompt gets put in front of the entire phrase getting disambiguated; for instance if (at the beginning) you enter “x bright hat/bright blue hat,” the player’s command after the response is considered to be “x bright blue hat bright hat”. Which works because any old word salad consisting of the words “bright blue hat” is understood as “bright blue hat.” Also, “x mike’s hat bright blue hat” works if entered as is (whether or not Mike also has another hat) but if you put something (besides “x”) before “mike’s hat” it doesn’t.
I’m not sure whether I think someone should file a bug report in 6E** for this, if it’s still happening. It seems to me that disambiguation ideally ought not to work this way, but it looks like changing the behavior would be a big pain.If someone does want to submit a report, here’s some shorter code that produces the same behavior:
[code]
After reading a command:
let X be indexed text;
let X be the player’s command;
replace the text “'s” in X with " [']s";
change the text of the player’s command to X.
Understand “[something related by reversed possession] 's” as a thing.
Starter is a room. Chris is a person in Starter. Chris carries a red hat. Chris carries a blue hat.
Test me with “x chris’s hat/red”.[/code]
BTW any “After reading a command” code will get executed after a disambiguation response as well as after the original command; as you can see above after the disambiguation response there are two spaces before the “'s,” but it doesn’t matter. This seems like something you have to watch out for if you’re writing “After reading a command,” rather than a bug.