Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001806Dwarf FortressDwarf Mode -- Militarypublic2010-05-08 22:102011-03-14 09:52
ReporterKazlor 
Assigned ToToady One 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusresolvedResolutionfixed 
PlatformPCOSWindows VistaOS Version64-bit
Product Version0.31.03 
Target VersionFixed in Version0.31.22 
Summary0001806: Non-cancelled kill orders persist into newly generated world and fortress.
DescriptionWhile defending a fortress, a squad of three soldiers were ordered through the kill list to destroy two alligators. Upon seeing the fun that was bestowed on me, I opted to abandon the fortress and generate a new world (attempting to find ideal evil and savagery settings (namely high)). I did not cancel the order.

Upon embarking to the new fortress in this new world and setting up a new squad, the squad immediately activated and when looking at the squad menu, they had standing orders to kill alligators.
Steps To ReproduceCreate squad.
Order squad to kill creature.
Abandon fortress without canceling orders.
Either create new world and fortress, or possibly even simply a new fortress or even a saved one.
Create squad.
Additional InformationThis is running on the current Mayday version.
TagsNo tags attached.
Relationships
related to 0000481acknowledged Toady One Kill/attack commands/orders don't work 
related to 0003109resolved Toady One Squad renaming on load 
related to 0002852resolved Footkerchief A long dead goblin becomes militia commander; entire squad empty afterwards 
parent of 0003285resolved Toady One Different Squad showing up 
parent of 0004099resolved Toady One Missing dwarfs in squad screen 
parent of 0001056resolved Toady One Activities Carry Over From One World to the Next 
has duplicate 0002742resolved Logical2u Kill Orders carry on through new Fortress 
has duplicate 0002974resolved Footkerchief Squad Station orders maintained after save, load of older save 
has duplicate 0002603resolved Logical2u New squad starts out with random kill order, doesn't show anybody in military screen 
has duplicate 0002634resolved Dwarfu Multiple dwarves treated as same squad candidate 
related to 0003602resolved Toady One Adventure Mode Quest Carries Over Between Characters 
related to 0000277acknowledged Toady One Game crash during saving game - cleaning objects phase 
related to 0003703resolved Footkerchief After killing a kobold thief my axedwarf's current job is still "Kill Name, kobold thief" and won't change. 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-05-08 22:10KazlorNew Issue
2010-05-09 00:12FootkerchiefNote Added: 0006441
2010-07-17 19:19Logical2uRelationship addedhas duplicate 0002742
2010-07-18 01:52FootkerchiefRelationship addedrelated to 0000481
2010-07-25 18:41piesquaredNote Added: 0011040
2010-07-25 18:57piesquaredNote Edited: 0011040bug_revision_view_page.php?bugnote_id=0011040#r4303
2010-08-07 10:08FootkerchiefRelationship addedhas duplicate 0002974
2010-08-07 10:08FootkerchiefNote Added: 0011590
2010-08-08 14:47FootkerchiefRelationship addedhas duplicate 0002983
2010-08-15 13:08DwarfuRelationship deletedhas duplicate 0002983
2010-08-18 05:00Hieronymous AlloyIssue Monitored: Hieronymous Alloy
2010-11-06 08:43Logical2uRelationship addedhas duplicate 0002603
2010-11-15 13:48FootkerchiefRelationship addedparent of 0003285
2010-11-15 14:01FootkerchiefRelationship addedrelated to 0003602
2010-11-30 18:15slothenNote Added: 0014324
2010-11-30 18:21slothenNote Edited: 0014324bug_revision_view_page.php?bugnote_id=0014324#r5453
2011-02-28 21:32FootkerchiefRelationship addedrelated to 0004099
2011-02-28 21:32FootkerchiefSticky IssueNo => Yes
2011-02-28 21:33FootkerchiefRelationship replacedparent of 0004099
2011-02-28 21:34FootkerchiefRelationship addedparent of 0003109
2011-02-28 21:34FootkerchiefRelationship addedrelated to 0003703
2011-02-28 21:35FootkerchiefRelationship addedparent of 0002852
2011-02-28 21:35FootkerchiefRelationship addedparent of 0001056
2011-03-05 00:30FootkerchiefRelationship addedrelated to 0000277
2011-03-07 10:58hyperactiveChipmunkNote Added: 0015903
2011-03-09 04:08Toady OneRelationship replacedrelated to 0003109
2011-03-09 04:08Toady OneRelationship replacedrelated to 0002852
2011-03-09 04:09Toady OneStatusnew => resolved
2011-03-09 04:09Toady OneFixed in Version => 0.31.22
2011-03-09 04:09Toady OneResolutionopen => fixed
2011-03-09 04:09Toady OneAssigned To => Toady One
2011-03-14 09:49FootkerchiefRelationship deletedrelated to 0003703
2011-03-14 09:50FootkerchiefRelationship addedrelated to 0003703
2011-03-14 09:52FootkerchiefSticky IssueYes => No
2013-03-04 02:46DwarfuRelationship addedhas duplicate 0002634

Notes
(0006441)
Footkerchief   
2010-05-09 00:12   
God that's appalling.
(0011040)
piesquared   
2010-07-25 18:41   
(edited on: 2010-07-25 18:57)
A perhaps slightly more serious consequence is that orders persist between saves. Facing an overwhelming siege I made a backup save to see what would happen if I tried to face it. I then ordered my military out the main gates, and watched them get slaughtered, fort spiral into defeat.

I restored to the backup to try a more conservative/cowardly/survivable tactic. This time I'll just raise the drawbridge, right? My military charged out the main gates, I watched them get slaughtered, fort spiral into defeat.

A quick test confirms that orders persist between saves the same as between fortresses.

Edit: This is less easy to test, but there seem to be other bits of squad information that incorrectly persist between saves. Namely, who's in a particular squad. Following the first massacre, only 3 dwarves from my military lived. Upon the reload, only those were listed as being in their squads, and the ones that were missing couldn't be re-added. I could add more dwarves, though, and any orders given to the squad would then potentially effect more then 10 dwarves. Probably just one bug, which is that with the revamped military, squad information isn't cleared when one saves or abandons.
(0011590)
Footkerchief   
2010-08-07 10:08   
Niveras posted this save for duplicate report 0002974: http://dffd.wimbli.com/file.php?id=2909 [^]
(0014324)
slothen   
2010-11-30 18:15   
(edited on: 2010-11-30 18:21)
This bug still exists in .18

I removed a squad member from a squad, then had to load a previous autosave from before that squad member was removed. Upon loading the new save, that squad member was not listed as a member of the squad, nor was that dwarf listed among dwarves eligible to be added to the squad. That dwarf continued to behave as a member of the squad, responding to station orders, carrying equipment, and training. Filling the vacant squad position seemed to have no effect on that dwarf's behavior.

I was able to find a workaround for my particular problem. I made that dwarf my captain of the guard, activated the captain of the guard squad, then fired her, and the dwarf went back to normal behavior.
(0015903)
hyperactiveChipmunk   
2011-03-07 10:58   
Exists in .21, much the same as in piesquared's case. Orders persist, and members who died are no longer in the squad upon reload. Exiting the game and re-loading "solves" the problem.