View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010341 | Dwarf Fortress | Dwarf Mode -- Military | public | 2017-11-23 21:36 | 2018-01-11 21:03 |
| Reporter | saverin | Assigned To | Toady One | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | PC | OS | Windows | OS Version | 10 |
| Product Version | 0.44.02 | ||||
| Fixed in Version | 0.44.03 | ||||
| Summary | 0010341: Canceling a mission after some dwarves have left the map prevents them from returning. | ||||
| Description | After a mission is assigned to a squad, it can still be removed using the mission interface up to a point, even if some dwarves have already left the map. Removing the mission while dwarves are off-map causes them to be stuck "traveling" and they will seemingly never return to the fort, even after retiring and unretiring. Note: If the squad is taken off the mission, the off-map dwarves will return to the fort as new arrivals. This bug only occurs if the mission is removed entirely. | ||||
| Steps To Reproduce | Create a squad and send them on a mission. After some but not all dwarves have left the map, remove the mission. (it's not clear exactly when the mission interface becomes locked, but a majority of the squad can leave before then) | ||||
| Tags | No tags attached. | ||||
|
|
Example save uploaded here: http://dffd.bay12games.com/file.php?id=13207 All starting dwarves were put in a squad and sent on a mission. The mission was removed once 5 of the dwarves had left the map. |
|
|
This happened near the end of a really long stream I was watching https://youtu.be/-PdqgmZQEbU?t=32812 |
|
|
Can this be raised in priority/assigned due to issue 0010345 since inability to auto retire the fortress when all the present dwarves are off map & dead with reclaiming parties & this present issue could be a significant exploit. |
|
|
The five dwarves from the save should return for next time, and it's generally a bit more robust. I imagine there could still be related issues though. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-11-23 21:36 | saverin | New Issue | |
| 2017-11-23 21:54 | saverin | Note Added: 0036948 | |
| 2017-11-24 15:28 | grayfox | Note Added: 0036966 | |
| 2017-11-24 15:51 | FantasticDorf | Note Added: 0036969 | |
| 2017-11-26 03:07 |
|
Assigned To | => user1294 |
| 2017-11-26 03:07 |
|
Status | new => confirmed |
| 2017-11-26 03:07 |
|
Sticky Issue | No => Yes |
| 2017-12-24 22:37 | Toady One | Note Added: 0037396 | |
| 2017-12-24 22:37 | Toady One | Status | confirmed => resolved |
| 2017-12-24 22:37 | Toady One | Fixed in Version | => Next Version |
| 2017-12-24 22:37 | Toady One | Resolution | open => fixed |
| 2017-12-24 22:37 | Toady One | Assigned To | user1294 => Toady One |
| 2018-01-11 21:03 | Loci | Sticky Issue | Yes => No |
