Rotate weekly challenges so the same kind never comes twice in a row

A random pick sometimes gives the same challenge two weeks running, or three shooting tasks in a row, and players feel the game ran out of ideas. Yet a strict order is predictable. Here is how to draw at random while still keeping variety, and what to do when the pool is small.

Why this works

Variety is a matter of memory: to avoid repeats the game needs to know what came lately. Making the dice an input, and easing the rules in a fixed order when no choice is left, gives every player the same week and never leaves the game empty-handed.

When not to use it

Do not rotate when the challenges build on each other, or when players want to choose their own; then show a list. Also skip the kind rule with only a few challenges, since there will be repeats anyway.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• A diagram of every state
• 13 lines of example code with 5 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Rotate weekly challenges so the same kind never comes twice in a row" (read_entry weekly-challenge-rotation-without-repeats) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP