View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006623 | The Dark Mod | AI | public | 23.05.2025 09:18 | 23.05.2025 09:19 |
| Reporter | Jnon | Assigned To | |||
| Priority | normal | Severity | normal | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | x86_64 | OS | Ubuntu | OS Version | 22.04.1 |
| Product Version | TDM 2.13 | ||||
| Summary | 0006623: Patrolling AI Ignore absence_alert spawnargs | ||||
| Description | In TDM 2.12, AI would enter an alert state when absence_alert (and absence_alert_increase) flags were placed on objects in the map which were subsequently moved or stolen. In TDM 2.13, AI no longer seem to respond to these flags. This was initially noticed in during testing of a map created in DarkRadiant, and was further confirmed in a test map created for the purpose of isolating the behavior. In both cases, the map was made in DarkRadian 3.9.2 amd64. A Loot entity was placed with the flags "absence_noticeability 1" and "absence_alert_level 23" (which should be "agitated searching". Running the map in TDM 2.12 results in agitated searching behaviour as expected. In 2.13, the patrolling AI does not react to the missing loot entity and simply continues patrolling with no change in suspicion level, or even barks indicating a reaction. | ||||
| Steps To Reproduce | 1) Create a map in DarkRadiant, placing a loot entity in the path of a patrolling AI with "absence_noticeability 1" and "absence_alert_level 23" spawnargs on said loot entity 2) Run the map in TDM v2.13 3) Steal the loot entity without being detected by the AI, then observe its behaviour during patrol 4) AI will not react Following the first three steps in TDM v2.12 reliably results in Step 4 being "AI increases suspicion" as expected. | ||||
| Additional Information | I started a forum thread of my initial encounter with this problem: https://forums.thedarkmod.com/index.php?/topic/22732-absence_noticeability-spontaneously-stopped-working/ While I have reliably reproduced this error on more than one map on my own system, I have yet to hear of this being reproduced by others, so I cannot rule out that some factor on my own system is causing this error. However, before upgrading TDM to 2.13 this behaviour did not occur, so it still seems likely this is related to the new version. I would very much like to confirm whether or not this can be reproduced by others. | ||||
| Tags | 2.12, 2.13, absence_alert_level, absence_noticeability | ||||
| Attached Files | |||||
 |
Addendum: Forgot to mention, the test map I created to reproduce the bug is attached to this issue as "absence_notice_test.zip". File contains a simple map that should demonstrate the problem behaviour if steps for reproduction are followed in TDM 2.13 and 2.12 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 23.05.2025 09:18 | Jnon | New Issue | |
| 23.05.2025 09:18 | Jnon | Tag Attached: 2.12 | |
| 23.05.2025 09:18 | Jnon | Tag Attached: 2.13 | |
| 23.05.2025 09:18 | Jnon | Tag Attached: absence_alert_level | |
| 23.05.2025 09:18 | Jnon | Tag Attached: absence_noticeability | |
| 23.05.2025 09:18 | Jnon | File Added: absence_notice_test.zip | |
| 23.05.2025 09:19 | Jnon | Note Added: 0017030 |
