0010318: Dwarves report incorrect region rumors locally

Dwarf Fortress Bug Tracker - Dwarf Fortress

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0010318

Dwarf Fortress

Civilizations/Entities -- General

public

2017-11-01 05:11

2017-11-02 04:33

Reporter

FantasticDorf

Assigned To

Knight Otu

Priority

normal

Severity

minor

Reproducibility

always

Status

resolved

Resolution

duplicate

Platform

OS Version

Product Version

0.40.24

Target Version

Fixed in Version

Summary

0010318: Dwarves report incorrect region rumors locally

Description

Dwarves make mention of monsters & animals particularly in 'rumors' circulated between themselves with 'trobules' being present in the local region that aren't possible.

Though some megabeasts may travel & settle in hidden caves within the territory you're settled in, normal named animals & Titans cannot move outside of their biome ranges into yours.

Armies also in adjacent biomes to dwarven territory are mentioned as being in the local region of the player fortress with dwarves discussing their presence (even though the battle happened the next biome over)

Steps To Reproduce

Log the conversations that occur between dwarves with [REGULAR CONVERSATION A_D:D_D] in announcement txt. They will periodically talk about threats filtered into announcements, parse through the information in-game or afterwards on the game log.

Embark in a biome with very little wildlife/monsters, listen closely for mentions of exotic monsters within your regional territory that are actually happening back in central dwarven territory.

Save, backup & retire the fortress when you have enough logs and return to legends mode, all of the threats listed appropriate to your region can be found there & find the mentioned monsters in legends mode to track their doings.

Additional Information

I have seen this behaviour in versions 40.13 & 40.12 one such example where a named dingo was mentioned to be in the regional vicinity of my tundra embarkation even though that is grossly outside of its biome.

Possibly fixed on testing the latest version 43.05 but worth mentioning incase it is not or the reporting of the regions remains inconsistent.