The Greenbox System

How to best implement Quests seems to attract quite a few questions among

(new) game developers (see links below) and a good Quest system probably requires a lot of thought even from experienced game developers. Obviously, the quest system you choose strongly depends on the type of game you want to implement.

I will not talk about using an existing quest system that ships with an engine or hard-coding individual quests in this blog post. Instead, I like to describe my self-made approach towards a quest system which reads the data for each quest from an external resource. I will give code examples which hopefully can inspire other game developers facing similar issues.

Saturday, July 18, 2015

What is "Tales - Told & Untold"

A World of Plenty

The 2.5D game world of Tales - Told & Untold
is hand-painted, non-repetitive and full of details.

Many games provide a big game world. In GTA you can freely move through a whole city or even a whole state. In Skyrim a whole continent is freely accessible. In Doom & Destiny, the worldmap is huge. But often a huge game world means an empty game world. In the older parts of the GTA series, you couldn't access most houses. In Doom & Destiny (which is - by the way - a great game), only a few cities and dungeons are spread across a huge world map.

Skyrim does a good job at populating the world, but sometimes you will encounter the same interchangeable event at different places or you will enter a dungeon that looks almost like the one you explored before. The reason for this is simple: content, especially good content, is expensive.

But the real world is different. There are no vast areas that are almost empty. The world is full of people, each of which is different. The wonders of nature are many and at every corner there is a story to discover, if you have time to explore it. That is what I want my game "Tales - Told Untold" to be like.