-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fortress mode - 'follow dwarf' not working properly #16
Comments
I can verify this. I originally thought this was an DF issue so did not report it. This can be consistently re-produced. Seems to happen whenever centering on a unit. |
Does it not work in the latest version (5.20 at least)? I thought I've fixed this. |
Oh ok, I played twbt 5.17 ! Thanks for the hint, i'll check later and report back if there's still any problem |
My apologies, didn't notice that following was fized. I probably skipped some forum post where this was mentioned. Also double apology for commenting on a duplicate ticket. I just saw the email notification and proceeded to comment, heh. However, when you go to unit list by pressing u and then zoom to a creature by pressing z to go to the unit, it does not center the screen on the unit, but it stays on the edge of the screen. Is this something Dwarf Fortress itself does or a TWBT bug? |
Yep, (z)oom is harder to fix. I think I have one idea now, I'll try. |
Also to point out, it happens not only directly with (z)oom, but also when game itself zooms, like when someone get strange mood. |
Did you close it since it was fixed? |
(z)oom is fixed in 5.47 just now, for automatic zoom on announcements I'll create a separate issue. |
twbt kind of messes up the follow object/dwarf (k on dwarf -> f) function.
if I try to follow a dwarf with twbt activated, the screen isn't centered on that dwarf you follow as it should be normally.
When twbt is deactivated the follow function works properly again.
if anyone has a workaround please write here, as I love to follow these dwarves around.
The text was updated successfully, but these errors were encountered: