Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

I've uploaded a new version of 'Seeker of Magic'. It's the same link and password as given in the first post. It incorporates all the changes suggested by my wonderful testers plus fixes for some other bugs that I found. There were some issues with the standard movement verbs that allowed you to (for example) use GO NORTH rather than N and bypass the obstacles related to the troll and darkness. This used to work, but there must have been some changes to Adventuron that caused it to break. I've had to completely redo this using barriers. I hope it works more reliably this time.

Enjoy. Bug reports and comments are more than welcome.

Now I'm ready to test other people's games. What fun!

I hadn't even thought of checking if GO NORTH caused problems! I often manually code barriers with matches like "N _"... Urgh.

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).