1) I think this setting really needs to support floating point. My lifespan works out to about 2.5 days per year, but I'm forced to use either 2 days per year, which severely overestimates age, with 40-year-old "young adults"; or 3 days per year, which severely overestimates age, with 8-year-old "teenagers".
2) I'd love it if the age in years option could be configured per age stage. Thusly:
Baby = 0 + (life_stage_age_in_days * baby_years_setting)
Toddler = Baby + (life_stage_age_in_days * toddler_years_setting)
Child = Baby + Toddler + (life_stage_age_in_days * child_years_setting)
Teen = Baby + Toddle + Child + (life_stage_age_in_days * teen_years_setting)
Even more ideally, we could configure "Max Ages" for each age stage -- e.g., the max age of an Infant is 1.5 years, the max age of a toddler is 4 years, the max age of a child is 12 years, the max age of a teenager is 19 years, etc. Then the game could simply read the age in days in the current life stage, checking against the AgingManager, and set the age equal to ((AgeInDaysInLifeStage/MaxDaysInLifeStage)*(MaxAgeCurrentStage-MaxAgePreviousStage).
Tagger Testing Request: Age in Years: per age stage
Tell me what you went and broke with the latest and greatest.
2 posts • Page 1 of 1