Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

I trap directions and map to go xxxxx, and have done for a while. There is a flaw in it though, in that I didn't map backwards from "go n"

So, as long as you trap directions with either barriers or : match "n _" or : match "north _", you are fine for all versions of north (n, north, go north).


start_at                 = my_location
locations {
   my_location : location "You are in a room" ;
} on_command {
   
   : match "n _"  {
      : print "Jimmy" ;
   }
   
   : match "north _"  {
      : print "jammy" ;
   }
   
   // DANGER -- Go north does not trap anything
   : match "go north"  {
      : print "jommy" ;
   }
   
}

It doesn't work reliably any more. I was using :match "n -" {} and that worked for n, north, go n & go north. This no longer works. I even tried :match "n -;north -;go n;go north" {} and the latter two weren't caught. You can still see this at the forest path in Seeker of Magic. Although it's not listed as a direction, you can use u or up to climb the tree, but go u and go up no longer work. They used to.

I replaced "u -" with "u _" and directions now work properly. You'd better fix that in future.

I just fixed it and it will be in the next release (tomorrow).