East facing advanced turtles.
hugeblank opened this issue · 11 comments
When an advanced turtle is blown up facing the east, it turns north. When right clicked, it will resume facing east. A very minor bug, but nevertheless, an intresting one.
Advanced turtles aren't supposed to be able to be blown up.. What did you
use to explode it?
On 22 Dec 2015 00:17, "hugeblank" [email protected] wrote:
When an advanced turtle is blown up facing the east, it turns north When
right clicked, it will resume facing east A very minor bug, but
nevertheless, an intresting one—
Reply to this email directly or view it on GitHub
#73.
You literally just said "is blown up". How did you trigger this bug?
On 22 Dec 2015 00:19, "hugeblank" [email protected] wrote:
It doesn't blow up.
—
Reply to this email directly or view it on GitHub
#73 (comment)
.
Yea, I misspoke... I placed a turtle down facing east with TNT next to it. triggered the TNT, and once it exploded it immediately turned north.
Reproduction steps:
- Place a turtle with a peripheral (Mining works best visually)
- Detonate TNT or creeper next to turtle.
- Turtle will visually turn into peripheral-less version facing north
- Any update to turtle (Like r-click) will make it restore to normal version.
This is also a trigger for #62 (monitors bugging out until re-chunkloaded) - the key seems to be that blocks in the area have to actually be changed (filling the same area with the same blocks twice won't achieve that, for eg, which may be why PokemonInLua later believed his report to be fixed).
Planting a large collection of TNT blocks in an enclosed space underground is more effective then firing off a single one directly next to actual turtles (which are blast-proof), though some level of proximity seems to be required (presumably "same chunk").
The original facing of the turtle doesn't seem to matter.
Here's a reproduction script for a command computer:
Before running it, label the command computer (!), and place some turtles, other computers, and some multiblock monitors around it (within the same chunk). It'll perform some block changes in an area about five blocks above, which should trigger the fault within a few seconds.
Confirmed in 1.77pr0 using with BombBloke code from 2 post up.
This and #62 seem to be same issue.