View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003279 | Dwarf Fortress | Dwarf Mode -- Jobs, Mechanisms | public | 2010-09-19 08:46 | 2010-11-15 11:34 |
| Reporter | Thoranius | Assigned To | Logical2u | ||
| Priority | low | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Platform | Custom Built PC | OS | Windows 7 Home | OS Version | Premium 64-bit |
| Product Version | 0.31.13 | ||||
| Summary | 0003279: The lever/cage/2 mechanism method for releasing caged creatures destroys 1 mechanism. | ||||
| Description | When using the lever and mechanism attachment method to remotely open cages to safely kill cage-trapped untamed creatures (or sentients) seems to always result in the net loss of one of the mechanisms used in the linking of the lever to the cage. (I apologize if this is an intended game mechanic, but you would assume when the cage opens when the lever is triggered, both the connecting mechanism and the opening mechanism would fall the the ground as the cage opens, leaving both mechanisms loose but intact). Can get really annoying if you neglect to 'forbid' an artifact mechanism, and use it because you failed to expand the list to doublecheck each mechanisms artifact status before use. | ||||
| Steps To Reproduce | Build a lever and a cage, link them through the lever's tasks with 2 mechanisms, activate with a dwarven pull, count remaining items. | ||||
| Additional Information | Again, I apologize if this is indeed an intended behaviour, but it seemed more like a potential bug to me, so I figured I'd better post it. | ||||
| Tags | Not a bug | ||||
|
|
Remember that linking a cage to a lever uses 2 mechanisms - one in the cage, and one in the lever. Thus, when you pull the lever to deconstruct the cage, you only regain the mechanism that was used in the cage. However, when you get around to deconstructing the lever itself, you'll regain all of the other mechanisms. It's always been this way, and it's even explicitly documented on the wiki. |
|
|
Ah, my apologies, I failed to find the relevant info on it on either the cage or lever pages, didn't see it squirreled away there on the mechanisms page. However, once I did get around to deconstructing the lever (on a different project, a floodgate synchronization issue involving many rebuilds and relinks to try and solve, for some odd reason), the end result of mechanisms recieved when finally scrapping the whole thing and starting again from scratch was only two mechanisms,although I must of deconstructed one of the two floodgates at least 5 times before giving up. I'll go and test it again, if the floodgates fail to sync again. However, on a side note, this is a 31.12 save ported into the 31.13 version, so it could just be a side effect similar to the bedroom placing issue. |
|
|
Ok, please report back here once you've tested it again. In the meantime I'll test it in my world, too. Edit: My testing shows that no mechanisms are lost. I had the following setup. 1 Lever + 1 Mechanism from previous linkage + 1 Mechanism from current linkage 1 Cage, linked. Pulling the lever, I obtained the mechanism in the cage. Deconstructing the lever I obtained the other three mechanisms, for a total of four. |
|
|
I haven't had any problems as well, using 31.12. I captured a flesh ball in a cage and wanted to have my military get some sparring time in on it. I built the cage in the arena. Built a lever outside the arena which uses one mechanism. Linked lever to cage which uses two mechanisms. Cage is now made up of an iron cage and iron mechanism, lever is now made up of two iron mechanisms. Pull lever, cage deconstructs into cage and mechanism sitting on floor. Deconstruct lever and it results in two mechanisms sitting on floor. Started with a cage, flesh ball, and three mechanisms. Ended up with a cage, flesh ball with a very long name, three mechanisms, and ten dead dwarves. :( |
|
|
Reminder sent to: Thoranius Do you have any updates, Thoranius? |
|
|
It must of been a carryover issue carrying a save file over from a previous version, I have as of yet been able to repeat the phenomenon. Thanks for the advice as to the situation, though. |
|
|
Marking as no-change-required, then. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-09-19 08:46 | Thoranius | New Issue | |
| 2010-09-19 08:51 | Quietust | Note Added: 0012815 | |
| 2010-09-19 08:52 | Quietust | Note Edited: 0012815 | |
| 2010-09-19 22:01 | Thoranius | Note Added: 0012832 | |
| 2010-09-23 08:02 | Logical2u | Note Added: 0012919 | |
| 2010-09-23 08:26 | Logical2u | Note Edited: 0012919 | |
| 2010-09-23 08:26 | Logical2u | Tag Attached: AWAITING UPDATE | |
| 2010-09-23 08:58 | hyndis | Note Added: 0012920 | |
| 2010-10-02 15:25 | Logical2u | Note Added: 0013154 | |
| 2010-10-19 22:18 | Thoranius | Note Added: 0013419 | |
| 2010-10-20 01:41 | Naros | Tag Attached: Not a bug | |
| 2010-11-15 09:56 | Logical2u | Note Added: 0013874 | |
| 2010-11-15 09:56 | Logical2u | Status | new => resolved |
| 2010-11-15 09:56 | Logical2u | Resolution | open => no change required |
| 2010-11-15 09:56 | Logical2u | Assigned To | => Logical2u |
| 2010-11-15 09:56 | Logical2u | Tag Detached: AWAITING UPDATE |
