View Issue Details

IDProjectCategoryView StatusLast Update
0002634Dwarf FortressDwarf Mode -- Militarypublic2013-03-04 02:46
ReporterManae Assigned Touser11 
PrioritylowSeverityminorReproducibilityhave not tried
Status resolvedResolutionduplicate 
Product Version0.31.10 
Summary0002634: Multiple dwarves treated as same squad candidate
DescriptionSave file: http://dffd.wimbli.com/file.php?id=2658

In this file, Solon Mörulurdim, Gem Cutter and Zuntîr Tegirolin, Bookkeeper are being treated as the same dwarf in the military squad menu. When Solon is in a group, assigning Zuntîr to another removes Solon from the first, and likewise if one is in a squad the other cannot be seen on the candidate list for that squad. Both behave independently of each other besides both being in the same squad if one is assigned.

World and fortress were both created in .30.06.

I've not been able to get any repeatability of this, but the information I can offer is as follows:
-In .30.08, an axedwarf in the first group died when caught by a forgotten beast before the rest of the squad had rallied to his position.
-The dead dwarf was removed from the squad, and replaced with Solon.
-Zuntîr was at no point that I can recall a part of any squad.
TagsSave Included

Relationships

duplicate of 0001806 resolvedToady One Non-cancelled kill orders persist into newly generated world and fortress. 

Activities

user11

2010-12-13 20:38

  ~0014577

Loaded in 31.18.

Verified created in 31.06.

Baroness listed also as manager, chief medical dwarf, broker and arsenal dwarf (but can be replaced/left vacant). Zuntir the Bookkeeper never shows in any list, whether Solon the Gem Cutter is in one or not. I can add and remove Solon the Gem Cutter at will to any squad.

It should be noted Zuntir the Bookkeeper is a legendary Axedwarf and Fighter (see 0000995). Removing him from office results in him being a legendary peasant.

Able to assign him as a militia captain and assign Solon the Gem Cutter as a squad member.

Deleted 3 burrows, no effect.
No errorlog.txt entries.

Deleted all squads and removed everyone from office in the nobles screen. Created a new squad. Appointed a new commander. Solon and Zuntir appear in available squad member list and can both be appointed to the same squad at the same time. Zuntir can also be reappointed as bookkeeper with no problems.

The origin of this problem was most likely fixed, but Toady may want to have a look at this, so I'm leaving it open for now.

Quietust

2010-12-13 20:50

reporter   ~0014578

Manae: Did you, at any point, load one fortress with a working military, save it, then immediately load this fortress without first closing and restarting Dwarf Fortress? This sounds like it could be a variant of 0001806.

Manae

2011-01-27 11:34

reporter   ~0014942

I apologize for the delay in any sort of response. Haven't checked this post nor the but tracker in general for some time due to being busy.

I believe the problem was solvable by creating a new squad and assigned both dwarves to it, none of the other steps were needed. I can't completely confirm this as it was some time ago.

I do have a bit more information on how exactly it happened, though: Zuntir had been in a squad (but none of my axedwarves had been legendary, that may be another bug if it was showing up that way). He was removed to become a bookkeeper so he had a non-military skill to such a level that he would not get a bad thought when going from active duty to inactive; a too-mixed training schedule was driving my soldiers to depression so I was attempting to cross-train some. The dwarf that replaced Zuntir in the squad later died and was replaced by Solon. After some Fun, I went back to an older save where Zuntir was still in the squad, which is how they got mixed.

This bug is still present in a form in the current version. Instead of becoming linked, though, the new soldiers who are no longer in a squad after going to an older save will still think they are in a squad and stand around with "Cannot Follow Order" as their job when the squad is active.

user11

2013-03-04 02:46

  ~0023877

31.18 solved this and given the save/load atmosphere, a duplicate of 0001806. The "Cannot follow order" bugs are reference/handled in other reports.

Issue History

Date Modified Username Field Change
2010-07-11 13:32 Manae New Issue
2010-12-13 20:38 user11 Note Added: 0014577
2010-12-13 20:38 user11 Tag Attached: Save Included
2010-12-13 20:39 user11 Tag Attached: Save Needs Testing
2010-12-13 20:50 Quietust Note Added: 0014578
2011-01-27 11:34 Manae Note Added: 0014942
2013-03-04 02:45 user11 Tag Detached: Save Needs Testing
2013-03-04 02:46 user11 Note Added: 0023877
2013-03-04 02:46 user11 Relationship added duplicate of 0001806
2013-03-04 02:46 user11 Status new => resolved
2013-03-04 02:46 user11 Resolution open => duplicate
2013-03-04 02:46 user11 Assigned To => user11