I have several places that moving in a nowhere direction gives pretty much the same result:
Instead of going nowhere from Thentis Road,
say "[one of]That direction will take you off quest.[or]The road continues into the distance but away from your main objective.[or]If you search the chapel, perhaps we can be done before nightfall.[at random]"
Instead of going nowhere from Mercer Cove Road,
say "[one of]That direction will take you off quest.[or]The road continues into the distance but away from your main objective.[or]If you search the chapel, perhaps we can be done before nightfall.[at random]"
I don’t know how to specify multiple conditions. I would prefer something like
Instead of going nowhere from Mercer Cove Road or Thentis Road...
but get an error for various attempted combinations.
One easy way to group together rooms when you want to specify rules in common among rooms is with a region.
The Road of Trials is a region.
Thentis Road is in the Road of Trials.
Mercer Cove Road is in the Road of Trials.
Instead of going nowhere from the Road of Trials:
say "[one of]That direction will take you off quest.[or]The road continues into the distance but away from your main objective.[or]If you search the chapel, perhaps we can be done before nightfall.[at random]"
A perhaps less idiomatic way to do it is to subtype the room, thus:
Instead of going nowhere from a Road-Room,
say "[one of]That direction will take you off quest.[or]The road continues into the distance but away from your main objective.[or]If you search the chapel, perhaps we can be done before nightfall.[at random]"
A Road-Room is a kind of room.
Thentis Road is a Road-Room.
Mercer Cove Road is a Road-Room. It is north from Thentis Road.
(Mentioned only for sake of variety: I actually prefer Zed’s solution.)
I tried the compound condition (location is Thentis Road etc) but I couldn’t get it to work. The region solution worked well. Thanks for letting me know that it IS possible and that it was typical user error on my part.
The former is, notably, a syntax that I6 supported but I7 doesn’t. I sometimes wonder why, because “value is option or option or option” isn’t especially ambiguous to parse. The typechecker handles worse ambiguities already.
It’s not hard to parse, but Inform’s “is” verb is extremely open-ended. You could write something like:
...when the location is Main Street or sunny or adjacent to Central Park:
Syntactically this can always be rephrased into “X is A or X is B or X is C” but the chance of landing somewhere the author didn’t intend is maybe too high.
I guess there’s also cases like
...when the location is sunny or adjacent to Central Park or Main Street: