Anonymous | Login | Signup for a new account | 2024-11-21 04:40 PST |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
0010795 | Dwarf Fortress | Dwarf Mode -- Jobs, General | public | 2018-06-23 17:34 | 2020-02-20 12:13 | ||||||
Reporter | noxiilarxene | ||||||||||
Assigned To | Toady One | ||||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||||
Status | acknowledged | Resolution | open | ||||||||
Platform | OS | Windows | OS Version | 10 | |||||||
Product Version | 0.44.11 | ||||||||||
Target Version | Fixed in Version | ||||||||||
Summary | 0010795: Messengers Do Not Go On Mission | ||||||||||
Description | Dwarven messengers assigned to a mission to bring back dwarves from an occupied site do not go on their mission, only doing in-fort jobs. | ||||||||||
Steps To Reproduce | 1. Start a Fort 2. Conquer a site 3. Assign a messenger 4. Assign messenger to bring dwarves back | ||||||||||
Additional Information | Not sure if having the dwarf have any tasks affects things: I tried disabling most, dwarf just idles. Maybe it has to do with a messenger at an occupied site? | ||||||||||
Tags | No tags attached. | ||||||||||
Attached Files | |||||||||||
Notes | |
(0038483) lethosor (manager) 2018-06-25 13:44 |
A save (http://dffd.bay12games.com/ [^]) would be helpful for this one too. |
(0038489) noxiilarxene (reporter) 2018-06-26 19:05 |
http://dffd.bay12games.com/file.php?id=13848 [^] Apologies on the delay, I accidentally deleted the save so I had to make a new one. TW: Offensive fort/group name. |
(0038491) noxiilarxene (reporter) 2018-06-26 19:37 |
Alright, so I played it for a few minutes. Messenger has no assigned jobs, not even hauling. Messenger shows "No Job" but still proceeds off the edge of the map. Maybe the problem is that the mission isn't being assigned as the messenger's job, allowing other labors to take precedence. |
(0038498) Loci (manager) 2018-06-27 16:59 |
Using the save, I sent the messenger Udil Postmaw to Wilthonor. He proceeded to exit the fortress and walk 10 or so tiles with "No job", then turn around and return to the fortress to Sleep. After his nap, his second attempt to leave the site, still with "No job", was successful. |
(0038500) noxiilarxene (reporter) 2018-06-27 17:51 |
That does match my observations. It shouldn't show "No Job", right? |
(0038505) Loci (manager) 2018-06-28 13:58 |
I'm not sure what job text is intended, however having the mission interrupted by non-critical needs seems buggy to me. |
(0038506) noxiilarxene (reporter) 2018-06-28 14:01 |
Probably "Request Workers from Wilthonor" or similar. |
(0038535) Toady One (administrator) 2018-07-04 20:16 |
I've updated the broken text. We'll see if priorities also need to be changed once people have the text to diagnose with. |
(0039150) Loci (manager) 2019-01-25 11:52 |
v0.44.12: Messengers still prefer to perform other jobs instead of carrying messages. One such messenger has dumped ~ 5 items and performed multiple 'store in stockpile' tasks. The "Make request" job does active briefly, but it is quickly replaced by higher-priority refuse hauling jobs. |
(0039948) noxiilarxene (reporter) 2020-02-07 19:47 |
Seems to mostly work in 47.02 but can't confirm fix, accidental or otherwise, without larger forts with messengers |
(0039949) Talvieno (reporter) 2020-02-07 20:06 |
I've had it work twice. It might be fixed. |
(0040140) Loci (manager) 2020-02-20 12:13 |
v0.47.03: Messengers still prefer to haul refuse, store seeds, and install furniture instead of carrying a message. Since message-carrying is a task directly assigned by the player, I'm of the opinion that it should at least take precedence over unskilled labors. Comparatively, militia dwarves will ignore all labors except personal needs when assigned a mission. |
Issue History | |||
Date Modified | Username | Field | Change |
2018-06-23 17:34 | noxiilarxene | New Issue | |
2018-06-25 13:44 | lethosor | Note Added: 0038483 | |
2018-06-26 19:05 | noxiilarxene | Note Added: 0038489 | |
2018-06-26 19:37 | noxiilarxene | Note Added: 0038491 | |
2018-06-27 16:59 | Loci | Note Added: 0038498 | |
2018-06-27 16:59 | Loci | Assigned To | => Loci |
2018-06-27 16:59 | Loci | Status | new => confirmed |
2018-06-27 17:51 | noxiilarxene | Note Added: 0038500 | |
2018-06-28 13:58 | Loci | Note Added: 0038505 | |
2018-06-28 14:01 | noxiilarxene | Note Added: 0038506 | |
2018-07-04 20:16 | Toady One | Note Added: 0038535 | |
2018-07-04 20:16 | Toady One | Status | confirmed => resolved |
2018-07-04 20:16 | Toady One | Fixed in Version | => Next Version |
2018-07-04 20:16 | Toady One | Resolution | open => fixed |
2018-07-04 20:16 | Toady One | Assigned To | Loci => Toady One |
2019-01-25 11:52 | Loci | Note Added: 0039150 | |
2019-01-25 11:52 | Loci | Status | resolved => acknowledged |
2019-01-25 11:54 | Loci | Priority | urgent => normal |
2019-01-25 11:54 | Loci | Severity | major => minor |
2019-01-25 11:54 | Loci | Resolution | fixed => open |
2019-01-25 11:54 | Loci | Fixed in Version | 0.44.12 => |
2020-02-07 19:47 | noxiilarxene | Note Added: 0039948 | |
2020-02-07 20:06 | Talvieno | Note Added: 0039949 | |
2020-02-20 12:13 | Loci | Note Added: 0040140 |
Copyright © 2000 - 2010 MantisBT Group |