QuestContainer: The Heart of Your Quest System

Today, we're diving deep into the QuestContainer class  the core component that manages all quests in our game.

What's in this update

• Introduction to the QuestContainer class and its purpose
• Implementation details of our Singleton approach
• Key methods for quest management
• Code snippets and explanations

The QuestContainer: What and Why

The QuestContainer is much more than just a simple quest manager. As a Singleton, it serves as the central hub where all components of our quest system communicate with each other. This design choice ensures that quest data remains consistent throughout the game and accessible from any part of our codebase.

Key Features Implemented

Our QuestContainer implementation includes several essential methods:

• add_quest(): Adds new quests to the container and activates them
• get_quest(): Retrieves specific quest information based on ID
• set_quest_status(): Manages the active state of quests
• increase_quest_progress(): Updates progress toward quest completion

We've also implemented a signal system with quest_added to notify other components when new quests become available.

What's Next?

In our next chapter, we'll implement the QuestProgress class - a crucial component that will handle tracking and visualizing objectives for each quest. We'll also introduce the Navigation system to help players locate these objectives in the game world.

With the QuestContainer foundation in place, we're now ready to build more advanced features on top of it, creating a flexible and powerful quest system for our game.

Stay tuned for more updates as we continue to develop our quest system!

Henrique Campos