Jump to content




Piston placement


  • You cannot reply to this topic
13 replies to this topic

#1 joebodo

  • Members
  • 69 posts

Posted 20 April 2014 - 10:11 PM

Version 1.6 included a change to the way pistons are placed by turtles. In the 1.6 version, the turtle can only place a piston with the piston head facing upwards. Prior to 1.6, the piston head faced in the direction the turtle was heading.

The piston can be very useful for turtles to manipulate other blocks. I currently use a piston to maneuver blocks into the correct locations for a schematic builder. Due to the changes in 1.6, I can no longer use this method.

I would like to see the following changed, if possible, for piston placement:

placeUp: piston head is pointing up
placeDown: piston head is pointing down
place: piston head is furthest away from the turtle

Please consider.
Thanks

#2 Cranium

    Ninja Scripter

  • Moderators
  • 4,031 posts
  • LocationLincoln, Nebraska

Posted 03 May 2014 - 09:09 AM

I do actually hope this gets implemented, because while it's now 100% predictable...it's not really helpful.

Good new to anyone wondering, most wrenches from other mods can change the direction of the pistons, and turtles can use those wrenches with turtle.place().

#3 electrodude512

  • Members
  • 167 posts
  • LocationEastern USA

Posted 05 May 2014 - 07:34 PM

The fact that wrenches can turn pistons is probably the reason that making pistons always face up was a viable option.

#4 awsmazinggenius

  • Members
  • 930 posts
  • LocationCanada

Posted 05 May 2014 - 08:45 PM

What about making this so that it works on all blocks with an orientation, not just pistons?

#5 KingofGamesYami

  • Members
  • 3,002 posts
  • LocationUnited States of America

Posted 17 May 2014 - 04:12 AM

What about making this:
turtle.place($optional_argument$)
turtle.place("up")
turtle.place('down')
turtle.place('back')
turtle.place('right')
turtle.place('left')
turtle.place('forward')
--#if no argument supplied, automatically places up
--#optional argument is ignored if block does not have orientation.


#6 Lyqyd

    Lua Liquidator

  • Moderators
  • 8,465 posts

Posted 17 May 2014 - 09:01 AM

Are you placing a bunch of signs there? turtle.place already has an optional argument.

#7 theoriginalbit

    Semi-Professional ComputerCrafter

  • Moderators
  • 7,332 posts
  • LocationAustralia

Posted 17 May 2014 - 09:10 AM

Personally I'd prefer that the Turtle were to always place the piston facing away from it, meaning
turtle.place would position the piston forward
turtle.placeUp would position the piston upward
turtle.placeDown would position the piston downward
with this logic it doesn't break anything (such as placing signs) and doesn't require extra methods, its just as (if not more intuitive) and means you can place the piston facing in any direction.

Edited by theoriginalbit, 17 May 2014 - 09:12 AM.


#8 awsmazinggenius

  • Members
  • 930 posts
  • LocationCanada

Posted 17 May 2014 - 12:58 PM

Will this work for things like stairs, signs and other things with an orientation?

#9 theoriginalbit

    Semi-Professional ComputerCrafter

  • Moderators
  • 7,332 posts
  • LocationAustralia

Posted 17 May 2014 - 01:07 PM

View Postawsmazinggenius, on 17 May 2014 - 12:58 PM, said:

Will this work for things like stairs, signs and other things with an orientation?
the method I suggested would. the rotation of those things would be dependent on the way the Turtle is facing.

with stairs just think about the bottom of the stairs always touching the Turtle and the top stair relating to the rotation... unfortunately you'll never have a perfect way to do rotations with the stairs and Turtles, they just don't have as many positions and pitch + yaw unlike a player does to be able to handle all possible rotations of stairs.

Edited by theoriginalbit, 17 May 2014 - 01:09 PM.


#10 SquidDev

    Frickin' laser beams | Resident Necromancer

  • Members
  • 1,427 posts
  • LocationDoes anyone put something serious here?

Posted 17 May 2014 - 01:41 PM

View PostKingofGamesYami, on 17 May 2014 - 04:12 AM, said:

What about making this:
turtle.place($optional_argument$)
turtle.place("up")
turtle.place('down')
turtle.place('back')
turtle.place('right')
turtle.place('left')
turtle.place('forward')
--#if no argument supplied, automatically places up
--#optional argument is ignored if block does not have orientation.

I'd have to agree with this. It would be nice to see some sort of placing system like the OpenComputers robot. The 'side'/'orientation' to place on would be an optional argument: turtle.place([string signText, [number side]])

I don't want to end up with CC copying from OC but this is one of its more useful features.

Edited by SquidDev, 17 May 2014 - 01:47 PM.


#11 KingofGamesYami

  • Members
  • 3,002 posts
  • LocationUnited States of America

Posted 21 May 2014 - 10:00 PM

View PostLyqyd, on 17 May 2014 - 09:01 AM, said:

Are you placing a bunch of signs there? turtle.place already has an optional argument.
Uh, no... I totally forgot about sign text... SquidDev explained it better than I did.

#12 Tiavor

  • Members
  • 3 posts

Posted 13 August 2015 - 08:54 PM

6 directions aren't enough for e.g. stairs and signs. each different type of block rotation needs a different implementation.

Can turtles use wrenches to turn blocks? If they are not, then this option is useless.

Edited by Tiavor, 22 September 2015 - 08:12 AM.


#13 Lion4ever

  • Members
  • 91 posts

Posted 30 December 2015 - 01:45 AM

placing the block against the turtle should be the first choice and only choice in my optionion, too.

#14 PleaseDeleteMe

  • Members
  • 11 posts
  • LocationNetherlands

Posted 10 January 2016 - 04:15 PM

In 1.76 the piston will face the turtle when placed, however when you place it above or below it will still follow this orientation, there's no way yet to place a turtle facing up or down just by using the three place methods, only 4 orientations are covered. I'd also like to see an optional parameter to allow placement of blocks in a certain orientation.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users