Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0007292Dwarf FortressDwarf Mode -- Noblespublic2014-07-14 14:392014-10-05 18:34
Reportercwilhelm 
Assigned ToToady One 
PrioritynormalSeveritycrashReproducibilityhave not tried
StatusresolvedResolutionfixed 
PlatformPCOSOS Version
Product Version0.40.02 
Target VersionFixed in Version 
Summary0007292: 2 Baronness at one time - Crash when I try to see relationships on near Baronness
DescriptionI had a baroness for quite some time, when all of a sudden, I get a message saying that someone else has become a baroness due to lineage. I assumed that this was a new feature that replaces a dead noble with a descendant. However, I checked and my old baroness was still alive and making demands (and working). I started meeting the new nobles demand's (soon upgraded to Duchess) when she gave birth. I checked the relationships on this new infant and the grandmother did not show up as the old baroness, instead it was some other name not from this fortress. Next I checked the new baroness's relationships and the game crashed. I rebooted and checked the new baronness's consort's relationships (no problem) and find another child they had - when I checked that child's relationships the game crashed as well.
Steps To ReproduceBe cursed with two nobles - check relationships on new noble and children.
TagsNo tags attached.
Attached Files

- Relationships
related to 0006699resolvedToady One y: Relationships crashes 
has duplicate 0007897resolvedFootkerchief Too many nobles 
has duplicate 0008069resolvedFootkerchief Several baron(es)s spawn at the same time for the same barony 
related to 0007295confirmedDwarfu Site has many barons/baronesses 

-  Notes
(0029352)
Shimrod (reporter)
2014-08-20 07:04

I have two barons now as well. The first one I got in 126, because (as I saw in legends mode), his father (who was a baron) was buried alive by a human in 126. Then later, my outpost liason came around and made me select a dwarf for elevation, who also became a baron.

Fort started in 0.40.04; current 0.40.09.

http://dffd.wimbli.com/file.php?id=9457 [^]
(0029357)
Talvieno (reporter)
2014-08-20 08:41
edited on: 2014-08-20 08:41

I have two baronesses in Gearedsquare: https://www.dropbox.com/s/z2xhzliq2uifs81/gear2.zip [^]

The first, Chita, inherited her position. The second came later, Chrissa, who I gave the position when the diplomat from the mountainhome offered it.

Looking at their relationship screens doesn't cause a crash for me.

Fort started in 40.07, currently at 40.09.

(0029704)
SteveTheRed (reporter)
2014-08-26 19:15

I have a fort with this problem, although in mine I have a baron and a baroness who aren't married to each other, and came to their positions independently.

http://dffd.wimbli.com/file.php?id=9529 [^]

The save is just after the baroness inherited her position (both were inherited as being the rightful heir).

I'm not sure why Logem was chosen though, as she has a bunch of older siblings. Maybe it was for her awesome name (Basementdwellers)?

Fort was created in 0.40.10.
(0029970)
Toady One (administrator)
2014-09-05 12:01

These are barons/baronesses of different sites -- I've changed the display so that instead of "<title>" it puts "<title> of <site>" whenever possible (there are a few places where it doesn't have enough information saved, like historical events). Sometimes a dwarf will inherit a foreign position. They don't know how to leave yet, and I'm not sure when I'll get to that, but at least the situation will be somewhat clarified now.

The crash though -- any more news on that?
(0029973)
Footkerchief (manager)
2014-09-05 12:38

I suspect the the crash was 0006699.
(0030152)
Talvieno (reporter)
2014-09-12 19:12

This is one of those things we really need a save for.
(0030345)
cwilhelm (reporter)
2014-09-24 14:02

Well, it's from a month ago and I don't have the save anymore. Sorry.
(0030346)
Footkerchief (manager)
2014-09-24 16:05

Okay, we'll assume the crash was covered by 0006699.

- Issue History
Date Modified Username Field Change
2014-07-14 14:39 cwilhelm New Issue
2014-07-14 16:32 Footkerchief Relationship added related to 0007295
2014-08-07 18:09 Footkerchief Relationship added has duplicate 0007897
2014-08-18 10:07 Footkerchief Relationship added has duplicate 0008069
2014-08-18 10:07 Footkerchief Issue Monitored: kwaio
2014-08-20 07:04 Shimrod Note Added: 0029352
2014-08-20 08:41 Talvieno Note Added: 0029357
2014-08-20 08:41 Talvieno Note Edited: 0029357 View Revisions
2014-08-20 09:36 Footkerchief Relationship added related to 0006699
2014-08-20 09:37 Footkerchief Assigned To => Footkerchief
2014-08-20 09:37 Footkerchief Status new => confirmed
2014-08-20 13:17 Talvieno Issue Monitored: Talvieno
2014-08-26 19:15 SteveTheRed Note Added: 0029704
2014-09-05 12:01 Toady One Note Added: 0029970
2014-09-05 12:01 Toady One Status confirmed => needs feedback
2014-09-05 12:38 Footkerchief Note Added: 0029973
2014-09-12 19:12 Talvieno Note Added: 0030152
2014-09-24 14:02 cwilhelm Note Added: 0030345
2014-09-24 14:02 cwilhelm Status needs feedback => assigned
2014-09-24 16:05 Footkerchief Note Added: 0030346
2014-09-24 16:05 Footkerchief Status assigned => resolved
2014-09-24 16:05 Footkerchief Resolution open => fixed
2014-09-24 16:05 Footkerchief Assigned To Footkerchief => Toady One
2014-10-05 18:34 Talvieno Issue End Monitor: Talvieno


Copyright © 2000 - 2010 MantisBT Group
Powered by Mantis Bugtracker