Understanding the Quests System rule engine

The user begins by accessing a section that displays a list of available quests. The developer's product communicates with the Back Server to retrieve the list of quests. The Back Server generates the list and sends it back to the developer's product, which then presents it to the user along with filter options.

The user can customize the filter options based on their preferences. Once the filters are configured, the developer's product sends a request to the Back Server to retrieve a filtered list of quests. The Back Server generates the filtered list and sends it back to the developer's product, which displays it to the user.

When the user selects a specific quest, the developer's product sends a request to the Back Server to obtain detailed information about that quest. The Back Server generates the necessary details and returns them to the developer's product, which then presents the quest information to the user.

If the user decides not to pursue any quests further, they can close the quest section. However, if they choose to proceed, they engage with the quest within the product and fulfill the required conditions.

Upon completion, the developer's product sends a quest completion request to the Back System. The Back System executes the quest based on the user's actions and provides a response confirming the completion. The developer's product then notifies the user about the successful quest completion.

As a reward for completing the quest, the developer's product grants the user a designated reward. This serves as an incentive for users to actively participate in quests and enhances their overall experience within the system.

Overall, the Understanding the Quests System rule engine ensures the smooth flow of quest-related interactions between the user, developer's product, Back Server, and Back System. It enables users to discover, engage with, and successfully complete quests while receiving appropriate rewards along the way.