Closed matt-dray closed 2 years ago
~This will be less of an issue if #4 is adopted.~
Decision: age is just the difference between the current date and the birth date recorded in the blueprint. The difference between 2022-09-19 and 2022-09-20 is 1, regardless of whether the pet was born at 2359.
Should the 'age' characteristic in the blueprint be the number of unique days for which there's been an interaction? Or days between birthdate and last interaction date? Or could these be separate characteristics in the blueprint?
(Originally I was going to trigger a daily GitHub Action to remotely update the age value, but this requires the user to set up a repo for the pet, which is an added layer of complexity I don't want. Instead, we can check and update the age value in the blueprint whenever the user interacts with the pet.)