Science Fiction, Fantasy & Horror Forums

So, every year we have this awkward transition from the old to the new year for the RYO. Folks get busy with the holidays and can't make it back to put the final updates on their challenges from the last year before the new challenges start and they get cut off. Or they're on holiday and don't get around to restarting the challenges they hosted last go 'round. We keep promising to fix it but honestly we don't think about it until about this time each year when its too late and we're busy with the holidays too.

I was lamenting this fact, yet again, when it occurred to me that we could just add an extra week to the challenges scheduled to end New Year's Day and that would give everyone time to wrap things up neatly. The new year challenges will start as usual so we'll have both 2022 and 2023 running together for a week while the former winds down and the latter ramps up.

Hopefully it won't be too confusing but keep in mind that this is a "no code" solution that we're trying on the fly. It "should" work but it could be a big mess if folks get confused and sign up for the old "Space Opera" instead of the new which use the same banner like so many others that get renewed each year. If it goes pear-shaped we'll just put the end dates back to where they were and kill the experiment. Cross your fingers!

For now you now have until January 7th to mark books as read, drop your reading level closer to what you actually read, or even bail on the challenges you just never got around to for whatever reason. You can even use the extra days to finish off that book that the holidays interrupted. Consider it a "grace period" for good behavior.

Let us know what you think and how it works for you in this thread.

Thanks!

That was a failed experiment. Just did not like that at all. I've put things back to normal.

Obviously we will have to put some more thought AND coding into a better solution for next year. Sorry for the confusion and thanks for your patience.

Unfortunately my magic has failed. I've got a call in to Chris to take a look. I'm missing something small and elusive in the code or the database. I'll post here once we get it fixed.