Skip to main content

What does a good game consist of? (part 8)

Non-linear quests

I have shared so far my thoughts on non-linear stories, but let's expand on it and actually define how would it be used for quests. I have once tried to make a game with non-linear story, but when it came to actually making lore quests, I ran into a major block: how could one possibly make a dynamic story?

The game design documentation for my game is already 30 pages long the quests would make it even longer.

So there had to be found another approach. I was stuck there for months. Until I read about test-driven development.

TDD or test-driven development strives to make game development process shorter, with less computer resources usage. But how would one create a quest which would connect to 20 different quests?

Here are my ideas:
- use Lucid Chart for diagrams of the quest structure tree
- better organize your code
- small amount of connections for each quest
- read on object-oriented programming
- make it more than a chore, the point is to have fun
- most of all though, make quests stand out so it's easier to connect them

Let's look at an example of the last idea. Here's an exercise for you:
try to make a quest which really stands out.

Please avoid "kill 200 rats" or "bring me 100 items of A,B, and C type" where the items are randomly put on the world with no relation to what the quest giver said.

Let me make an example: Adventurer, I am in dire need of a help finding me a sword. But it can't be just any sword. I need a scimitar which will be of yellow handle and black blade. I need you to get me one but it will be dangerous. To get the scimitar you will have to steal one from a shop, as they don't want to sell them anymore. The smithy makes them only for himself. It will be hard and make sure they don't catch you. I have the black dye, I will also need a golden-yellow which is so hard to get these days. You'll also get one at the royal apothecary.

May I ask you why you need such a sword?

I got an offer to sell it for a great amount of gold. I will give you the third.

I think you get the point.

Comments

Popular posts from this blog

object oriented programming

Object oriented programming is a sound and bold approach to c++ and internet wiring application and video games. It reduces a lot of code messes, made by global and half global functions. One of the more advanced object programming techniques are private access, poly morph and object message inheritance. It is set by c++ bjarne stroustrup and iso isometric standard convention comitee to use classes instead of structs and structures for making objects. Which means you most definitely should , but not must or have to. class Monster {     std::string memory_attributes{}; public:     void treck();     void track();     void trace(); }; The treck() function makes the monster roam and do human like jogging and trimming. track() means the monster goes ai path tracking and trace() means it tries to find other monsters in the area. class Weapon {     std::string memory_attributes{}; public:    void use(); }; void Weapon::use() {   ...

What does a good game consist of? (part 19)

Programmer's Role in Game Development -part 1: Better Code Organization This will be a bit different blog post compared to the previous. It will be a sub-series of the role of programmer in the game development. The first part of the sub-series will explain how a game programmer is more effective alone or in a team. Code organization is in my experience essential, as the amount of code quickly increases, especially if the game has many features. It includes: knowledge of the programming language, APIs, dev kits and make sure you know the techniques with which will you finish the project  list of steps to get there a clear to read and understand GDD a clear task list don't rush to learn everything about everything related to your project-set to make a project which you can actually handle(=have learnt 98%-100% about it) There you go, one step closer to understanding how to make a classic game.