Anonymous | Login | Signup for a new account | 2024-10-08 09:21 PDT |
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 | |
0007754 | Dwarf Fortress | Dwarf Mode -- Military | public | 2014-07-30 22:20 | 2016-10-05 19:25 | |
Reporter | FDoKE | |||||
Assigned To | Loci | |||||
Priority | normal | Severity | major | Reproducibility | always | |
Status | resolved | Resolution | duplicate | |||
Platform | PC | OS | Windows | OS Version | Windows 7 | |
Product Version | 0.40.05 | |||||
Target Version | Fixed in Version | |||||
Summary | 0007754: Dwarwes don't shoot through fortification (or don't stand close to it?) | |||||
Description | I builded a tower and surround it with fortification (also it can be a room that surrounded by fortificaions your dwarwes - outside, enemies inside that box) and found one thing - dwarwes don't shoot from the tower (outside) unless they stand right in front of fortification, the problem is that almost all dwarwes (8/10?) standing in the middle of the tower or if you set stand command near fortification only 2-3 dwarwes will be stand near fortification and shoot, others will just stand and do nothing... Is there a way to order dwarwes to stand right in front of fortifications? Or they should fire not just in front of it? My Forgotten beast catcher(F - fortification, X - wall, D - door, V - dwarf1, B - dwarf2, F - forgotten beast, S - stand command): XXXXXXXXXXXX .....V.....X ......S.B..X ...XFFFFFFFX ...D.......X ...X...F.... XXXXXXXXXXXX So the problem is that dwarf "V" will not shoot, but the dwarf "B" will, while forgotten beast destroying a door. And almost half of the all dwarwes will not shoot because of it. | |||||
Tags | No tags attached. | |||||
Attached Files | ||||||
Relationships | ||||||
|
Notes | |
(0028006) Aisher (reporter) 2014-07-30 22:49 |
they do shoot trough if their skill allow, otherwise not. check wiki for details |
(0028008) MornieOhtar (reporter) 2014-07-31 00:44 edited on: 2014-07-31 01:15 |
Aisher, I think the problem is different. In case mentioned in original bug, dwarf V can simply go closer to the fortification, if his skill doesn't allow to shoot from distance. I had same issue a lot of time... mostly all my defence is a bridge to close my fortress and fortifications in +1 z-level for archers. Let's say FFFFFFFFFFFFFFFF F...x...............F F....................F And so on in form of square. Here, x is order for my archers squad to station. Even if it's just after fortifications, I need to be very lucky to get at last some dwarf close enough to it to shoot (well, actually skilled enough dwarves are shooting, but others don't). The question is... Is there any way to tell those, who doesn't skilled enough to come closer? Will not this exact situation be a bug, when soldiers have no reason to avoid combat (they not horrified, not injured and ambushers don't even shoot back as they don't have archers)? (Well, order to kill goblin or something other, that come close to fortification doesn't work either... Actually, this order is fully ignored in my case, but this'll be other bug if a bug at all - need to investigate further). PS. I still use 34.11, but as I can see 40.05 still have this issue. Hmmm... Okay, seams to me that this is a dublicate of 0002697. |
(0028014) splitcorez (reporter) 2014-07-31 01:51 |
>The question is... Is there any way to tell those, who doesn't skilled enough to come closer? Will not this exact situation be a bug, when soldiers have no reason to avoid combat (they not horrified, not injured and ambushers don't even shoot back as they don't have archers)? Only workaround I've found is to build towers with 1 tile width hallways so the marksdwarves are forced to walk next to fortifications. |
(0028015) MornieOhtar (reporter) 2014-07-31 02:15 |
> Only workaround I've found is to build towers with 1 tile width hallways so the marksdwarves are forced to walk next to fortifications. It's writen on 0002697:0011627 in bug mentioned by me earlier. But as I can see, this still counted as a bug and probably needs to be fixed. As for me, checked this workaround and it worked. Might propose to original reported to test to be sure that this is the case (as long as exists 'related' to it), add proper relations and close as duplicate. |
Issue History | |||
Date Modified | Username | Field | Change |
2014-07-30 22:20 | FDoKE | New Issue | |
2014-07-30 22:49 | Aisher | Note Added: 0028006 | |
2014-07-31 00:44 | MornieOhtar | Note Added: 0028008 | |
2014-07-31 00:45 | MornieOhtar | Note Edited: 0028008 | View Revisions |
2014-07-31 01:15 | MornieOhtar | Note Edited: 0028008 | View Revisions |
2014-07-31 01:51 | splitcorez | Note Added: 0028014 | |
2014-07-31 02:15 | MornieOhtar | Note Added: 0028015 | |
2016-10-05 19:25 | Loci | Relationship added | duplicate of 0002697 |
2016-10-05 19:25 | Loci | Status | new => resolved |
2016-10-05 19:25 | Loci | Resolution | open => duplicate |
2016-10-05 19:25 | Loci | Assigned To | => Loci |
Copyright © 2000 - 2010 MantisBT Group |