I may be misunderstanding, but setting the describe_new_location to "true" when performing a goto would force the game to do a redescribe when you arrive. Setting it to false would force it to keep silent.
However, setting it to true doesn't seem to force a redescribe. It's not a massive problem, since I can immediately call "redescribe" afterwards.
type "xyzzy" when the game starts, and you will be transported to the second location, however the new location is not described upon arrival.
start_at = location_1
locations {
location_1 : location "You are at Location 1."
{
on_command {
:match "xyzzy -" {
:goto "location_2" describe_new_location="true" ;
}
}
}
location_2 : location "You are at Location 2." ;
}
This still seems to be an issue. I have to add a :redescribe; after the goto. Maybe just remove this parameter, it's not a problem to just add a redescribe, so it's probably unnecessary sugar.
I may be misunderstanding, but setting the describe_new_location to "true" when performing a goto would force the game to do a redescribe when you arrive. Setting it to false would force it to keep silent.
However, setting it to true doesn't seem to force a redescribe. It's not a massive problem, since I can immediately call "redescribe" afterwards.
type "xyzzy" when the game starts, and you will be transported to the second location, however the new location is not described upon arrival.