My team of tester friends have been reporting issues for the last few weeks, and I've been busy fixing them.

Nothing impacts more a project than wasted time, and nothing impacts more the quality of the work than the iteration time between when something is changed and when you finally see it in the final game.

When it comes to text adventures and point-and-click games, less is often more. In this article I look at how adventure game interfaces evolved from complex natural language parsers to simple contextual actions, and why I chose a minimalist approach for Encounter.

When I started playing adventure games back in the 80ies, there were basically two types of game implementations:

• Games written as actual programs
• Games using some portable virtual machine or database