Let quest completions beyond a page's need count toward the next page
A season book opens a page each week, and a keen player finishes quests before the next page exists, so their effort vanishes or sits at a full bar that pays nothing. Here is a single running count that fills pages in order and banks the surplus.
Why this works
Effort should never be lost to a calendar the player cannot control. One running total, with each page reading its share from it, means work done early is already waiting when a page opens, and handing out a reward changes nothing.
When not to use it
Skip it when the book is meant to pace players on purpose, so nobody can rush ahead and finish everything in one weekend. Then keep a cap per page or per week, and tell people what happens to extra work.
In the full entry
- What to build, step by step
- Starting values and the reason for each
- 4 common mistakes and the fix
- A diagram of every state
- 23 lines of example code with 3 checks that pass
- How your AI shows you that it works
Say this to your AI
Use the Spielerando entry "Let quest completions beyond a page's need count toward the next page" (read_entry season-book-extra-completions-carry-over) 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