0001973: King is 180 when he arrived. Dwarven maxage is 170.

Issue History
Date Modified	Username	Field	Change
2010-05-19 14:49	ItchyBeard	New Issue
2010-05-19 14:58	Footkerchief	Note Added: 0007025
2010-05-19 14:58	Footkerchief	Relationship added	duplicate of 0000672
2010-05-19 14:58	Footkerchief	Status	new => resolved
2010-05-19 14:58	Footkerchief	Resolution	open => duplicate
2010-05-19 14:58	Footkerchief	Assigned To	=> Footkerchief
2010-05-19 15:02	Footkerchief	Relationship deleted	0000672
2010-05-19 15:02	Footkerchief	Relationship added	duplicate of 0000972
2010-05-19 15:02	Footkerchief	Note Edited: 0007025	View Revisions
2010-05-19 21:47	ItchyBeard	Note Added: 0007039
2010-05-19 21:47	ItchyBeard	Status	resolved => needs feedback
2010-05-19 21:47	ItchyBeard	Resolution	duplicate => reopened
2010-05-19 23:28	Footkerchief	Note Added: 0007041
2010-05-19 23:28	Footkerchief	Issue Monitored: Footkerchief
2010-05-22 01:57	Footkerchief	Status	needs feedback => resolved
2010-05-22 01:57	Footkerchief	Resolution	reopened => duplicate
2010-06-09 06:45	Toady One	Status	resolved => closed

Notes
(0007025) Footkerchief (manager) 2010-05-19 14:58 edited on: 2010-05-19 15:02	Although 0000972 was about a diplomat, not a king, I'm marking this report as a duplicate because I'm 99% sure the underlying cause (world gen fails to check for deaths from old age) is the same in both cases.

(0007039) ItchyBeard (reporter) 2010-05-19 21:47	While it could be a worldgen problem, the fort where this happened was 25+ years old (which would have put the leader under maxage when the fort started). If rulers are not dying out during a running fort, does that still count as a worldgen problem?

(0007041) Footkerchief (manager) 2010-05-19 23:28	The semantics get a little fuzzy... anything that happens (or should happen, e.g. old age deaths) outside your fortress could be considered world generation. There may be a better term for it, I dunno. Regardless of the term, what matters here is that it appears to be the same bug as 0000972.