Keeping tasks until the end of the game

We hope you are confident users of a feature “Keep until answered correctly.” (https://loquiz.com/2019/03/20/two-new-question-settings-to-keep-tasks-in-the-game/). But we also hope that the sibling of this feature, called “Keep until the end of the game,” will find a spot in the array of your gamification tricks. 

What’s “Keep until the end of the game”?

The task is not disappearing from the game, even though the players opened and answered the task beforehand. If a task is basing on a pin, the pin will stick and stay on the map until the end of the game. If you set up the task in a list format, the task will remain in the list until the end. 

When can you implement it:

• In every game format (in- or outdoor games; list- or map-based games). It’s a task that could need examination over and over again. It could be a set of hints that the players are using different phases of the game or an intro task to a new game level. 
• In outdoor or map-based games – when the task serves an informative role. For instance: important landmarks, restricted areas and borders of the game. Or pins at tour-based games that could be returned several times. And with similar purposes.

A couple of small aspects to consider before starting working with the feature: 

• As answering the task multiple times is possible, the new answer submits will sum to the overall score. The system is not calculating it as a median. 
• It’s not recommended to have the finishing condition of a game as finishing when all tasks are completed. The tasks with the feature of “Keep until the end of the game” won’t be completed, and that restricts the game finishing. A good alternative for the game finish can be a time-based finish. 
• In the “Keep until the end of the game” configurations, you can find the default time of “Deactivate location after answering for” as 60 seconds. The reason for that is, when used in the outdoor map-based game, the GPS will instantly activate the task again. To allow the teams to exit the task radius, it would be a good idea to add a brief time of deactivation.