Talk:Camo detection: Difference between revisions
Latest comment: 19 September 2025 by Polavux in topic BTD5 generation table should be split.
Planterror (talk | contribs) →BTD5 generation table should be split.: new section |
|||
| Line 2: | Line 2: | ||
Between the features in BTD5, Battles and BMC, I believe it's correct to split these tables per game instead of per generation. For example, Engineer has sentries at Level 3 MK in BMC see camo, or Battles having the camo detection turbo charge ability, compared to BTD5 where specialty buildings allow ice to decamo. [[User:Planterror|Planterror]] ([[User talk:Planterror|talk]]) 16:39, 19 September 2025 (UTC) | Between the features in BTD5, Battles and BMC, I believe it's correct to split these tables per game instead of per generation. For example, Engineer has sentries at Level 3 MK in BMC see camo, or Battles having the camo detection turbo charge ability, compared to BTD5 where specialty buildings allow ice to decamo. [[User:Planterror|Planterror]] ([[User talk:Planterror|talk]]) 16:39, 19 September 2025 (UTC) | ||
:I agree. [[Range]] and [[pierce]] do the same thing. [[User:Polavux|po]]●[[User talk:Polavux|la]]●[[Special:Contributions/Polavux|vux]] 20:09, 19 September 2025 (UTC) | |||
Latest revision as of 20:09, 19 September 2025
BTD5 generation table should be split.
[edit source]Between the features in BTD5, Battles and BMC, I believe it's correct to split these tables per game instead of per generation. For example, Engineer has sentries at Level 3 MK in BMC see camo, or Battles having the camo detection turbo charge ability, compared to BTD5 where specialty buildings allow ice to decamo. Planterror (talk) 16:39, 19 September 2025 (UTC)