We already have a finite set of boss battles available, which can be chosen and enabled in the QA Editor tools.
Let's create a scheduled task (can run once a day in the Worker) to keep track of the last boss index, and rotate through the list as each one expires. In other words, the worker would do the following:
- check to see if a boss is already enabled
- if not, determine what the next boss should be
- activate the next boss
We can do the same thing with daily challenges if we happen to still have access to those. They may have been stored in S3, though, which would make this more difficult as we'd need to create or generate the content instead.
Summary
We already have a finite set of boss battles available, which can be chosen and enabled in the QA Editor tools.
Let's create a scheduled task (can run once a day in the Worker) to keep track of the last boss index, and rotate through the list as each one expires. In other words, the worker would do the following:
We can do the same thing with daily challenges if we happen to still have access to those. They may have been stored in S3, though, which would make this more difficult as we'd need to create or generate the content instead.