Number of generations should be N+1

Bug #599407 reported by Andrés Pérez-Figueroa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
newAge
New
Wishlist
Unassigned

Bug Description

Just a stupid issue. The program should run N+1 generations (e.g. If you say 200 years, then include the year 200). Most of user won't consider year 0 in their count

Changed in newage:
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.