Talk:Towercap

Incorrect data about cave-ins

>Caution: Chopping towercap will immediately cause a cave-in to occur if they have prevented a cave in, even if all tiles are supported by other supports

This seems to be incorrect. I've planted a bunch of towercaps without treeplanter's pot, chopped down stunted ones, and some did cause cave-in even though they haven't prevented any. Drathvedro (talk) 19:59, 15 October 2022 (UTC)

Questions that come to my mind:

- How did you know no cave-in's where prevented ? (assuming natural clear area)

- How did you know where all the "cavein-trigger" tiles where ? (if it was a natural clear area)

Else it makes sense that the chopping towercaps that did not trigger a cave-in just had no "cavein-trigger" tiles inside there mine-support range. And those that did trigger a cave-in did.

(assuming chopped towercaps only scan inside there active mine-support range for "cavein-trigger" tiles. And that there is always a chance a in-range "cavein-trigger" tile might be triggered by this action - Dev's love to use randomization where possible.)

--.MvGulik. 20:48, 16 October 2022 (UTC)

Yeah, this is basically a wording issue. What I've meant is that, from reading the caution, I've assumed that if you don't mine out any cavein-triggering tiles within towercaps radius (or don't mine anything at all), then it would be completely safe to chop them down. But it does sometimes cause caveins in some random clear areas. My bet is on that it only checks whether there are any cavein-triggering tiles within the radius, no matter if they were ever mined out or not, or even been mineable at all. Gotta test it a bit more the next time I plant them Drathvedro (talk) 23:10, 19 October 2022 (UTC)

It might be potentially useful if someone tries to probe the dev's on what trigger-tiles settings(if any) might be in the game. Any additional data could potentially lower the testing amount needed to pry out more unambiguous behaviors/features. --.MvGulik. 11:59, 20 October 2022 (UTC)