Barebones of Quests
"Quests" and "Missions" in Video Games all have common bare-bones, whether blatant or subtle. In this article, we'll explore the "skeletal structure" of quests in video games and how we can add "meat" to it.
Don't worry about the story
Well, not yet, anyway. After all, the #1 priority in the creative side of games should be the challenges players have to go through. Before we go any further, let's put ourselves in a position where a designer cares more about progressing his story in a scenario as opposed to making a fun quest. Jonas was a powerful Battlemage. He had unlocked all five sacred runes and was fully prepared to enter the Dark Wizard's lair. Except a Stone Guardian stood in front of the entrance. Jonas fought the Stone Guardian, who shattered to pieces. When he went inside the lair, the Dark Wizard decided to absorb the Stone Guardian's soul and grew stronger than ever. Okay, not my best work, but you get the idea. This sounds like it'd be really enjoyable to go through because the story's so deep. Hey, even from a gameplay perspective it's pretty neat. The Dark Wizard has new powers in the final boss battle! Except, there's one thing missing. The depth. Not the kind of depth you look for in a story, either. I'm talking about the sequence of actions the player must take in order to complete his mission. When you think about it, the final quest really just boils down to the player going to the lair and killing two people. He should have built his story off of the barebones of a fun quest.Barebones of quests
I think you've seen them in games before, too. You've played enough mediocre and just plain awful RPG games to see that all quests have this skeletal structure of blandness that's added on to by story. These barebones often include basic quest structures such as:- Go find this item.
- Go kill this mob.
- Bring this mob to this location safely.
- Go kill X amount of mobs and bring me their substance.
Conclusion
Now we know how to give a quest both an interesting story and a fun sequence of action. Basic tasks can be expanded into something really deep with a bit of effort, and it's up to you to either conform your stories to your quests, or the other way around. This method can be used for those who aren't good at coming up with stories and need to create an incentive to play the game, or for those who are great with stories and need to create quests that can also stand as a fun and challenging experience.Related Tutorials
Lesson 1 — What C# Actually Is
Why is C# the language driving the production of thousands of indie games using Unity and custom engines all around the…
Steps to Make a Simple Game in Unity
if you’re diving into game development, Flappy Bird is basically the ‘hello world‘ of the gaming universe. It is the ul…
Automatic Tutorial Creation for Unity | No AI | No more time waste
Automatic Tutorial Maker (ATM) for Unity is a tool that automates in-game tutorial creation by recording developer acti…
Save and Load System for Godot 4 – Tutorial
Saving and loading game data is a crucial feature for any game, as it allows players to continue their progress even af…
Unity Finite State Machine Tutorial
Comprehensive tutorial on utilizing finite state machines (FSMs) in Unity game development. It explains the concept of …
Project Structure - Guide to Cocos Cyberpunk Source Code
In my previous post, I mentioned that I would be write a series of articles on Cocos Cyberpunk. So let's kick off with …
Discussion