Turtle.place doesn't reliably place blocks facing the same direction. Seems to be based on movement of turtle before placing. I haven't found anything in change logs or forums so I can only assume its a bug. I've tested both 1.76pr8 and 1.75.

[testing code]
turtle.select(1)

turtle.down()
turtle.place()

for i = 1, 2 do
turtle.up()
turtle.place()
end

[result]

Is this intended? Blocks seem to face the opposite direction.

Placement rules (for forward placement) are as follows:
If there is a block directly in front of turtle, it places onto that.
Else, if there is a block below the space in front, it places down onto
that.
Else, if there is a block behind the space in front, it places across onto
that.

Does this match your observations?
On 22 Dec 2015 16:58, "peon2" [email protected] wrote:

Turtleplace doesn't reliably place blocks facing the same direction Seems
to be based on movement of turtle before placing I haven't found anything
in change logs or forums so I can only assume its a bug I've tested both
176pr8 and 175

[testing code]
turtleselect(1)

turtledown()
turtleplace()

for i = 1, 2 do
turtleup()
turtleplace()
end

[result]
[image: 2015-12-22_16 55 08]
https://camo.githubusercontent.com/c311abd1e0ff0f5f970838f7e042dce82608089b/68747470733a2f2f636c6f756467697468756275736572636f6e74656e74636f6d2f6173736574732f31363430333435302f31313936303934302f33326265626531362d613863642d313165352d386338382d363230326166396235333565706e67

—
Reply to this email directly or view it on GitHub
#76.

Oh: if there's no blocks nearby, it places backwards onto itself.

So because there is nothing underneath the first set of blocks they place backwards, but since the second and third layers have blocks underneath them they place normally. Thanks for the clarification!

No worries, glad to be of help