Cloudy, have you speak with Dan200 about detecting air, void, liquid, solid and such?
What was results?
1
turtle.getItemId()?
Started by creepig, Oct 05 2012 12:39 PM
22 replies to this topic
#22
-
- Members
- 830 posts
Posted 08 October 2012 - 09:22 PM
So cloudy, if getting item IDs and metadata breaks the fourth wall, how about this?
turtle.associate(slot, ID). You can memorize an item in its inventory for later comparison without having to carry it around all the time. slot being the slot to memorize, ID being the ID you want to save it as. Since the ID is provided by the program instead of "Oh, I know, that's ItemID 1!", the 4th wall remains unbroken. Of course, an accompanying function would be needed to compare a block in front of the turtle to a stored item ID (Or maybe to return which stored ID it matches, or false. That would speed things up.).
Yay or nay?
turtle.associate(slot, ID). You can memorize an item in its inventory for later comparison without having to carry it around all the time. slot being the slot to memorize, ID being the ID you want to save it as. Since the ID is provided by the program instead of "Oh, I know, that's ItemID 1!", the 4th wall remains unbroken. Of course, an accompanying function would be needed to compare a block in front of the turtle to a stored item ID (Or maybe to return which stored ID it matches, or false. That would speed things up.).
Yay or nay?
#23
-
- Members
- 1,033 posts
Lua God
- LocationWellington, New Zealand
Posted 09 October 2012 - 12:42 AM
D3matt, on 08 October 2012 - 09:22 PM, said:
So cloudy, if getting item IDs and metadata breaks the fourth wall, how about this?
turtle.associate(slot, ID). You can memorize an item in its inventory for later comparison without having to carry it around all the time. slot being the slot to memorize, ID being the ID you want to save it as. Since the ID is provided by the program instead of "Oh, I know, that's ItemID 1!", the 4th wall remains unbroken. Of course, an accompanying function would be needed to compare a block in front of the turtle to a stored item ID (Or maybe to return which stored ID it matches, or false. That would speed things up.).
Yay or nay?
turtle.associate(slot, ID). You can memorize an item in its inventory for later comparison without having to carry it around all the time. slot being the slot to memorize, ID being the ID you want to save it as. Since the ID is provided by the program instead of "Oh, I know, that's ItemID 1!", the 4th wall remains unbroken. Of course, an accompanying function would be needed to compare a block in front of the turtle to a stored item ID (Or maybe to return which stored ID it matches, or false. That would speed things up.).
Yay or nay?
I think I suggested that when turtle.compare was added, and it still hasn't happened, so it seems unlikely.
Edit: Database turtles, from Aperture Science Turtle Upgrades, can do this.
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users
