budzilla wrote:also, what is the difference between when .01 and .02 etc dust falls?
jorb wrote:Ideally the game should play itself.
ricky wrote:budzilla wrote:also, what is the difference between when .01 and .02 etc dust falls?
if you've ever played minesweeper, the number of cavedust dropped represents the number of adjacent tiles that will cause a cavein.
ricky wrote:budzilla wrote:also, what is the difference between when .01 and .02 etc dust falls?
sorry i cant answer your first question - but i can answer this
if you've ever played minesweeper, the number of cavedust dropped represents the number of adjacent tiles that will cause a cavein.
Sprymazi wrote:This can't be true or it's bugged.
I mined a tile that had 0.1 cavedust in it and there was 5 tiles that were possible to mine around it since it was dug straight into a cave wall. I gambled on the next one straight forward and it was safe and also dropped 0.1 cavedust. So 4 possible tiles left for a cave-in from the first tile. Third tile i dug into was straight in and caused a cave-in. So the amount of cavedust doesn't indicate how many tiles are cave-ins.
#1
X 1 X
X X X
#2
X 1 X
X 1 X
X C X
jorb wrote:Ideally the game should play itself.
ricky wrote:one explanation i can think of is that the first tile you mined (the cave wall) was detecting a cave-in tile on one of the three non-minable (cave floor) tiles, but is that a bug? can cave floor tiles cave in in the off chance you build/destroy a mine support there?
#1
X 1 X
X X X
#2
F F F
X 1 X
X 1 X
B C B
MagicManICT wrote:Sprymazi wrote:This can't be true or it's bugged.
I mined a tile that had 0.1 cavedust in it and there was 5 tiles that were possible to mine around it since it was dug straight into a cave wall. I gambled on the next one straight forward and it was safe and also dropped 0.1 cavedust. So 4 possible tiles left for a cave-in from the first tile. Third tile i dug into was straight in and caused a cave-in. So the amount of cavedust doesn't indicate how many tiles are cave-ins.
You probably did it wrong, but there very well could be a bug, too. A visualization might help. This is what you ended up with, C being the collapsing tile?
- Code: Select all
#1
X 1 X
X X X
#2
X 1 X
X 1 X
X C X