First Encounter

This is a brief Adventuron game that has a short tutorial at the beginning.

In it, you play as a young child at a hotel who wakes up to find an old woman in your room. She beckons for you to follow.

And that's most of the game; the gameplay is pretty simple. There are a few small puzzles, but this is otherwise mostly linear. The concept has a lot of implicit horror in it, but I feel like that theme wasn't developed as much as it could have been.

Overall nothing is bad in this game, there's just not much: not much story, not much interaction, not much game. I feel like it could be expanded a bit, but as it is, it was fun while it lasted.

This is a tiny, simple, immersive game written using Adventuron. The experience player will recognise a comfortable adventuring experience, the new one will go through this one without frustration (there is a tutorial, navigation is simple, puzzles are self contained).

It does not do anything particularly new, but sometimes you just want to play some good horror. Well done!

This looks like a first-time complete game from an author who had, as of 2023, some basic game elements and a partial one. So they knew what an initiate to text adventures might have had trouble with. Not only that, they've executed something that would work well on its own or as a fit for TALJ. First Encounter is a brief horror tale where a ghost of a woman appears to you, and you follow her. It's not quite clear why she appears, so there's some mystery.

However, you learn soon enough, because FE is relatively on rails. The experience was effective for me. There aren't many puzzles beyond finding a light source and leaving the house the right way. Locking yourself outside to follow ghosts with uncertain motives willy-nilly is just a bad idea and, in this case, taking precautions heightened the tension for me. There are also a few directed-verb-guessing puzzles. Here I'd suggest the tutorial might go on a bit longer. I really don't know if Adventuron has something to look at the input and say, for instance, if someone has a kazoo and people type BLOW KAZOO, "this is a relatively simple verb." But if it does, that feels like a tap-in for a post-comp release.

Saying the author didn't try to do too much always feels like a backhanded compliment because it kind of implies they shouldn't have considered reaching higher, or maybe they should not do so the next time. But here I hope it is sincere, because of the increasing scope I saw in their itch.io submissions, and it feels like they're ready to make another jump soon, if they want. Too many people, some with considerable skill and knowledge, shoot too high and wind up with nothing. I think TALP really helps with that--you'd better have an excuse to do too much! And one problem with a too-elaborate game is that it can exhaust reviewers and judges for the next one, though of course too many that lack details make us look for more exciting stuff elsewhere. And of course there's a balance between self-interest and not hogging the oxygen. It feels like EF made sure it did not hog the oxygen, and the author can and should be bolder with their next game.

FE works particularly well with TALP, as it took on a good subject and good atmosphere that forced it, or gave it an excuse, not to do too much. In this case, adults were sleeping and you didn't want to disturb them, which meant you couldn't go walking through the house. It may be the shortest one you play through in TALP, but that's more due to very sensible, logical cluing and an economy of use. There are few red herrings, if any.