View Issue Details

IDProjectCategoryView StatusLast Update
0011268Dwarf FortressAdventure Mode -- Movementpublic2020-02-05 20:10
ReporterPyoro64 Assigned ToToady One  
PrioritynormalSeverityminorReproducibilitysometimes
Status resolvedResolutionfixed 
PlatformPCOSWindowsOS Version10
Product Version0.47.01 
Fixed in Version0.47.02 
Summary0011268: Mount controls direction of the adventurer after fast traveling while mounted
DescriptionIf you fast travel while mounted, and stop, pressing any direction will instead advance time by one turn. All movement is controlled by the mount. If it wants to stay still, pressing a direction will do nothing. If it goes somewhere, you go with it, regardless of any buttons pressed. Dismounting puts you back in control of yourself, but re-mounting does not resolve the issue. This problem began to occur after some time was spent playing. It does not happen immediately after creating a new adventurer.

After a random number of directional inputs, you regain control of your mount.
Steps To ReproduceIn the case of the save included, simply fast traveling while mounted will cause the issue reported.
Additional InformationFile save: http://dffd.bay12games.com/file.php?id=14698
TagsNo tags attached.

Activities

nautical

2020-01-31 20:05

reporter   ~0039749

I've had similar experiences.

Sean Mirrsen

2020-02-01 06:47

reporter   ~0039761

I've had this experience as well, however I don't think it's an issue. The mount (horse in my case) is perfectly responsive after travelling, unless it is panicking. Upon, i.e., seeing a hostile creature.

If there's an issue, it would be if increasing the Riding skill doesn't reduce or remove the instances where the mount gets out of your control. Or if acquiring some kind of trained mount (or training it yourself) doesn't reduce that reaction's frequency.

Pyoro64

2020-02-02 11:40

reporter   ~0039809

Upon more play time, I have noticed that when your mount is panicking and out of control, the color of the mount's speed text will be blue. This is not the case with this bug.

Issue History

Date Modified Username Field Change
2020-01-31 19:58 Pyoro64 New Issue
2020-01-31 20:05 nautical Note Added: 0039749
2020-02-01 06:47 Sean Mirrsen Note Added: 0039761
2020-02-02 11:40 Pyoro64 Note Added: 0039809
2020-02-05 20:10 Toady One Status new => resolved
2020-02-05 20:10 Toady One Fixed in Version => Next Version
2020-02-05 20:10 Toady One Resolution open => fixed
2020-02-05 20:10 Toady One Assigned To => Toady One