Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Please try adventuron.io/beta

(beta 55d)

I don't think there will be adverse side effects, but do test before releasing using this version.

Thanks, but the Beta version, at https://adventuron.io/beta/, is still 55a.

Please try pressing CONTROL + F5, to receive 55d.

I'm sorry! I don't usually have to do this.

Well, I'll test the changes tomorrow.
Thanks again.

I have the same problem in case I change the boolean value of the barrier:
> test
>(key press)
>(key press)

start_at = loc1
redescribe = auto_beta
booleans {
   is_001 : boolean;
}
locations {
   loc1 : location "You are in room 1." {
      on_command {
         : match "test -"  {
            : set_true "is_001" ;
            : clear_screen;
            : print "Welcome!" ;
            : press_any_key ;
            : redescribe ;
         }
      }
   };
   loc2 : location "You are in room 2." ;   
}
connections {
   from, direction, to = [
      loc1, north, loc2,    
   ]
} barriers {
   barrier_01 : block_path {
      from    = loc1
      to      = loc2
      block_when = is_001
      message = The path is blocked.
   }
}
(2 edits)

Please try again (55e).

Incidentally, Adventuron will automatically add a press_any_key and redescribe if you print something at the same time as changing the object list (add or remove object) or exit list (add or remove listed exit) from an on_command {} block.

Usually you don't have to redescribe manually from the on_command {} block in auto_beta mode. That said, it shouldn't ask for ANOTHER press_any_key if you manually ask for one yourself.