Skip to main content

Browse GamesGame JamsUpload GameDeveloper LogsCommunity
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
Adventuron4 years ago (1 edit)

Connection scanning in explicit match commands pre-dates the barrier mechanism.

It essentially lets adventuron know when a direction will lead somewhere not covered by the connection map (like directions in a maze for example), or context specific enter and exits, or directions.

I think I'm going to change adventuron to use basic exit list calculations by default. The barrier mechanism is far more reliable at blocking and enabling conditional exits, but the mechanism can still be switched on for games with mazes (where connections mappings are dynamic and made via the on_command {} block.

Reply
Garry Francis4 years ago

Why on earth would mazes need this? Mazes aren't dynamic. Not unless they use random connections and that's a very bad practice anyway.

Reply
ChristopherMerriner4 years ago

Bad practice, but de rigueur in the 1980s, I recall (from spending many frustrating turns in mazes, back in the day).

Reply
Garry Francis4 years ago

This ain't the 1980s. If you put a maze with random exits nowadays, you'll get crucified. Even so, the maze will always show you the exits, it's the destination that's random.

Reply
ChristopherMerriner4 years ago

Sadly, this is true. Although doubtless there are a few 1980s adventure game masochists  still about, who would relish a game full of random mazes and  (for good measure) non-reciprocal exits that lead to a totally  different location in the reverse direction. There is a niche for everything!

Reply
AboutFAQBlogContact us
Copyright © 2025 itch corp · Directory · Terms · Privacy · Cookies