I try to never think of a question as a complaint. To me they are all opportunities to improve the application.
In this case, it gives me the opportunity to see how someone might use the countdown feature, and revisit how it works and why I made the decisions I made regarding it. Today, I believe if a countdown is in progress when a tournament is saved, then when the tournament is later loaded, the countdown is simply canceled and the user will have to reconfigure and start a countdown if they wish. Thinking more about this, it doesn't have to be this way. This situation can be handled intelligently. If a tournament is saved while in progress, when the tournament is later loaded, it continues right where it left off with the only change being the clock will be paused upon loading. We can apply the same logic to a countdown. If the countdown is for a specific length of time, we do the same thing: start where we left off with the countdown clock paused. If the countdown is to a specific date/time, we allow the countdown to continue if the date/time is in the future (since this type of countdown can't be paused), or cancel the countdown (perhaps with a notification to the user) if the date/time is in the past.
There's no technical reason to allow only today/tomorrow, but it is more convenient as I believe this is how most countdowns are configured. But we could add a custom option to allow for any future date/time.