View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007265 | Dwarf Fortress | Adventure Mode -- General | public | 2014-07-14 01:47 | 2014-07-18 09:02 |
| Reporter | SmileyMan | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | x64 | OS | Windows | OS Version | 7 |
| Product Version | 0.40.03 | ||||
| Summary | 0007265: Conversation filter does not match kill/conflict summaries | ||||
| Description | While attempting to tell a lord about my killing of the beast that had been terrorizing the town, I typed in the beast's name as filter. Several attack rumours were returned, but the important rumour about me slaying him was not. | ||||
| Steps To Reproduce | 1) Kill a creature, noting the name 2) Start a conversation with someone, and select to talk about a specific rumour or incident 3) Type in the name of the killed creature as a filter Some attacks will be highlighted because they have matched the creature name, others will not | ||||
| Tags | No tags attached. | ||||
|
|
Save uploaded to http://dffd.wimbli.com/file.php?id=8959 1) Load adventurer save 2) Continue current conversation with Lord 3) Bring up a specific incident or rumour 4) Type 'LOKU' to filter on slain beast's name. 5) Note that several combats are highlighted, but the actual slaying of the beast is not highlighted, and can only be found several pages down |
|
|
Can confirm that this happened to me in 40.01. Do we need another save? |
|
|
I'd like to second/third this, and mention a related thing I noticed: when looking at historical figures in Legends, words like 'vampire' or 'dragon' didn't return results (race presumably not included in the filterable words list). For Legends, it would be convenient to be able to check the total number of a type of NPC (and go through their information one by one); for conversations, it would be convenient to be able to first scare someone with a chilling rumour, then boast about having resolved it (getting both to the top of the conversation list by name-filtering). Edit: Checking other conversation-related issues (such as 7183) I note 'Please post suggestions in the Suggestions forum', so for this I should probably stress {the incompleteness of the current filter options as something to be fixed} rather than {the convenience once it is fixed}. |
|
|
Multipartite: yes, this seems possibly unintentional. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2014-07-14 01:47 | SmileyMan | New Issue | |
| 2014-07-14 02:00 | SmileyMan | Note Added: 0026299 | |
| 2014-07-14 02:45 | clanl | Note Added: 0026303 | |
| 2014-07-14 02:49 | SmileyMan | Note Edited: 0026299 | |
| 2014-07-14 03:58 | Multipartite | Note Added: 0026307 | |
| 2014-07-14 04:21 | Multipartite | Note Edited: 0026307 | |
| 2014-07-14 12:27 |
|
Summary | Conversation filter does not match kills => Conversation filter does not match kill/conflict summaries |
| 2014-07-18 09:02 |
|
Note Added: 0026871 |
