View Issue Details

IDProjectCategoryView StatusLast Update
0001836Infinitode 2[All Projects] Infinitode 2public2024-03-06 15:10
Reporteroct0 Assigned Totherainycat  
PrioritylowSeverityminorReproducibilitysometimes
Status resolvedResolutionfixed 
PlatformMobileOSAndroidOS VersionAny
Product Version 
Target Version1.9.0 (Season 3)Fixed in Version1.9.0 (Season 3) 
Summary0001836: 2nd poison tower doesn't re-target to apply multiple stacks of poison.(target priority set to "first")
Description

The current behavior of the venom tower is that it will re-target to apply poison to any enemy in range that doesn't have it, until all targets in range have a stack of poison from that tower. Additionally you can apply multiple stacks of poison from other venom towers, with diminishing returns from each tower.

However, the issue I have found is that a second venom tower will only target un-poisoned enemies or the first enemy in line if all enemies in range already have a stack of poison. This is not in-line with the new auto targeting behavior introduced with the new version as it is not spreading a 2nd stack of poison to all enemies, only the first one in line.

Steps To Reproduce

Load up a game and place two venom towers some distance apart so the effect is more easily observable, but not so far that the poison effect from the first tower expires. Ideally they are spaced such that the wave of enemies is poisoned when entering the range of the 2nd tower and stay poisoned throughout so you can see which are receiving 2 stacks and which aren't.
Unfortunately you must wait until a wave where the enemies have enough HP where they aren't dying immediately after receiving the 2nd stack of poison, and the 2nd tower has ample time to re-target(which it won't).

TagsNo tags attached.

Activities

oct0

oct0

2021-08-19 17:58

reporter   ~0001732

reproducibility should be "sometimes" instead of "always", doing more tests.

therainycat

therainycat

2023-12-20 22:53

administrator   ~0002167

Has to be reproduced in 1.9 beta before I can change this issue's status

Issue History

Date Modified Username Field Change
2021-08-18 23:34 oct0 New Issue
2021-08-19 17:58 oct0 Note Added: 0001732
2021-12-19 19:48 therainycat Priority high => normal
2021-12-29 16:31 therainycat Reproducibility always => sometimes
2021-12-29 16:31 therainycat Assigned To => therainycat
2021-12-29 16:31 therainycat Status new => acknowledged
2022-01-18 21:43 therainycat Priority normal => low
2023-03-17 22:44 therainycat Status acknowledged => assigned
2023-03-18 00:00 therainycat Target Version => 1.8.8
2023-03-30 02:17 therainycat Target Version 1.8.8 => 1.9.0 (Season 3)
2023-12-20 22:52 therainycat Project Infinitode 2 => Infinitode 2 v.1.9 Beta
2023-12-20 22:53 therainycat Status assigned => feedback
2023-12-20 22:53 therainycat Note Added: 0002167
2023-12-20 22:59 therainycat Project Infinitode 2 v.1.9 Beta => Infinitode 2
2024-03-06 15:10 therainycat Status feedback => resolved
2024-03-06 15:10 therainycat Resolution open => fixed
2024-03-06 15:10 therainycat Fixed in Version => 1.9.0 (Season 3)