Playtesting has started


Play testing has started!

The process is simple: I build a new version of the game, I play it through while recording, then the recording is reviewed for glitches, typos, missing information, etc. all these are written to a wiki page as a list of bullet points.

No Jira involved

The idea is to do a first pass with only me and a close friend, to eliminate these 90% of obvious stuff that everybody would catch.

When these are out of the way, then I can get actual testers play the game, and have them report stuff I does not know about already.

So far, most of the issues have been typos, Incorrect US Style Capitalization Of Words In An English Game, strange text formulations or use of “false friends” words.

In addition some incorrect game states changes have been found, issues with some of the sounds not playing properly on the real hardware (oops).

Stay tuned :)

Comments

Log in with itch.io to leave a comment.

(+1)

Looking forward to this : )

Hopefully you will not be disappointed, but at the root it’s still a text adventure game made mostly by a single person, so don’t expect the moon :D

(+1)

I enjoy text adventure games, it's a genre that doesn't seem as popular as it was in the 80's.

Well, back then it was a relatively low barrier to entry in term of ease of programming, you could make a very simple adventure 100% in BASIC, and most of them were very very badly designed, and by the time proper tools were designed to create proper adventures, with database of items, easy to link rooms, etc… the genre was in the process of being replaced by graphical Point’n Click adventures.

I guess what I’m doing with Encounter is some kind of in-between: It’s still a text adventure game at the core, but I reduced the vocabulary to change the game from a “try to figure out the proper command to use to do what I want” to something more intuitive that let the player experiment and have cool visual and audio feedback in return.

Hopefully people will like my choices :)