1. When updating, it should be checked that games not in need of an update get skipped, such as 2 or 3 per week jackpot draws.

2. Consider an update per game check box along with the update all function.

3. Make sure PB and MM read all the info, but divert bonus balls to their own file which just includes the date and column A. In both create and update versions.

Regardless of how long it takes to incorporate this into a full fledged application, this one project alone will save at least an hour per week! It will also be the key to the "calculate anywhere" vision I have for the mobile app... update ALL of history with a button click, then process the game of interest with another button click... 2 clicks to a pick!

Can't believe I did not think of this sooner... wasted all of those coding sessions trying to wrangle their sloppy RSS feed.

I can also see incorporating other scripts into the mix, so alongside classification, I could check daily things like follower data or whole history distribution statistics.

Easier to continue on the journey when you have an idea of the end product.

Right now, if I were doing Agile. This would be solving the user stories: "User wants to update all games quickly with a single button", "User wants the flexibility of choosing from multiple active games" and "User does not need to know the behind the scenes functioning of the program, it just needs to present up to date information on demand".