ComputerCraft Wiki - User contributions [en]

User talk:Thesbros

2012-10-24T01:29:40Z

Riking: Undo revision 3486 by Riking (talk) lolninja

User talk:Thesbros

2012-10-24T01:29:26Z

Riking: /* Mandrake */ new section

== Keymapper API ==

The keymapper API was intended to assist with deciphering os.pullEvent("key") calls. os.pullEvent("char") basically replicates the conditions that it was intended to solve, and that's why os.pullEvent("char") was the only one I listed in the deprecated statement. Can you explain to me your reasoning for including key events in the notice? [[User:Riking|Riking]]

== Random Reverts? ==
Hello its mandrake again. and I would like to ask why you keep reverting like a madman?! I wanted that page deleted for a reason. The code on that page is old and outdated and did not work back in 1.3 or so when i tried it.
[[User:FernFlower|FernFlower]] 21:28, 23 October 2012 (EDT)

== Mandrake ==

Hello its mandrake again. and I would like to ask why you keep reverting like a madman?! I wanted that page deleted for a reason. The code on that page is old and outdated and did not work back in 1.3 or so when i tried it.
[[User:FernFlower|FernFlower]] 21:28, 23 October 2012 (EDT)

User talk:Thesbros

2012-10-24T01:25:03Z

Riking:

User talk:Theeboris

2012-10-24T01:24:42Z

Riking: create section "Your username"

==Your username==
Hello, welcome to the wiki. Your username is very similar to that of [[User:Thesbros]]. It's not at all required that you change it, I'm just asking you to consider that this may cause some confusion among people. Thank you for contributing to the ComputerCraft Wiki, though! [[User:Riking|Riking]] 21:24, 23 October 2012 (EDT)

Turtle (API)

2012-10-08T04:15:40Z

Riking: Update to craft() mechanics

The Turtle API is used to work with your Turtles.

{| border="1" cellpadding="2" cellspacing="0|"
| colspan="2" | <center>KEY</center>
|-
! Color
! Turtles that can perform this
|-
|White
|All
|-{{row-lightgreen}}
|Green
|Crafty
|-{{row-lightyellow}}
|Yellow
|Mining, Felling, Digging, Farming
|-{{row-lightred}}
|Red
|Any tool
|}


{| border="1" cellpadding="2" cellspacing="0|"
!style="background:#EEE" width="100px"|Return
!style="background:#EEE" width="200px"|Method name
!style="background:#EEE" width="*"|Description
!style="background:#EEE" width="*"|Min version
|-{{row-lightgreen}}
|bool "success"
|[[turtle.craft]]()
|Craft items using ingredients anywhere in the Turtle's inventory and place results in the active slot
|
|-
|bool "success"
|[[turtle.forward]]()
|Let the Turtle move forward
|
|-
|bool "success"
|[[turtle.back]]()
|Let the Turtle move back
|
|-
|bool "success"
|[[turtle.up]]()
|Let the Turtle move up
|
|-
|bool "success"
|[[turtle.down]]()
|Let the Turtle move down
|
|-
|bool "true"
|[[turtle.turnLeft]]()
|The Turtle turns left
|
|-
|bool "true"
|[[turtle.turnRight]]()
|The Turtle turns right
|
|-
|bool "slot > 16"
|[[turtle.select]]( slotNum )
|The Turtle selects the given Slot (1 is top left, 16 (9 in 1.33 and earlier) is bottom right)
|
|-
|int "result"
|[[turtle.getItemCount]]( slotNum )
|Counts how many items are in the given Slot
|
|-
|int "result"
|[[turtle.getItemSpace]]( slotNum )
|Counts how many remaining items you need to fill the stack in the given Slot
|
|-{{row-lightred}}
|bool "success"
|[[turtle.attack]]()
|Attacks in front of the turtle.
| 1.4
|-{{row-lightred}}
|bool "success"
|[[turtle.attackUp]]()
|Attacks over the turtle.
| 1.4
|-{{row-lightred}}
|bool "success"
|[[turtle.attackDown]]()
|Attacks under the turtle.
| 1.4
|-{{row-lightyellow}}
|bool "success"
|[[turtle.dig]]()
|Breaks the Block in front. With hoe: tills the dirt in front of it.
|
|-{{row-lightyellow}}
|bool "success"
|[[turtle.digUp]]()
|Breaks the Block above. With hoe: tills the dirt above it.
|
|-{{row-lightyellow}}
|bool "success"
|[[turtle.digDown]]()
|Breaks the Block below. With hoe: tills the dirt below it.
|
|-
|nil
|[[turtle.place]]( [signText] )
|Places a Block of the selected slot in front. Engrave [signText] on signs if provided.
| 1.4
|-
|nil
|[[turtle.placeUp]]()
|Places a Block of the selected slot above
|
|-
|nil
|[[turtle.placeDown]]()
|Places a Block of the selected slot below
|
|-
|bool "result"
|[[turtle.detect]]()
|Detects if there is a Block in front. Does not detect mobs.
|
|-
|bool "result"
|[[turtle.detectUp]]()
|Detects if there is a Block above
|
|-
|bool "result"
|[[turtle.detectDown]]()
|Detects if there is a Block below
|
|-
|bool "result"
|[[turtle.compare]]()
|Detects if the block in front is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareUp]]()
|Detects if the block above is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareDown]]()
|Detects if the block below is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareTo]]( [slot] )
|Compare the current selected slot and the given slot to see if the items are the same, yields true if they are the same, and false if not.
| 1.4
|-
|bool "success"
|[[turtle.drop]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e in front of the turtle) it will try to place into the inventory, returning false if the inventory is full.
|
|-
|bool "success"
|[[turtle.drop|turtle.dropUp]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e above the turtle) it will try to place into the inventory, returning false if the inventory is full. If below a furnace, will place item in the bottom slot.
|
|-
|bool "success"
|[[turtle.drop|turtle.dropDown]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e below the turtle) it will try to place into the inventory, returning false if the inventory is full. If above a furnace, will place item in the top slot.
|
|-
|bool "success"
|[[turtle.suck]]()
|Picks up an item stack of any number, from the ground or an inventory in front of the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.suckUp]]()
|Picks up an item stack of any number, from the ground or an inventory above the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.suckDown]]()
|Picks up an item stack of any number, from the ground or an inventory below the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.refuel]]([quantity])
|If the current selected slot contains a fuel item, it will consume it to give the turtle the ability to move. Added in 1.4 and is only needed in needfuel mode. If the current slot doesn't contain a fuel item, it yields false. Fuel values for different items can be found at [[Turtle.refuel#Fuel_Values]]. If a quantity is specified, it will refuel only up to that many items, otherwise, it will consume all the items in the slot.
| 1.4
|-
|int "fuel"
|[[turtle.getFuelLevel]]()
|Returns the current fuel level of the turtle, this is the number of blocks the turtle can move. If turtleNeedFuel = 0 then it yields "unlimited".
| 1.4
|}

Trivia:
During the 1.4 beta, turtle.getFuelLevel() in softcore(that is now turtleneedsfuel = 0) returned 9000.
[[Category:APIs]]

Disk

2012-09-26T22:39:55Z

Riking: bold not italic

{{disambiguation}}
'''Disk''' can mean one of:
* [[Floppy Disk]], an item you use to store data on
* [[Disk (API)]], an API for programs

Disk

2012-09-26T22:39:44Z

Riking: disambig

{{disambiguation}}
''Disk'' can mean one of:
* [[Floppy Disk]], an item you use to store data on
* [[Disk (API)]], an API for programs

User talk:Thesbros

2012-09-24T01:21:22Z

Riking: Keymapper API

Turtle

2012-09-24T01:09:46Z

Riking: /* Recipes */ centered text, added text

'''Turtles''' are essentially robots, and were added in the 1.3 update. They run an OS (like the [[Console|consoles]]) named [[TurtleOS]]. They have the ability to place, break and detect blocks, move around and drop items in their inventory. The programs they run are stored on its internal memory or [[Floppy Disk|floppy disks]].

The 1.4 update was focused on turtles and added new tools for them to use. Turtles can now in addition to pickaxes use: Hoes, crafting tables, axes, shovels and sword. The update also included a new fuel system for the turtles. Turtles also got an inventory upgrade from 9 slots to 16.

Turtles are submersible and lavaproof. As such, they are extremely useful for mining near bedrock, where heavy lava flows can prevent access to diamonds and other rare finds.

If you would like to know more about how to program them, have a look at the [[Turtle (API)|Turtle API]].

==Floppy Disks==
Turtles do not have a built-in floppy drive. As such they need a floppy drive placed beside them to access disks. However if the turtle is a Wireless turtle, the floppy drive and other peripherals must be placed on a side other than the side the wireless modem is on.

==Power source==
Turtles run on fuel. Fuel is any item that works in a regular furnace, like coal and lava. The turtle gains 0.6 movement per half second the fuel would have burnt in a furnace.
The turtle can move 1 block for each fuel count it got, for example, coal yields 96 block movements. For more information, go to the [[Turtle.refuel]] page.

=== Optional Non-fuel mode ===

In this mode turtles use their internal redstone engine, they do not need to be re-charged, or any other form of external power.
This is because redstone continuously emits low levels of energy, and the turtle's engine is very efficient.
This mode can be turned on by editing the turtle config file (config/mod_CCTurtle.cfg) and setting turtleNeedsFuel to 0.

==Farming==
Turtles equipped with a hoe can till dirt.

==Mining==
Turtles crafted with a [[diamond pickaxe]], [[diamond axe]], or [[diamond shovel]], can break blocks, mine wood, and even break dirt and gravel, depending on the tool you used on it. The tools equipped on the turtle have no durability, and so can be used indefinitely without the need for any additional materials. When a turtle breaks the block it gets the item directly into its inventory. Different tools yields different drop, for example, an axe can break anything, but it won't get ores.

==Crafting==
Turtles equipped with a workbench can craft items. When crafting, the inventory must be clear of all items other than the ones needed for the recipe.

==Melee==
Turtles equipped with a sword can attack players and mobs. When a turtle kills a mob it will leave the experience orbs on the ground, but add the loot to it's inventory. Turtles can also attack with any tool, where axe is the second best after the sword.

==Recipes==

{|
|+'''Crafting ingredients'''
|-
|Turtle
|{{Crafting grid
|A1=iron_ingot |B1=iron_ingot |C1=iron_ingot
|A2=iron_ingot |B2=console |C2=iron_ingot
|A3=iron_ingot |B3=chest |C3=iron_ingot
|Output=turtle
}}
|}
Turtles can be equipped with different peripherals and tools. A turtle can only have one tool and one peripheral.
 The following tools can be equipped to a turtles: [[diamond pickaxe]], [[diamond axe]], [[diamond shovel]], [[diamond hoe]] and [[diamond sword]]
 The following peripherals can be equipped to a turtles: [[modem|wireless modem]] and [[crafting table]].
 '''Turtle recipe and examples for equipping a turtle with tools and peripherals.'''
{| border="1" cellpadding="2" cellspacing="0|" style="text-align: center"
!style="background:#EEE" width="100px"|
!style="background:#EEE" |None
!style="background:#EEE" |Crafty
!style="background:#EEE" |Wireless
|-
!style="background:#EEE" |None
|{{Crafting grid
|B2=turtle
|Output=turtle
}}
|{{Crafting grid
|B2=turtle |A2=workbench
|Output=Crafty_Turtle
}}
|{{Crafting grid
|B2=turtle |A2=modem
|Output=wireless_turtle
}}
|-
!style="background:#EEE" |Mining
|{{Crafting grid
|B2=turtle |C2=diamond_pickaxe
|Output=mining_turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_pickaxe
|Output=Crafty_Mining_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_pickaxe
|Output=wireless_mining_turtle
}}
|-
!style="background:#EEE" |Farming
|{{Crafting grid
|B2=turtle |C2=diamond_hoe
|Output=Farming_Turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_hoe
|Output=Crafty_Farming_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_hoe
|Output=Wireless_Farming_Turtle
}}
|-
!style="background:#EEE" |Melee
|{{Crafting grid
|B2=turtle |C2=diamond_sword
|Output=Melee_Turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_sword
|Output=Crafty_Melee_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_sword
|Output=Wireless_Melee_Turtle
}}
|-
!style="background:#EEE" |Felling
|{{Crafting grid
|B2=turtle |C2=diamond_axe
|Output=Felling_Turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_axe
|Output=Crafty_Felling_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_axe
|Output=Wireless_Felling_Turtle
}}
|-
!style="background:#EEE" |Digging
|{{Crafting grid
|B2=turtle |C2=diamond_shovel
|Output=Digging_Turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_shovel
|Output=Crafty_Digging_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_shovel
|Output=Wireless_Digging_Turtle
}}
|-
!style="background:#EEE" |Crafty
|See Above
|N/A
|{{Crafting grid
|A2=modem |B2=turtle |C2=workbench
|Output=Wireless_Crafty_Turtle
}}
|}
[[Category:Blocks]]

Turtle

2012-09-24T01:07:01Z

Riking: /* Recipes */

'''Turtles''' are essentially robots, and were added in the 1.3 update. They run an OS (like the [[Console|consoles]]) named [[TurtleOS]]. They have the ability to place, break and detect blocks, move around and drop items in their inventory. The programs they run are stored on its internal memory or [[Floppy Disk|floppy disks]].

The 1.4 update was focused on turtles and added new tools for them to use. Turtles can now in addition to pickaxes use: Hoes, crafting tables, axes, shovels and sword. The update also included a new fuel system for the turtles. Turtles also got an inventory upgrade from 9 slots to 16.

Turtles are submersible and lavaproof. As such, they are extremely useful for mining near bedrock, where heavy lava flows can prevent access to diamonds and other rare finds.

If you would like to know more about how to program them, have a look at the [[Turtle (API)|Turtle API]].

==Floppy Disks==
Turtles do not have a built-in floppy drive. As such they need a floppy drive placed beside them to access disks. However if the turtle is a Wireless turtle, the floppy drive and other peripherals must be placed on a side other than the side the wireless modem is on.

==Power source==
Turtles run on fuel. Fuel is any item that works in a regular furnace, like coal and lava. The turtle gains 0.6 movement per half second the fuel would have burnt in a furnace.
The turtle can move 1 block for each fuel count it got, for example, coal yields 96 block movements. For more information, go to the [[Turtle.refuel]] page.

=== Optional Non-fuel mode ===

In this mode turtles use their internal redstone engine, they do not need to be re-charged, or any other form of external power.
This is because redstone continuously emits low levels of energy, and the turtle's engine is very efficient.
This mode can be turned on by editing the turtle config file (config/mod_CCTurtle.cfg) and setting turtleNeedsFuel to 0.

==Farming==
Turtles equipped with a hoe can till dirt.

==Mining==
Turtles crafted with a [[diamond pickaxe]], [[diamond axe]], or [[diamond shovel]], can break blocks, mine wood, and even break dirt and gravel, depending on the tool you used on it. The tools equipped on the turtle have no durability, and so can be used indefinitely without the need for any additional materials. When a turtle breaks the block it gets the item directly into its inventory. Different tools yields different drop, for example, an axe can break anything, but it won't get ores.

==Crafting==
Turtles equipped with a workbench can craft items. When crafting, the inventory must be clear of all items other than the ones needed for the recipe.

==Melee==
Turtles equipped with a sword can attack players and mobs. When a turtle kills a mob it will leave the experience orbs on the ground, but add the loot to it's inventory. Turtles can also attack with any tool, where axe is the second best after the sword.

==Recipes==

{|
|+'''Crafting ingredients'''
|-
|Turtle
|{{Crafting grid
|A1=iron_ingot |B1=iron_ingot |C1=iron_ingot
|A2=iron_ingot |B2=console |C2=iron_ingot
|A3=iron_ingot |B3=chest |C3=iron_ingot
|Output=turtle
}}
|}
Turtles can be equipped with different peripherals and tools. A turtle can only have one tool and one peripheral.
 The following tools can be equipped to a turtles: [[diamond pickaxe]], [[diamond axe]], [[diamond shovel]], [[diamond hoe]] and [[diamond sword]]
 The following peripherals can be equipped to a turtles: [[modem|wireless modem]] and [[crafting table]].
 '''Turtle recipe and examples for equipping a turtle with tools and peripherals.'''
{| border="1" cellpadding="2" cellspacing="0|"
!style="background:#EEE" width="100px"|
!style="background:#EEE" |None
!style="background:#EEE" |Crafty
!style="background:#EEE" |Wireless
|-
!style="background:#EEE" |None
|{{Crafting grid
|B2=turtle
|Output=turtle
}}
|{{Crafting grid
|B2=turtle |A2=workbench
|Output=Crafty_Turtle
}}
|{{Crafting grid
|B2=turtle |A2=modem
|Output=wireless_turtle
}}
|-
!style="background:#EEE" |Mining
|{{Crafting grid
|B2=turtle |C2=diamond_pickaxe
|Output=mining_turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_pickaxe
|Output=Crafty_Mining_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_pickaxe
|Output=wireless_mining_turtle
}}
|-
!style="background:#EEE" |Farming
|{{Crafting grid
|B2=turtle |C2=diamond_hoe
|Output=Farming_Turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_hoe
|Output=Crafty_Farming_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_hoe
|Output=Wireless_Farming_Turtle
}}
|-
!style="background:#EEE" |Melee
|{{Crafting grid
|B2=turtle |C2=diamond_sword
|Output=Melee_Turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_sword
|Output=Crafty_Melee_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_sword
|Output=Wireless_Melee_Turtle
}}
|-
!style="background:#EEE" |Felling
|{{Crafting grid
|B2=turtle |C2=diamond_axe
|Output=Felling_Turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_axe
|Output=Crafty_Felling_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_axe
|Output=Wireless_Felling_Turtle
}}
|-
!style="background:#EEE" |Digging
|{{Crafting grid
|B2=turtle |C2=diamond_shovel
|Output=Digging_Turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_shovel
|Output=Crafty_Digging_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_shovel
|Output=Wireless_Digging_Turtle
}}
|-
!style="background:#EEE" |Crafty
|See Above
|N/A
|{{Crafting grid
|A2=modem |B2=turtle |C2=workbench
|Output=Wireless_Crafty_Turtle
}}
|}
[[Category:Blocks]]

Turtle

2012-09-24T01:06:34Z

Riking: Undo revision 3157 by Riking (talk)

'''Turtles''' are essentially robots, and were added in the 1.3 update. They run an OS (like the [[Console|consoles]]) named [[TurtleOS]]. They have the ability to place, break and detect blocks, move around and drop items in their inventory. The programs they run are stored on its internal memory or [[Floppy Disk|floppy disks]].

The 1.4 update was focused on turtles and added new tools for them to use. Turtles can now in addition to pickaxes use: Hoes, crafting tables, axes, shovels and sword. The update also included a new fuel system for the turtles. Turtles also got an inventory upgrade from 9 slots to 16.

Turtles are submersible and lavaproof. As such, they are extremely useful for mining near bedrock, where heavy lava flows can prevent access to diamonds and other rare finds.

If you would like to know more about how to program them, have a look at the [[Turtle (API)|Turtle API]].

==Floppy Disks==
Turtles do not have a built-in floppy drive. As such they need a floppy drive placed beside them to access disks. However if the turtle is a Wireless turtle, the floppy drive and other peripherals must be placed on a side other than the side the wireless modem is on.

==Power source==
Turtles run on fuel. Fuel is any item that works in a regular furnace, like coal and lava. The turtle gains 0.6 movement per half second the fuel would have burnt in a furnace.
The turtle can move 1 block for each fuel count it got, for example, coal yields 96 block movements. For more information, go to the [[Turtle.refuel]] page.

=== Optional Non-fuel mode ===

In this mode turtles use their internal redstone engine, they do not need to be re-charged, or any other form of external power.
This is because redstone continuously emits low levels of energy, and the turtle's engine is very efficient.
This mode can be turned on by editing the turtle config file (config/mod_CCTurtle.cfg) and setting turtleNeedsFuel to 0.

==Farming==
Turtles equipped with a hoe can till dirt.

==Mining==
Turtles crafted with a [[diamond pickaxe]], [[diamond axe]], or [[diamond shovel]], can break blocks, mine wood, and even break dirt and gravel, depending on the tool you used on it. The tools equipped on the turtle have no durability, and so can be used indefinitely without the need for any additional materials. When a turtle breaks the block it gets the item directly into its inventory. Different tools yields different drop, for example, an axe can break anything, but it won't get ores.

==Crafting==
Turtles equipped with a workbench can craft items. When crafting, the inventory must be clear of all items other than the ones needed for the recipe.

==Melee==
Turtles equipped with a sword can attack players and mobs. When a turtle kills a mob it will leave the experience orbs on the ground, but add the loot to it's inventory. Turtles can also attack with any tool, where axe is the second best after the sword.

==Recipes==

{|
|+'''Crafting ingredients'''
|-
|Turtle
|{{Crafting grid
|A1=iron_ingot |B1=iron_ingot |C1=iron_ingot
|A2=iron_ingot |B2=console |C2=iron_ingot
|A3=iron_ingot |B3=chest |C3=iron_ingot
|Output=turtle
}}
|}
Turtles can be equipped with different peripherals and tools. A turtle can only have one tool and one peripheral.
 The following tools can be equipped to a turtles: [[diamond pickaxe]], [[diamond axe]], [[diamond shovel]], [[diamond hoe]] and [[diamond sword]]
 The following peripherals can be equipped to a turtles: [[modem|wireless modem]] and [[crafting table]].
 '''Turtle recipe and examples for equipping a turtle with tools and peripherals.'''
{| border="1" cellpadding="2" cellspacing="0|"
!style="background:#EEE" width="100px"|
!style="background:#EEE" |None
!style="background:#EEE" |Crafty
!style="background:#EEE" |Wireless
|-
!style="background:#EEE" |None
|{{Crafting grid
|B2=turtle
|Output=turtle
}}
|{{Crafting grid
|B2=turtle |A2=workbench
|Output=Crafty_Turtle
}}
|{{Crafting grid
|B2=turtle |A2=modem
|Output=wireless_turtle
}}
|-
!style="background:#EEE" |Mining
|{{Crafting grid
|B2=turtle |C2=diamond_pickaxe
|Output=mining_turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_pickaxe
|Output=Crafty_Mining_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_pickaxe
|Output=wireless_mining_turtle
}}
|-
!style="background:#EEE" |Farming
|{{Crafting grid
|B2=turtle |C2=diamond_hoe
|Output=Farming_Turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_hoe
|Output=Crafty_Farming_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_hoe
|Output=Wireless_Farming_Turtle
}}
|-
!style="background:#EEE" |Melee
|{{Crafting grid
|B2=turtle |C2=diamond_sword
|Output=Melee_Turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_sword
|Output=Crafty_Melee_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_sword
|Output=Wireless_Melee_Turtle
}}
|-
!style="background:#EEE" |Felling
|{{Crafting grid
|B2=turtle |C2=diamond_axe
|Output=Felling_Turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_axe
|Output=Crafty_Felling_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_axe
|Output=Wireless_Felling_Turtle
}}
|-
!style="background:#EEE" |Digging
|{{Crafting grid
|B2=turtle |C2=diamond_shovel
|Output=Digging_Turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_shovel
|Output=Crafty_Digging_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_shovel
|Output=Wireless_Digging_Turtle
}}
|-
!style="background:#EEE" |Crafty
|
|
|{{Crafting grid
|A2=modem |B2=turtle |C2=workbench
|Output=Wireless_Crafty_Turtle
}}
|}
[[Category:Blocks]]

Turtle

2012-09-24T01:01:01Z

Riking: /* Recipes */ No, crafty is a vertical category.

'''Turtles''' are essentially robots, and were added in the 1.3 update. They run an OS (like the [[Console|consoles]]) named [[TurtleOS]]. They have the ability to place, break and detect blocks, move around and drop items in their inventory. The programs they run are stored on its internal memory or [[Floppy Disk|floppy disks]].

The 1.4 update was focused on turtles and added new tools for them to use. Turtles can now in addition to pickaxes use: Hoes, crafting tables, axes, shovels and sword. The update also included a new fuel system for the turtles. Turtles also got an inventory upgrade from 9 slots to 16.

Turtles are submersible and lavaproof. As such, they are extremely useful for mining near bedrock, where heavy lava flows can prevent access to diamonds and other rare finds.

If you would like to know more about how to program them, have a look at the [[Turtle (API)|Turtle API]].

==Floppy Disks==
Turtles do not have a built-in floppy drive. As such they need a floppy drive placed beside them to access disks. However if the turtle is a Wireless turtle, the floppy drive and other peripherals must be placed on a side other than the side the wireless modem is on.

==Power source==
Turtles run on fuel. Fuel is any item that works in a regular furnace, like coal and lava. The turtle gains 0.6 movement per half second the fuel would have burnt in a furnace.
The turtle can move 1 block for each fuel count it got, for example, coal yields 96 block movements. For more information, go to the [[Turtle.refuel]] page.

=== Optional Non-fuel mode ===

In this mode turtles use their internal redstone engine, they do not need to be re-charged, or any other form of external power.
This is because redstone continuously emits low levels of energy, and the turtle's engine is very efficient.
This mode can be turned on by editing the turtle config file (config/mod_CCTurtle.cfg) and setting turtleNeedsFuel to 0.

==Farming==
Turtles equipped with a hoe can till dirt.

==Mining==
Turtles crafted with a [[diamond pickaxe]], [[diamond axe]], or [[diamond shovel]], can break blocks, mine wood, and even break dirt and gravel, depending on the tool you used on it. The tools equipped on the turtle have no durability, and so can be used indefinitely without the need for any additional materials. When a turtle breaks the block it gets the item directly into its inventory. Different tools yields different drop, for example, an axe can break anything, but it won't get ores.

==Crafting==
Turtles equipped with a workbench can craft items. When crafting, the inventory must be clear of all items other than the ones needed for the recipe.

==Melee==
Turtles equipped with a sword can attack players and mobs. When a turtle kills a mob it will leave the experience orbs on the ground, but add the loot to it's inventory. Turtles can also attack with any tool, where axe is the second best after the sword.

==Recipes==

{|
|+'''Crafting ingredients'''
|-
|Turtle
|{{Crafting grid
|A1=iron_ingot |B1=iron_ingot |C1=iron_ingot
|A2=iron_ingot |B2=console |C2=iron_ingot
|A3=iron_ingot |B3=chest |C3=iron_ingot
|Output=turtle
}}
|}
Turtles can be equipped with different peripherals and tools. A turtle can only have one tool and one peripheral.
 The following tools can be equipped to a turtles: [[diamond pickaxe]], [[diamond axe]], [[diamond shovel]], [[diamond hoe]] and [[diamond sword]]
 The following peripherals can be equipped to a turtles: [[modem|wireless modem]] and [[crafting table]].
 '''Turtle recipe and examples for equipping a turtle with tools and peripherals.'''
{| border="1" cellpadding="2" cellspacing="0|"
!style="background:#EEE" width="100px"|
!style="background:#EEE" |None
!style="background:#EEE" |Crafty
!style="background:#EEE" |Wireless
|-
!style="background:#EEE" |None
|{{Crafting grid
|B2=turtle
|Output=turtle
}}
|{{Crafting grid
|B2=turtle |A2=workbench
|Output=Crafty_Turtle
}}
|{{Crafting grid
|B2=turtle |A2=modem
|Output=wireless_turtle
}}
|-
!style="background:#EEE" |Mining
|{{Crafting grid
|B2=turtle |C2=diamond_pickaxe
|Output=mining_turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_pickaxe
|Output=Crafty_Mining_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_pickaxe
|Output=wireless_mining_turtle
}}
|-
!style="background:#EEE" |Farming
|{{Crafting grid
|B2=turtle |C2=diamond_hoe
|Output=Farming_Turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_hoe
|Output=Crafty_Farming_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_hoe
|Output=Wireless_Farming_Turtle
}}
|-
!style="background:#EEE" |Melee
|{{Crafting grid
|B2=turtle |C2=diamond_sword
|Output=Melee_Turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_sword
|Output=Crafty_Melee_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_sword
|Output=Wireless_Melee_Turtle
}}
|-
!style="background:#EEE" |Felling
|{{Crafting grid
|B2=turtle |C2=diamond_axe
|Output=Felling_Turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_axe
|Output=Crafty_Felling_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_axe
|Output=Wireless_Felling_Turtle
}}
|-
!style="background:#EEE" |Digging
|{{Crafting grid
|B2=turtle |C2=diamond_shovel
|Output=Digging_Turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_shovel
|Output=Crafty_Digging_Turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_shovel
|Output=Wireless_Digging_Turtle
}}
|-
[[Category:Blocks]]

Turtle (API)

2012-09-23T22:24:14Z

Riking:

The Turtle API is used to work with your Turtles.

{| border="1" cellpadding="2" cellspacing="0|"
| colspan="2" | <center>KEY</center>
|-
! Color
! Turtles that can perform this
|-
|White
|All
|-{{row-lightgreen}}
|Green
|Crafty
|-{{row-lightyellow}}
|Yellow
|Any Tool
|-{{row-lightred}}
|Red
|(Not Used)
|}


{| border="1" cellpadding="2" cellspacing="0|"
!style="background:#EEE" width="100px"|Return
!style="background:#EEE" width="200px"|Method name
!style="background:#EEE" width="*"|Description
!style="background:#EEE" width="*"|Min version
|-{{row-lightgreen}}
|bool "success"
|[[turtle.craft]]()
|Craft items using ingredients in the nine upper left slots
|
|-
|bool "success"
|[[turtle.forward]]()
|Let the Turtle move forward
|
|-
|bool "success"
|[[turtle.back]]()
|Let the Turtle move back
|
|-
|bool "success"
|[[turtle.up]]()
|Let the Turtle move up
|
|-
|bool "success"
|[[turtle.down]]()
|Let the Turtle move down
|
|-
|bool "true"
|[[turtle.turnLeft]]()
|The Turtle turns left
|
|-
|bool "true"
|[[turtle.turnRight]]()
|The Turtle turns right
|
|-
|bool "slot > 16"
|[[turtle.select]]( slotNum )
|The Turtle selects the given Slot (1 is top left, 16 (9 in 1.33 and earlier) is bottom right)
|
|-
|int "result"
|[[turtle.getItemCount]]( slotNum )
|Counts how many items are in the given Slot
|
|-
|int "result"
|[[turtle.getItemSpace]]( slotNum )
|Counts how many remaining items you need to fill the stack in the given Slot
|
|-{{row-lightyellow}}
|bool "success"
|[[turtle.attack]]()
|Attacks in front of the turtle.
| 1.4
|-{{row-lightyellow}}
|bool "success"
|[[turtle.attackUp]]()
|Attacks over the turtle.
| 1.4
|-{{row-lightyellow}}
|bool "success"
|[[turtle.attackDown]]()
|Attacks under the turtle.
| 1.4
|-{{row-lightyellow}}
|bool "success"
|[[turtle.dig]]()
|Breaks the Block in front. With hoe: tills the dirt in front of it.
|
|-{{row-lightyellow}}
|bool "success"
|[[turtle.digUp]]()
|Breaks the Block above. With hoe: tills the dirt above it.
|
|-{{row-lightyellow}}
|bool "success"
|[[turtle.digDown]]()
|Breaks the Block below. With hoe: tills the dirt below it.
|
|-
|nil
|[[turtle.place]]( [signText] )
|Places a Block of the selected slot in front. Engrave [signText] on signs if provided.
| 1.4
|-
|nil
|[[turtle.placeUp]]()
|Places a Block of the selected slot above
|
|-
|nil
|[[turtle.placeDown]]()
|Places a Block of the selected slot below
|
|-
|bool "result"
|[[turtle.detect]]()
|Detects if there is a Block in front
|
|-
|bool "result"
|[[turtle.detectUp]]()
|Detects if there is a Block above
|
|-
|bool "result"
|[[turtle.detectDown]]()
|Detects if there is a Block below
|
|-
|bool "result"
|[[turtle.compare]]()
|Detects if the block in front is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareUp]]()
|Detects if the block above is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareDown]]()
|Detects if the block below is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareTo]]( [slot] )
|Compare the current selected slot and the given slot to see if the items are the same, yields true if they are the same, and false if not.
| 1.4
|-
|bool "success"
|[[turtle.drop]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e in front of the turtle) it will try to place into the inventory, returning false if the inventory is full.
|
|-
|bool "success"
|[[turtle.drop|turtle.dropUp]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e above the turtle) it will try to place into the inventory, returning false if the inventory is full. If below a furnace, will place item in the bottom slot.
|
|-
|bool "success"
|[[turtle.drop|turtle.dropDown]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e below the turtle) it will try to place into the inventory, returning false if the inventory is full. If above a furnace, will place item in the top slot.
|
|-
|bool "success"
|[[turtle.suck]]()
|Picks up an item stack of any number, from the ground or an inventory in front of the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.suckUp]]()
|Picks up an item stack of any number, from the ground or an inventory above the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.suckDown]]()
|Picks up an item stack of any number, from the ground or an inventory below the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.refuel]]()
|If the current selected slot contains a fuel item, it will consume it to give the turtle the ability to move. Added in 1.4 and is only needed in needfuel mode. If the current slot doesn't contain a fuel item, it yields false. Fuel values for different items can be found at [[Turtle.refuel#Fuel_Values]].
| 1.4
|-
|int "fuel"
|[[turtle.getFuelLevel]]()
|Returns the current fuel level of the turtle, this is the number of blocks the turtle can move. If turtleNeedFuel = 0 then it yields "unlimited".
| 1.4
|}

Trivia:
During the 1.4 beta, turtle.getFuelLevel() in softcore(that is now turtleneedsfuel = 0) returned 9000.
[[Category:APIs]]

Turtle (API)

2012-09-10T04:02:45Z

Riking: add comment

The Turtle API is used to work with your Turtles.

{| border="1" cellpadding="2" cellspacing="0|"
| colspan="2" | <center>KEY</center>
|-
! Color
! Turtles that can perform this
|-
|White
|All
|-{{row-lightgreen}}
|Green
|Crafty
|-{{row-lightyellow}}
|Yellow
|Mining, Felling, Digging, Farming
|-{{row-lightred}}
|Red
|Any tool
|}


{| border="1" cellpadding="2" cellspacing="0|"
!style="background:#EEE" width="100px"|Return
!style="background:#EEE" width="200px"|Method name
!style="background:#EEE" width="*"|Description
!style="background:#EEE" width="*"|Min version
|-{{row-lightgreen}}
|bool "success"
|[[turtle.craft]]()
|Craft items using ingredients in the nine upper left slots
|
|-
|bool "success"
|[[turtle.forward]]()
|Let the Turtle move forward
|
|-
|bool "success"
|[[turtle.back]]()
|Let the Turtle move back
|
|-
|bool "success"
|[[turtle.up]]()
|Let the Turtle move up
|
|-
|bool "success"
|[[turtle.down]]()
|Let the Turtle move down
|
|-
|bool "true"
|[[turtle.turnLeft]]()
|The Turtle turns left
|
|-
|bool "true"
|[[turtle.turnRight]]()
|The Turtle turns right
|
|-
|bool "slot > 16"
|[[turtle.select]]( slotNum )
|The Turtle selects the given Slot (1 is top left, 16 (9 in 1.33 and earlier) is bottom right)
|
|-
|int "result"
|[[turtle.getItemCount]]( slotNum )
|Counts how many items are in the given Slot
|
|-
|int "result"
|[[turtle.getItemSpace]]( slotNum )
|Counts how many remaining items you need to fill the stack in the given Slot
|
|-{{row-lightred}}
|bool "success"
|[[turtle.attack]]()
|Attacks in front of the turtle.
| 1.4
|-{{row-lightred}}
|bool "success"
|[[turtle.attackUp]]()
|Attacks over the turtle.
| 1.4
|-{{row-lightred}}
|bool "success"
|[[turtle.attackDown]]()
|Attacks under the turtle.
| 1.4
|-{{row-lightyellow}}
|bool "success"
|[[turtle.dig]]()
|Breaks the Block in front. With hoe: tills the dirt in front of it.
|
|-{{row-lightyellow}}
|bool "success"
|[[turtle.digUp]]()
|Breaks the Block above. With hoe: tills the dirt above it.
|
|-{{row-lightyellow}}
|bool "success"
|[[turtle.digDown]]()
|Breaks the Block below. With hoe: tills the dirt below it.
|
|-
|nil
|[[turtle.place]]( [signText] )
|Places a Block of the selected slot in front. Engrave [signText] on signs if provided.
| 1.4
|-
|nil
|[[turtle.placeUp]]()
|Places a Block of the selected slot above
|
|-
|nil
|[[turtle.placeDown]]()
|Places a Block of the selected slot below
|
|-
|bool "result"
|[[turtle.detect]]()
|Detects if there is a Block in front
|
|-
|bool "result"
|[[turtle.detectUp]]()
|Detects if there is a Block above
|
|-
|bool "result"
|[[turtle.detectDown]]()
|Detects if there is a Block below
|
|-
|bool "result"
|[[turtle.compare]]()
|Detects if the block in front is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareUp]]()
|Detects if the block above is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareDown]]()
|Detects if the block below is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareTo]]( [slot] )
|Compare the current selected slot and the given slot to see if the items are the same, yields true if they are the same, and false if not.
| 1.4
|-
|bool "success"
|[[turtle.drop]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e in front of the turtle) it will try to place into the inventory, returning false if the inventory is full.
|
|-
|bool "success"
|[[turtle.drop|turtle.dropUp]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e above the turtle) it will try to place into the inventory, returning false if the inventory is full. If below a furnace, will place item in the bottom slot.
|
|-
|bool "success"
|[[turtle.drop|turtle.dropDown]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e below the turtle) it will try to place into the inventory, returning false if the inventory is full. If above a furnace, will place item in the top slot.
|
|-
|bool "success"
|[[turtle.suck]]()
|Picks up an item stack of any number, from the ground or an inventory in front of the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.suckUp]]()
|Picks up an item stack of any number, from the ground or an inventory above the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.suckDown]]()
|Picks up an item stack of any number, from the ground or an inventory below the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.refuel]]()
|If the current selected slot contains a fuel item, it will consume it to give the turtle the ability to move. Added in 1.4 and is only needed in needfuel mode. If the current slot doesn't contain a fuel item, it yields false. Fuel values for different items can be found at [[Turtle.refuel#Fuel_Values]].
| 1.4
|-
|int "fuel"
|[[turtle.getFuelLevel]]()
|Returns the current fuel level of the turtle, this is the number of blocks the turtle can move. If turtleNeedFuel = 0 then it yields "unlimited".
| 1.4
|}

Trivia:
During the 1.4 beta, turtle.getFuelLevel() in softcore(that is now turtleneedsfuel = 0) returned 9000.
[[Category:APIs]]

Turtle (API)

2012-09-10T04:01:15Z

Riking: sp: tiles -> tills

The Turtle API is used to work with your Turtles.

{| border="1" cellpadding="2" cellspacing="0|"
| colspan="2" | <center>KEY</center>
|-
! Color
! Turtles that can perform this
|-
|White
|All
|-{{row-lightgreen}}
|Green
|Crafty
|-{{row-lightyellow}}
|Yellow
|Mining, Felling, Digging
|-{{row-lightred}}
|Red
|Any tool
|}

{| border="1" cellpadding="2" cellspacing="0|"
!style="background:#EEE" width="100px"|Return
!style="background:#EEE" width="200px"|Method name
!style="background:#EEE" width="*"|Description
!style="background:#EEE" width="*"|Min version
|-{{row-lightgreen}}
|bool "success"
|[[turtle.craft]]()
|Craft items using ingredients in the nine upper left slots
|
|-
|bool "success"
|[[turtle.forward]]()
|Let the Turtle move forward
|
|-
|bool "success"
|[[turtle.back]]()
|Let the Turtle move back
|
|-
|bool "success"
|[[turtle.up]]()
|Let the Turtle move up
|
|-
|bool "success"
|[[turtle.down]]()
|Let the Turtle move down
|
|-
|bool "true"
|[[turtle.turnLeft]]()
|The Turtle turns left
|
|-
|bool "true"
|[[turtle.turnRight]]()
|The Turtle turns right
|
|-
|bool "slot > 16"
|[[turtle.select]]( slotNum )
|The Turtle selects the given Slot (1 is top left, 16 (9 in 1.33 and earlier) is bottom right)
|
|-
|int "result"
|[[turtle.getItemCount]]( slotNum )
|Counts how many items are in the given Slot
|
|-
|int "result"
|[[turtle.getItemSpace]]( slotNum )
|Counts how many remaining items you need to fill the stack in the given Slot
|
|-{{row-lightred}}
|bool "success"
|[[turtle.attack]]()
|Attacks in front of the turtle.
| 1.4
|-{{row-lightred}}
|bool "success"
|[[turtle.attackUp]]()
|Attacks over the turtle.
| 1.4
|-{{row-lightred}}
|bool "success"
|[[turtle.attackDown]]()
|Attacks under the turtle.
| 1.4
|-{{row-lightyellow}}
|bool "success"
|[[turtle.dig]]()
|Breaks the Block in front. With hoe: tills the dirt in front of it.
|
|-{{row-lightyellow}}
|bool "success"
|[[turtle.digUp]]()
|Breaks the Block above. With hoe: tills the dirt above it.
|
|-{{row-lightyellow}}
|bool "success"
|[[turtle.digDown]]()
|Breaks the Block below. With hoe: tills the dirt below it.
|
|-
|nil
|[[turtle.place]]( [signText] )
|Places a Block of the selected slot in front. Engrave [signText] on signs if provided.
| 1.4
|-
|nil
|[[turtle.placeUp]]()
|Places a Block of the selected slot above
|
|-
|nil
|[[turtle.placeDown]]()
|Places a Block of the selected slot below
|
|-
|bool "result"
|[[turtle.detect]]()
|Detects if there is a Block in front
|
|-
|bool "result"
|[[turtle.detectUp]]()
|Detects if there is a Block above
|
|-
|bool "result"
|[[turtle.detectDown]]()
|Detects if there is a Block below
|
|-
|bool "result"
|[[turtle.compare]]()
|Detects if the block in front is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareUp]]()
|Detects if the block above is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareDown]]()
|Detects if the block below is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareTo]]( [slot] )
|Compare the current selected slot and the given slot to see if the items are the same, yields true if they are the same, and false if not.
| 1.4
|-
|bool "success"
|[[turtle.drop]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e in front of the turtle) it will try to place into the inventory, returning false if the inventory is full.
|
|-
|bool "success"
|[[turtle.drop|turtle.dropUp]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e above the turtle) it will try to place into the inventory, returning false if the inventory is full. If below a furnace, will place item in the bottom slot.
|
|-
|bool "success"
|[[turtle.drop|turtle.dropDown]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e below the turtle) it will try to place into the inventory, returning false if the inventory is full. If above a furnace, will place item in the top slot.
|
|-
|bool "success"
|[[turtle.suck]]()
|Picks up an item stack of any number, from the ground or an inventory in front of the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.suckUp]]()
|Picks up an item stack of any number, from the ground or an inventory above the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.suckDown]]()
|Picks up an item stack of any number, from the ground or an inventory below the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.refuel]]()
|If the current selected slot contains a fuel item, it will consume it to give the turtle the ability to move. Added in 1.4 and is only needed in needfuel mode. If the current slot doesn't contain a fuel item, it yields false. Fuel values for different items can be found at [[Turtle.refuel#Fuel_Values]].
| 1.4
|-
|int "fuel"
|[[turtle.getFuelLevel]]()
|Returns the current fuel level of the turtle, this is the number of blocks the turtle can move. If turtleNeedFuel = 0 then it yields "unlimited".
| 1.4
|}

Trivia:
During the 1.4 beta, turtle.getFuelLevel() in softcore(that is now turtleneedsfuel = 0) returned 9000.
[[Category:APIs]]

Turtle

2012-09-09T06:09:47Z

Riking: /* Recipes */ doop

'''Turtles''' are essentially robots, and were added in the 1.3 update. They run an OS (like the [[Console|consoles]]) named [[TurtleOS]]. They have the ability to place, break and detect blocks, move around and drop items in their inventory. The programs they run are stored on its internal memory or [[Floppy Disk|floppy disks]].

The 1.4 update was focused on turtles and added new tools for them to use. Turtles can now in addition to pickaxes use: Hoes, crafting tables, axes, shovels and sword. The update also included a new fuel system for the turtles. Turtles also got an inventory upgrade from 9 slots to 16.

Turtles are submersible and lavaproof. As such, they are extremely useful for mining near bedrock, where heavy lava flows can prevent access to diamonds and other rare finds.

If you would like to know more about how to program them, have a look at the [[Turtle (API)|Turtle API]].

==Floppy Disks==
Turtles do not have a built-in floppy drive. As such they need a floppy drive placed beside them to access disks. However if the turtle is a Wireless turtle, the floppy drive and other peripherals must be placed on a side other than the side the wireless modem is on.

==Power source==
Turtles run on fuel. Fuel is any item that works in a regular furnace, like coal and lava. The turtle gains 0.6 movement per half second the fuel would have burnt in a furnace.
The turtle can move 1 block for each fuel count it got, for example, coal yields 96 block movements. For more information, go to the [[Turtle.refuel]] page.

=== Optional Non-fuel mode ===

In this mode turtles use their internal redstone engine, they do not need to be re-charged, or any other form of external power.
This is because redstone continuously emits low levels of energy, and the turtle's engine is very efficient.
This mode can be turned on by editing the turtle config file (config/mod_CCTurtle.cfg) and setting turtleNeedsFuel to 0.

==Farming==
Turtles equipped with a hoe can till dirt.

==Mining==
Turtles crafted with a [[diamond pickaxe]], [[diamond axe]], or [[diamond shovel]], can break blocks, mine wood, and even break dirt and gravel, depending on the tool you used on it. The tools equipped on the turtle have no durability, and so can be used indefinitely without the need for any additional materials. When a turtle breaks the block it gets the item directly into its inventory. Different tools yields different drop, for example, an axe can break anything, but it won't get ores.

==Crafting==
Turtles equipped with a workbench can craft items. When crafting, the inventory must be clear of all items other than the ones needed for the recipe.

==Melee==
Turtles equipped with a sword can attack players and mobs. When a turtle kills a mob it will leave the experience orbs on the ground, but add the loot to it's inventory. Turtles can also attack with any tool, where axe is the second best after the sword.

==Recipes==

{|
|+'''Crafting ingredients'''
|-
|Turtle
|{{Crafting grid
|A1=iron_ingot |B1=iron_ingot |C1=iron_ingot
|A2=iron_ingot |B2=console |C2=iron_ingot
|A3=iron_ingot |B3=chest |C3=iron_ingot
|Output=turtle
}}
|}
Turtles can be equipped with different peripherals and tools. A turtle can only have one tool and one peripheral.
 The following tools can be equipped to a turtles: [[diamond pickaxe]], [[diamond axe]], [[diamond shovel]], [[diamond hoe]] and [[diamond sword]]
 The following peripherals can be equipped to a turtles: [[modem|wireless modem]] and [[crafting table]].
 '''Turtle recipe and examples for equipping a turtle with tools and peripherals.'''
{| border="1" cellpadding="2" cellspacing="0|"
!style="background:#EEE" width="100px"|
!style="background:#EEE" |None
!style="background:#EEE" |Crafting
!style="background:#EEE" |Wireless
|-
!style="background:#EEE" |None
|{{Crafting grid
|B2=turtle
|Output=turtle
}}
|{{Crafting grid
|B2=turtle |A2=workbench
|Output=crafting_turtle
}}
|{{Crafting grid
|B2=turtle |A2=modem
|Output=wireless_turtle
}}
|-
!style="background:#EEE" |Mining
|{{Crafting grid
|B2=turtle |C2=diamond_pickaxe
|Output=mining_turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_pickaxe
|Output=crafting_mining_turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_pickaxe
|Output=wireless_mining_turtle
}}
|-
!style="background:#EEE" |Farming
|{{Crafting grid
|B2=turtle |C2=diamond_hoe
|Output=farming_turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_hoe
|Output=crafting_farming_turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_hoe
|Output=wireless_farming_turtle
}}
|-
!style="background:#EEE" |Melee
|{{Crafting grid
|B2=turtle |C2=diamond_sword
|Output=melee_turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_sword
|Output=crafting_melee_turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_sword
|Output=wireless_melee_turtle
}}
|-
!style="background:#EEE" |Felling
|{{Crafting grid
|B2=turtle |C2=diamond_axe
|Output=felling_turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_axe
|Output=crafting_felling_turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_axe
|Output=wireless_felling_turtle
}}
|-
!style="background:#EEE" |Digging
|{{Crafting grid
|B2=turtle |C2=diamond_shovel
|Output=digging_turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_shovel
|Output=crafting_digging_turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_shovel
|Output=wireless_digging_turtle
}}
|}
[[Category:Blocks]]

Turtle

2012-09-09T06:09:04Z

Riking: we require additional tables

'''Turtles''' are essentially robots, and were added in the 1.3 update. They run an OS (like the [[Console|consoles]]) named [[TurtleOS]]. They have the ability to place, break and detect blocks, move around and drop items in their inventory. The programs they run are stored on its internal memory or [[Floppy Disk|floppy disks]].

The 1.4 update was focused on turtles and added new tools for them to use. Turtles can now in addition to pickaxes use: Hoes, crafting tables, axes, shovels and sword. The update also included a new fuel system for the turtles. Turtles also got an inventory upgrade from 9 slots to 16.

Turtles are submersible and lavaproof. As such, they are extremely useful for mining near bedrock, where heavy lava flows can prevent access to diamonds and other rare finds.

If you would like to know more about how to program them, have a look at the [[Turtle (API)|Turtle API]].

==Floppy Disks==
Turtles do not have a built-in floppy drive. As such they need a floppy drive placed beside them to access disks. However if the turtle is a Wireless turtle, the floppy drive and other peripherals must be placed on a side other than the side the wireless modem is on.

==Power source==
Turtles run on fuel. Fuel is any item that works in a regular furnace, like coal and lava. The turtle gains 0.6 movement per half second the fuel would have burnt in a furnace.
The turtle can move 1 block for each fuel count it got, for example, coal yields 96 block movements. For more information, go to the [[Turtle.refuel]] page.

=== Optional Non-fuel mode ===

In this mode turtles use their internal redstone engine, they do not need to be re-charged, or any other form of external power.
This is because redstone continuously emits low levels of energy, and the turtle's engine is very efficient.
This mode can be turned on by editing the turtle config file (config/mod_CCTurtle.cfg) and setting turtleNeedsFuel to 0.

==Farming==
Turtles equipped with a hoe can till dirt.

==Mining==
Turtles crafted with a [[diamond pickaxe]], [[diamond axe]], or [[diamond shovel]], can break blocks, mine wood, and even break dirt and gravel, depending on the tool you used on it. The tools equipped on the turtle have no durability, and so can be used indefinitely without the need for any additional materials. When a turtle breaks the block it gets the item directly into its inventory. Different tools yields different drop, for example, an axe can break anything, but it won't get ores.

==Crafting==
Turtles equipped with a workbench can craft items. When crafting, the inventory must be clear of all items other than the ones needed for the recipe.

==Melee==
Turtles equipped with a sword can attack players and mobs. When a turtle kills a mob it will leave the experience orbs on the ground, but add the loot to it's inventory. Turtles can also attack with any tool, where axe is the second best after the sword.

==Recipes==

{|
|+'''Crafting ingredients'''
|-
|Turtle
|{{Crafting grid
|A1=iron_ingot |B1=iron_ingot |C1=iron_ingot
|A2=iron_ingot |B2=console |C2=iron_ingot
|A3=iron_ingot |B3=chest |C3=iron_ingot
|Output=turtle
}}
|}
Turtles can be equipped with different peripherals and tools. A turtle can only have one tool and one peripheral.
 The following tools can be equipped to a turtles: [[diamond pickaxe]], [[diamond axe]], [[diamond shovel]], [[diamond hoe]] and [[diamond sword]]
 The following peripherals can be equipped to a turtles: [[modem|wireless modem]] and [[crafting table]].
 '''Turtle recipe and examples for equipping a turtle with tools and peripherals.'''
{| border="1" cellpadding="2" cellspacing="0|"
!style="background:#EEE" width="100px"|
!style="background:#EEE" |None
!style="background:#EEE" |Crafting
!style="background:#EEE" |Wireless
!style="background:#EEE" |Melee
!style="background:#EEE" |Felling
!style="background:#EEE" |Digging
|-
!style="background:#EEE" |None
|{{Crafting grid
|B2=turtle
|Output=turtle
}}
|{{Crafting grid
|B2=turtle |A2=workbench
|Output=crafting_turtle
}}
|{{Crafting grid
|B2=turtle |A2=modem
|Output=wireless_turtle
}}
|-
!style="background:#EEE" |Mining
|{{Crafting grid
|B2=turtle |C2=diamond_pickaxe
|Output=mining_turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_pickaxe
|Output=crafting_mining_turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_pickaxe
|Output=wireless_mining_turtle
}}
|-
!style="background:#EEE" |Farming
|{{Crafting grid
|B2=turtle |C2=diamond_hoe
|Output=farming_turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_hoe
|Output=crafting_farming_turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_hoe
|Output=wireless_farming_turtle
}}
|-
!style="background:#EEE" |Melee
|{{Crafting grid
|B2=turtle |C2=diamond_sword
|Output=melee_turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_sword
|Output=crafting_melee_turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_sword
|Output=wireless_melee_turtle
}}
|-
!style="background:#EEE" |Felling
|{{Crafting grid
|B2=turtle |C2=diamond_axe
|Output=felling_turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_axe
|Output=crafting_felling_turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_axe
|Output=wireless_felling_turtle
}}
|-
!style="background:#EEE" |Digging
|{{Crafting grid
|B2=turtle |C2=diamond_shovel
|Output=digging_turtle
}}
|{{Crafting grid
|A2=workbench |B2=turtle |C2=diamond_shovel
|Output=crafting_digging_turtle
}}
|{{Crafting grid
|A2=modem |B2=turtle |C2=diamond_shovel
|Output=wireless_digging_turtle
}}
|}
[[Category:Blocks]]

Turtle (API)

2012-09-09T05:55:51Z

Riking:

The Turtle API is used to work with your Turtles.

{| border="1" cellpadding="2" cellspacing="0|"
| colspan="2" | <center>KEY</center>
|-
! Color
! Turtles that can perform this
|-
|White
|All
|-{{row-lightgreen}}
|Green
|Crafty
|-{{row-lightyellow}}
|Yellow
|Mining, Felling, Digging
|-{{row-lightred}}
|Red
|Melee, Felling
|}

{| border="1" cellpadding="2" cellspacing="0|"
!style="background:#EEE" width="100px"|Return
!style="background:#EEE" width="200px"|Method name
!style="background:#EEE" width="*"|Description
!style="background:#EEE" width="*"|Min version
|-{{row-lightgreen}}
|bool "success"
|[[turtle.craft]]()
|Craft items using ingredients in the nine upper left slots
|
|-
|bool "success"
|[[turtle.forward]]()
|Let the Turtle move forward
|
|-
|bool "success"
|[[turtle.back]]()
|Let the Turtle move back
|
|-
|bool "success"
|[[turtle.up]]()
|Let the Turtle move up
|
|-
|bool "success"
|[[turtle.down]]()
|Let the Turtle move down
|
|-
|bool "true"
|[[turtle.turnLeft]]()
|The Turtle turns left
|
|-
|bool "true"
|[[turtle.turnRight]]()
|The Turtle turns right
|
|-
|bool "slot > 16"
|[[turtle.select]]( slotNum )
|The Turtle selects the given Slot (1 is top left, 16 (9 in 1.33 and earlier) is bottom right)
|
|-
|int "result"
|[[turtle.getItemCount]]( slotNum )
|Counts how many items are in the given Slot
|
|-
|int "result"
|[[turtle.getItemSpace]]( slotNum )
|Counts how many remaining items you need to fill the stack in the given Slot
|
|-{{row-lightred}}
|??
|[[turtle.attack]]()
|Attacks in front of the turtle.
| 1.4
|-{{row-lightred}}
|??
|[[turtle.attackUp]]()
|Attacks over the turtle.
| 1.4
|-{{row-lightred}}
|??
|[[turtle.attackDown]]()
|Attacks under the turtle.
| 1.4
|-{{row-lightyellow}}
|bool "success"
|[[turtle.dig]]()
|Breaks the Block in front
|
|-{{row-lightyellow}}
|bool "success"
|[[turtle.digUp]]()
|Breaks the Block above
|
|-{{row-lightyellow}}
|bool "success"
|[[turtle.digDown]]()
|Breaks the Block below
|
|-
|nil
|[[turtle.place]]( [signText] )
|Places a Block of the selected slot in front. Engrave [signText] on signs if provided.
| 1.4
|-
|nil
|[[turtle.placeUp]]()
|Places a Block of the selected slot above
|
|-
|nil
|[[turtle.placeDown]]()
|Places a Block of the selected slot below
|
|-
|bool "result"
|[[turtle.detect]]()
|Detects if there is a Block in front
|
|-
|bool "result"
|[[turtle.detectUp]]()
|Detects if there is a Block above
|
|-
|bool "result"
|[[turtle.detectDown]]()
|Detects if there is a Block below
|
|-
|bool "result"
|[[turtle.compare]]()
|Detects if the block in front is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareUp]]()
|Detects if the block above is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareDown]]()
|Detects if the block below is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareTo]]( [slot] )
|Compare the current selected slot and the given slot to see if the items are the same, yields true if they are the same, and false if not.
| 1.4
|-
|bool "success"
|[[turtle.drop]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e in front of the turtle) it will try to place into the inventory, returning false if the inventory is full.
|
|-
|bool "success"
|[[turtle.drop|turtle.dropUp]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e above the turtle) it will try to place into the inventory, returning false if the inventory is full. If below a furnace, will place item in the bottom slot.
|
|-
|bool "success"
|[[turtle.drop|turtle.dropDown]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e below the turtle) it will try to place into the inventory, returning false if the inventory is full. If above a furnace, will place item in the top slot.
|
|-
|bool "success"
|[[turtle.suck]]()
|Picks up an item stack of any number, from the ground or an inventory in front of the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.suckUp]]()
|Picks up an item stack of any number, from the ground or an inventory above the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.suckDown]]()
|Picks up an item stack of any number, from the ground or an inventory below the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.refuel]]()
|If the current selected slot contains a fuel item, it will consume it to give the turtle the ability to move. Added in 1.4 and is only needed in hardcore turtle mode. If the current slot doesn't contain a fuel item, it yields false. Fuel values for different items can be found at [[Turtle.refuel#Fuel_Values]].
| 1.4
|-
|int "fuel"
|[[turtle.getFuelLevel]]()
|Returns the current fuel level of the turtle, this is the number of blocks the turtle can move. If turtleNeedFuel = 0 then it yields "unlimited".
| 1.4
|}

Trivia:
During the 1.4 beta, turtle.getFuelLevel() in softcore(that is now turtleneedsfuel = 0) returned 9000.
[[Category:APIs]]

Turtle (API)

2012-09-09T05:55:16Z

Riking: Add colors to attack commands

The Turtle API is used to work with your Turtles.

{| border="1" cellpadding="2" cellspacing="0|"
| colspan="2" | <center>KEY</center>
|-
! Color
! Turtles that can perform this
|-
|White
|All
|-{{row-lightgreen}}
|Green
|Crafty
|-{{row-lightyellow}}
|Yellow
|Mining, Felling
|-{{row-lightred}}
|Red
|Melee, Felling
|}

{| border="1" cellpadding="2" cellspacing="0|"
!style="background:#EEE" width="100px"|Return
!style="background:#EEE" width="200px"|Method name
!style="background:#EEE" width="*"|Description
!style="background:#EEE" width="*"|Min version
|-{{row-lightgreen}}
|bool "success"
|[[turtle.craft]]()
|Craft items using ingredients in the nine upper left slots
|
|-
|bool "success"
|[[turtle.forward]]()
|Let the Turtle move forward
|
|-
|bool "success"
|[[turtle.back]]()
|Let the Turtle move back
|
|-
|bool "success"
|[[turtle.up]]()
|Let the Turtle move up
|
|-
|bool "success"
|[[turtle.down]]()
|Let the Turtle move down
|
|-
|bool "true"
|[[turtle.turnLeft]]()
|The Turtle turns left
|
|-
|bool "true"
|[[turtle.turnRight]]()
|The Turtle turns right
|
|-
|bool "slot > 16"
|[[turtle.select]]( slotNum )
|The Turtle selects the given Slot (1 is top left, 16 (9 in 1.33 and earlier) is bottom right)
|
|-
|int "result"
|[[turtle.getItemCount]]( slotNum )
|Counts how many items are in the given Slot
|
|-
|int "result"
|[[turtle.getItemSpace]]( slotNum )
|Counts how many remaining items you need to fill the stack in the given Slot
|
|-{{row-lightred}}
|??
|[[turtle.attack]]()
|Attacks in front of the turtle.
| 1.4
|-{{row-lightred}}
|??
|[[turtle.attackUp]]()
|Attacks over the turtle.
| 1.4
|-{{row-lightred}}
|??
|[[turtle.attackDown]]()
|Attacks under the turtle.
| 1.4
|-{{row-lightyellow}}
|bool "success"
|[[turtle.dig]]()
|Breaks the Block in front
|
|-{{row-lightyellow}}
|bool "success"
|[[turtle.digUp]]()
|Breaks the Block above
|
|-{{row-lightyellow}}
|bool "success"
|[[turtle.digDown]]()
|Breaks the Block below
|
|-
|nil
|[[turtle.place]]( [signText] )
|Places a Block of the selected slot in front. Engrave [signText] on signs if provided.
| 1.4
|-
|nil
|[[turtle.placeUp]]()
|Places a Block of the selected slot above
|
|-
|nil
|[[turtle.placeDown]]()
|Places a Block of the selected slot below
|
|-
|bool "result"
|[[turtle.detect]]()
|Detects if there is a Block in front
|
|-
|bool "result"
|[[turtle.detectUp]]()
|Detects if there is a Block above
|
|-
|bool "result"
|[[turtle.detectDown]]()
|Detects if there is a Block below
|
|-
|bool "result"
|[[turtle.compare]]()
|Detects if the block in front is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareUp]]()
|Detects if the block above is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareDown]]()
|Detects if the block below is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareTo]]( [slot] )
|Compare the current selected slot and the given slot to see if the items are the same, yields true if they are the same, and false if not.
| 1.4
|-
|bool "success"
|[[turtle.drop]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e in front of the turtle) it will try to place into the inventory, returning false if the inventory is full.
|
|-
|bool "success"
|[[turtle.drop|turtle.dropUp]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e above the turtle) it will try to place into the inventory, returning false if the inventory is full. If below a furnace, will place item in the bottom slot.
|
|-
|bool "success"
|[[turtle.drop|turtle.dropDown]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e below the turtle) it will try to place into the inventory, returning false if the inventory is full. If above a furnace, will place item in the top slot.
|
|-
|bool "success"
|[[turtle.suck]]()
|Picks up an item stack of any number, from the ground or an inventory in front of the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.suckUp]]()
|Picks up an item stack of any number, from the ground or an inventory above the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.suckDown]]()
|Picks up an item stack of any number, from the ground or an inventory below the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.refuel]]()
|If the current selected slot contains a fuel item, it will consume it to give the turtle the ability to move. Added in 1.4 and is only needed in hardcore turtle mode. If the current slot doesn't contain a fuel item, it yields false. Fuel values for different items can be found at [[Turtle.refuel#Fuel_Values]].
| 1.4
|-
|int "fuel"
|[[turtle.getFuelLevel]]()
|Returns the current fuel level of the turtle, this is the number of blocks the turtle can move. If turtleNeedFuel = 0 then it yields "unlimited".
| 1.4
|}

Trivia:
During the 1.4 beta, turtle.getFuelLevel() in softcore(that is now turtleneedsfuel = 0) returned 9000.
[[Category:APIs]]

Template:Row-lightred

2012-09-09T05:54:48Z

Riking:

style="background:#ff879c;"

Template:Row-lightred

2012-09-09T05:54:32Z

Riking:

style="background:#ff474c;"

Template:Row-lightred

2012-09-09T05:54:05Z

Riking:

style="background:#d9544d;"

Turtle (API)

2012-09-09T05:52:39Z

Riking:

The Turtle API is used to work with your Turtles.

{| border="1" cellpadding="2" cellspacing="0|"
| colspan="2" | <center>KEY</center>
|-
! Color
! Turtles that can perform this
|-
|White
|All
|-{{row-lightgreen}}
|Green
|Crafty
|-{{row-lightyellow}}
|Yellow
|Mining, Felling
|}

{| border="1" cellpadding="2" cellspacing="0|"
!style="background:#EEE" width="100px"|Return
!style="background:#EEE" width="200px"|Method name
!style="background:#EEE" width="*"|Description
!style="background:#EEE" width="*"|Min version
|-{{row-lightgreen}}
|bool "success"
|[[turtle.craft]]()
|Craft items using ingredients in the nine upper left slots
|
|-
|bool "success"
|[[turtle.forward]]()
|Let the Turtle move forward
|
|-
|bool "success"
|[[turtle.back]]()
|Let the Turtle move back
|
|-
|bool "success"
|[[turtle.up]]()
|Let the Turtle move up
|
|-
|bool "success"
|[[turtle.down]]()
|Let the Turtle move down
|
|-
|bool "true"
|[[turtle.turnLeft]]()
|The Turtle turns left
|
|-
|bool "true"
|[[turtle.turnRight]]()
|The Turtle turns right
|
|-
|bool "slot > 16"
|[[turtle.select]]( slotNum )
|The Turtle selects the given Slot (1 is top left, 16 (9 in 1.33 and earlier) is bottom right)
|
|-
|int "result"
|[[turtle.getItemCount]]( slotNum )
|Counts how many items are in the given Slot
|
|-
|int "result"
|[[turtle.getItemSpace]]( slotNum )
|Counts how many remaining items you need to fill the stack in the given Slot
|
|-
|??
|[[turtle.attack]]()
|Attacks in front of the turtle.
| 1.4
|-
|??
|[[turtle.attackUp]]()
|Attacks over the turtle.
| 1.4
|-
|??
|[[turtle.attackDown]]()
|Attacks under the turtle.
| 1.4
|-{{row-lightyellow}}
|bool "success"
|[[turtle.dig]]()
|Breaks the Block in front
|
|-{{row-lightyellow}}
|bool "success"
|[[turtle.digUp]]()
|Breaks the Block above
|
|-{{row-lightyellow}}
|bool "success"
|[[turtle.digDown]]()
|Breaks the Block below
|
|-
|nil
|[[turtle.place]]( [signText] )
|Places a Block of the selected slot in front. Engrave [signText] on signs if provided.
| 1.4
|-
|nil
|[[turtle.placeUp]]()
|Places a Block of the selected slot above
|
|-
|nil
|[[turtle.placeDown]]()
|Places a Block of the selected slot below
|
|-
|bool "result"
|[[turtle.detect]]()
|Detects if there is a Block in front
|
|-
|bool "result"
|[[turtle.detectUp]]()
|Detects if there is a Block above
|
|-
|bool "result"
|[[turtle.detectDown]]()
|Detects if there is a Block below
|
|-
|bool "result"
|[[turtle.compare]]()
|Detects if the block in front is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareUp]]()
|Detects if the block above is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareDown]]()
|Detects if the block below is the same as the one in the currently selected slot
|
|-
|bool "result"
|[[turtle.compareTo]]( [slot] )
|Compare the current selected slot and the given slot to see if the items are the same, yields true if they are the same, and false if not.
| 1.4
|-
|bool "success"
|[[turtle.drop]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e in front of the turtle) it will try to place into the inventory, returning false if the inventory is full.
|
|-
|bool "success"
|[[turtle.drop|turtle.dropUp]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e above the turtle) it will try to place into the inventory, returning false if the inventory is full. If below a furnace, will place item in the bottom slot.
|
|-
|bool "success"
|[[turtle.drop|turtle.dropDown]]( [count] )
|Drops all items in the selected slot, or if [count] is specified, drops that many items. [>= 1.4 only:] If there is a inventory on the side (i.e below the turtle) it will try to place into the inventory, returning false if the inventory is full. If above a furnace, will place item in the top slot.
|
|-
|bool "success"
|[[turtle.suck]]()
|Picks up an item stack of any number, from the ground or an inventory in front of the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.suckUp]]()
|Picks up an item stack of any number, from the ground or an inventory above the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.suckDown]]()
|Picks up an item stack of any number, from the ground or an inventory below the turtle. If the turtle can't pick up the item, the function yields false.
| 1.4
|-
|bool "success"
|[[turtle.refuel]]()
|If the current selected slot contains a fuel item, it will consume it to give the turtle the ability to move. Added in 1.4 and is only needed in hardcore turtle mode. If the current slot doesn't contain a fuel item, it yields false. Fuel values for different items can be found at [[Turtle.refuel#Fuel_Values]].
| 1.4
|-
|int "fuel"
|[[turtle.getFuelLevel]]()
|Returns the current fuel level of the turtle, this is the number of blocks the turtle can move. If turtleNeedFuel = 0 then it yields "unlimited".
| 1.4
|}

Trivia:
During the 1.4 beta, turtle.getFuelLevel() in softcore(that is now turtleneedsfuel = 0) returned 9000.
[[Category:APIs]]

Template:Row-lightyellow

2012-09-09T05:49:03Z

Riking: Created page with "style="background:#fffe7a;""

style="background:#fffe7a;"

Template:Row-lightgreen

2012-09-09T05:22:02Z

Riking: Created page with "style="background:#8fff9f;""

style="background:#8fff9f;"

Template:Row-lightred

2012-09-09T05:21:13Z

Riking: Created page with "style="background:#ffd1df;""

style="background:#ffd1df;"

CcSensors

2012-09-01T21:19:10Z

Riking:

{{DISPLAYTITLE:ccSensors}}
'''ccSensors''' is a user created peripheral by Yoskaz01, which adds sensors to ComputerCraft. It provides readings from the Minecraft surroundings to lua programs.
A reading can be a value a simple as Light level, a isRaining, isDay or as complex as the content of a chest or the temperature of IC2 reactor.

==Getting Started==

# place a Sensor Controller next to a computer
# open the sensor Controller GUI and hit the "New" button to register a new freq
# place blank transmitter card in the slot and click "Encode Transmitter" to get an encoded transmitter to be used with the remote sensor.
# Place a Remote Sensor (can be placed anywhere) and put the transmitter card in the bottom slot. (you can rename the Remote Sensor from the default name "Sensor")
# Place a SensorModule card into the top slot.
# open the computer terminal and run: /ccSensors/console to run the sample console program. That's it - you now have a working sensor connected to a computer :)

==API: sensors==
Note: Documentation is ripped from source code. Information is provided "as-is" with no guarntee of accuracy.

{| class="sortable" border="1" cellpadding="2" cellspacing="0"
!style="background:#EEE" width="200px"|Method name
!style="background:#EEE" width="*"|Description
|-
|getVersion()
|sensorAPI version
|-
|getPeripherals()
|returns a dict of attached peripherals : SensorController,monitor,modem
|-
|getController()
|return the side the first controller is attached at
|-
|rIterator( table )
|Intended for internal use only.
|-
|tabtodict( table )
|Intended for internal use only.
|-
|getReadingAsTable( side, sensor, ... )
|return sensor reading as a table instead of a dict
|-
|setTarget( side, sensor, target )
|set the active target for a given sensor
|-
|setSensorRange( side, sensor, range )
|set the sensor range (as long is < max_sensor_range)
|-
|getAvailableReadings( side, sensor )
|returns names of all readings available for a given sensor
|-
|setActiveReading( side, sensor, reading )
|set the active reading to be used when getReading is called
|-
|getAvailableTargets( side, sensor )
|returns the available targets for a given sensor
|-
|getAvailableTargetsforProbe( side, sensor, probe )
|UNDOCUMENTED
|-
|getAvailableTargetsforProbe2( side, sensor, probe )
|UNDOCUMENTED
|-
|getProbes( side, sensor )
|UNDOCUMENTED
|-
|getSensorInfo( side, sensor, ... )
|returns the following information for a given sensor: cardType,name,activereading,activereadingid,distance,location,methods,SensorRange
|-
|getSensorInfoAsTable( side, sensor, ... )
|same as getSensorInfo, except as a table
|-
|getReading( side, sensor, ... )
|returns sensor reading in a dict of reading,value pairs
|-
|getReading2( side, sensor, probe, target, ... )
|returns sensor reading in a dict of reading,value pairs
|-
|getSensors( side )
|returns the names of all connected sensors
|-
|getSensorReadingAsDict(side,sensor,target,reading,...)
|get a reading while setting the target and reading type for a given sensor. returns a dictionary
|-
|getSensorReadingAsDict2(side, sensor, probe, target, ...)
|Alias for getReading2
|-
|getSensorReadingAsTable( side, sensor, target, reading, ...)
|get a reading while setting the target and reading type for a given sensor
|-
|getItemInfo(name,content)
|return item info from an inventory dictionary
|-
|getItemsInfo(names,content)
|returns a dict for each item in the given names table with .dmg and .qty
|}

== External links==
*[http://www.computercraft.info/forums2/index.php?/topic/126-mc-125-cc-133-ccsensors-smpssp/ ccSensors]—ComputerCraft Forum Thread

[[Category:User Created Peripherals]]

CcSensors

2012-09-01T18:26:24Z

Riking: Add api docs

{{DISPLAYTITLE:ccSensors}}
'''ccSensors''' is a user created peripheral by Yoskaz01, which adds sensors to ComputerCraft. It provides readings from the Minecraft surroundings to lua programs.
A reading can be a value a simple as Light level, a isRaining, isDay or as complex as the content of a chest or the temperature of IC2 reactor.

==Getting Started==

# place a Sensor Controller next to a computer
# open the sensor Controller GUI and hit the "New" button to register a new freq
# place blank transmitter card in the slot and click "Encode Transmitter" to get an encoded transmitter to be used with the remote sensor.
# Place a Remote Sensor (can be placed anywhere) and put the transmitter card in the bottom slot. (you can rename the Remote Sensor from the default name "Sensor")
# Place a SensorModule card into the top slot.
# open the computer terminal and run: /ccSensors/console to run the sample console program. That's it - you now have a working sensor connected to a computer :)

==API==
Note: Documentation is ripped from source code. Information is provided "as-is" with no guarntee of accuracy.

{| class="sortable" border="1" cellpadding="2" cellspacing="0"
!style="background:#EEE" width="200px"|Method name
!style="background:#EEE" width="*"|Description
|-
|getVersion()
|sensorAPI version
|-
|getPeripherals()
|returns a dict of attached peripherals : SensorController,monitor,modem
|-
|getController()
|return the side the first controller is attached at
|-
|rIterator( table )
|Intended for internal use only.
|-
|tabtodict( table )
|Intended for internal use only.
|-
|getReadingAsTable( side, sensor, ... )
|return sensor reading as a table instead of a dict
|-
|setTarget( side, sensor, target )
|set the active target for a given sensor
|-
|setSensorRange( side, sensor, range )
|set the sensor range (as long is < max_sensor_range)
|-
|getAvailableReadings( side, sensor )
|returns names of all readings available for a given sensor
|-
|setActiveReading( side, sensor, reading )
|set the active reading to be used when getReading is called
|-
|getAvailableTargets( side, sensor )
|returns the available targets for a given sensor
|-
|getAvailableTargetsforProbe( side, sensor, probe )
|UNDOCUMENTED
|-
|getAvailableTargetsforProbe2( side, sensor, probe )
|UNDOCUMENTED
|-
|getProbes( side, sensor )
|UNDOCUMENTED
|-
|getSensorInfo( side, sensor, ... )
|returns the following information for a given sensor: cardType,name,activereading,activereadingid,distance,location,methods,SensorRange
|-
|getSensorInfoAsTable( side, sensor, ... )
|same as getSensorInfo, except as a table
|-
|getReading( side, sensor, ... )
|returns sensor reading in a dict of reading,value pairs
|-
|getReading2( side, sensor, probe, target, ... )
|returns sensor reading in a dict of reading,value pairs
|-
|getSensors( side )
|returns the names of all connected sensors
|-
|getSensorReadingAsDict(side,sensor,target,reading,...)
|get a reading while setting the target and reading type for a given sensor. returns a dictionary
|-
|getSensorReadingAsDict2(side, sensor, probe, target, ...)
|Alias for getReading2
|-
|getSensorReadingAsTable( side, sensor, target, reading, ...)
|get a reading while setting the target and reading type for a given sensor
|-
|getItemInfo(name,content)
|return item info from an inventory dictionary
|-
|getItemsInfo(names,content)
|returns a dict for each item in the given names table with .dmg and .qty
|}

== External links==
*[http://www.computercraft.info/forums2/index.php?/topic/126-mc-125-cc-133-ccsensors-smpssp/ ccSensors]—ComputerCraft Forum Thread

[[Category:User Created Peripherals]]

User talk:24.20.222.206

2012-04-25T19:44:53Z

Riking: create section: Signatures

==Signatures==
Hi! I've noticed that you comment on the talk pages a lot. However, your style isn't all that great. Here's some tips on making your comments look better:
* Put <nowiki>~~~~</nowiki> after your comment to sign it
* Use colons (:) to indent your message, not spaces.
Thank you for trying to help, though. :) [[User:Riking|Riking]] 19:44, 25 April 2012 (UTC)

Talk:Turtle Tutorial

2012-04-25T19:42:39Z

Riking: unsigned template and talkpage cleanup

==I need help==
i need help,i get this error from my code

mine:1: attempt to call nil

PS ( mine is the name of the program) — Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:76.111.25.128|76.111.25.128]] ([[User talk:76.111.25.128|talk]] • [[Special:Contributions/76.111.25.128|contribs]]) 02:04, 23 March 2012
:What is your code? — Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:24.20.222.206|24.20.222.206]] ([[User talk:24.20.222.206|talk]] • [[Special:Contributions/24.20.222.206|contribs]]) 18:15, 26 March 2012

Talk:Adventure

2012-04-25T19:41:12Z

Riking: unsigned template and talkpage cleanup

==Needs a save command==
mmh.. this programm needs a save command.. — Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:Dude|Dude]] ([[User talk:Dude|talk]] • [[Special:Contributions/Dude|contribs]]) 11:34, 11 March 2012
==Information gone==
404, page not found... jk, some MORON edited this page (before me) and now the information is gone. :'( <---me — Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:24.113.51.30|24.113.51.30]] ([[User talk:24.113.51.30|talk]] • [[Special:Contributions/24.113.51.30|contribs]]) 04:49, 2 April 2012‎

Talk:Turtle (API)

2012-04-25T19:38:54Z

Riking: unsigned template

Is there a way to detect a block's type? Preferably without picking it up; it would be nice to be able to write a function to check the block about to be broken against a list of "Do not break" blocks, such as Industrial craft's MFSU, which loses all held power when picked up.

Also I request a way to set server-wide list of blocks immune to the turtle.dig() functions, such as say personal safes (Industrial Craft again).— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:50.131.199.48|50.131.199.48]] ([[User talk:50.131.199.48|talk]] • [[Special:Contributions/50.131.199.48|contribs]]) 
:As far as I know, there's no way to check the block type with the current API. Could be a feature in the future though, never know. {{User:Scarfacial/Signature|22:17 - 8 March 2012}}
::Would be interesting to see if one could write a function for that. {{User:Banane9/Signature|22:43 - 9 March 2012}}
:::i would see it too please. But i dont think that you can make that in a function
:::[[User:Dude|Dude]] 22:13, 9 March 2012 (UTC)

== treefarm ==

i have write a big programm (120 lines) that destory the tree full (with the leaves) when the tree is grown. so the turtle can plant an new tree an beginn at the start. My problem: the programm dont work and i cant find the faults... — Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:Dude|Dude]] ([[User talk:Dude|talk]] • [[Special:Contributions/Dude|contribs]]) 

== Turtle range ==
I've made a simple program that takes the turtle 30 spaces up into the air, and then drives X number of times forward, then X number of times backwards then lands.

It works fine for small values of X (5, 10, 30, 100).. But when I put it to 300, my turtle never returned. I could not find it when walking along it's course either

Is there a way to make minecraft process chunks that has a turtle in it, or is this a limitation to minecraft it's not possible to work around?— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:62.16.170.203|62.16.170.203]] ([[User talk:62.16.170.203|talk]] • [[Special:Contributions/62.16.170.203|contribs]])

Talk:Redstone (API)

2012-04-25T19:36:59Z

Riking: unsigned template and talkpage cleanup

==(no title)==
i tried to do it but for some reason it didnt work, i tried:

sleep(5) 
setBundledOutput(orange,back,magenta) 
sleep(0.5) 
setBundledOutput(orange,back,magenta) 

and after the 5 seconds, it puts:
"redtest:2: attempt to call nil"

how the heck does it work? how can i get it to work? someone plez reply lol, im new to lua so i know very little about lua... — Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:98.127.192.199|98.127.192.199]] ([[User talk:98.127.192.199|talk]] • [[Special:Contributions/98.127.192.199|contribs]]) 

: First of all, where's the function declaration? You call redtest(), but the error tells that it doesn't exist. Second, use redstone.setBundledOutput() or rs.setBundledOutput(). [[User:Wukl|Wukl]] 09:12, 9 April 2012 (UTC)

User talk:Chrispaul3

2012-04-25T19:35:25Z

Riking: Blanked spam account's talk page

Talk:Making a Delay function

2012-04-25T19:34:03Z

Riking: unsigned template

==Useless Page?==
There's already sleep(seconds), there's no need for this page? — Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:24.20.222.206|24.20.222.206]] ([[User talk:24.20.222.206|talk]] • [[Special:Contributions/24.20.222.206|contribs]])

Talk:HTTP (API)

2012-04-25T19:33:30Z

Riking: unsigned template

"mod_ComputerCraft.cfg is located in .minecraft/config" 
At least for client side it is. Does this file generate server side? (I can get this to work client side, but when playing multiplayer on a server, it's not enabled) — Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:96.236.138.19|96.236.138.19]] ([[User talk:96.236.138.19|talk]] • [[Special:Contributions/96.236.138.19|contribs]]) 
:This must be enabled on the server. You can find the config in mods/ComputerCraft in the Server Folder.— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:77.165.144.76|77.165.144.76]] ([[User talk:77.165.144.76|talk]] • [[Special:Contributions/77.165.144.76|contribs]])

Talk:Making a Password Protected Door

2012-04-25T19:31:46Z

Riking: {{unsigned}} for all comments

== Re: "Make code better, again" ==

How is it 'better' to leave the computer running when it's not needed?
Assuming this is the desired behaviour, why is it 'better' to reboot the computer each time instead of using a loop?
And assuming ''that'' is the desired behaviour, why is it 'better' to have the call to os.reboot() repeated inside the if blocks instead of once after the if?— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:2.102.58.164|2.102.58.164]] ([[User talk:2.102.58.164|talk]] • [[Special:Contributions/2.102.58.164|contribs]]) 

:Loop uses more memory. Also, there's no difference, do you really care that much? — Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:24.20.22.206|24.20.22.206]] ([[User talk:24.20.22.206|talk]] • [[Special:Contributions/24.20.22.206|contribs]]) 
::I reverted changes from two users. This guide is supposed to be a reasonably low level tutorial. Simply slapping code on a page is not a tutorial, hence the previous version with screen shots is more noob friendly. Secondly, the latter version used variables that don't need to be variables. [[Special:Contributions/121.45.75.253|121.45.75.253]] 14:07, 16 April 2012 (UTC)

== I think this can be more "Noob" friendly ==

i am a noob and have just started to use Computer Craft. I was learning how to make a password protected lock and i understood all of it, until it said, " Now to start it, we have the computer call the function after it declares it." This confused me very much and i was hoping someone could clarify or edit the page to be even more "Noob" friendly. — Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:Tpomdreams|Tpomdreams]] ([[User talk:Tpomdreams|talk]] • [[Special:Contributions/Tpomdreams|contribs]]) 

:Try the 'Better / Alternative Code', you might understand that more. — Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:24.20.22.206|24.20.22.206]] ([[User talk:24.20.22.206|talk]] • [[Special:Contributions/24.20.22.206|contribs]])

Talk:Making a Password Protected Door

2012-04-25T19:30:08Z

Riking: clean up talk page, add {{subst:unsigned}}

== Re: "Make code better, again" ==

How is it 'better' to leave the computer running when it's not needed?
Assuming this is the desired behaviour, why is it 'better' to reboot the computer each time instead of using a loop?
And assuming ''that'' is the desired behaviour, why is it 'better' to have the call to os.reboot() repeated inside the if blocks instead of once after the if?
:Loop uses more memory. Also, there's no difference, do you really care that much? — Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:24.20.22.206|24.20.22.206]] ([[User talk:24.20.22.206|talk]] • [[Special:Contributions/24.20.22.206|contribs]]) 
::I reverted changes from two users. This guide is supposed to be a reasonably low level tutorial. Simply slapping code on a page is not a tutorial, hence the previous version with screen shots is more noob friendly. Secondly, the latter version used variables that don't need to be variables. [[Special:Contributions/121.45.75.253|121.45.75.253]] 14:07, 16 April 2012 (UTC)

== I think this can be more "Noob" friendly ==

i am a noob and have just started to use Computer Craft. I was learning how to make a password protected lock and i understood all of it, until it said, " Now to start it, we have the computer call the function after it declares it." This confused me very much and i was hoping someone could clarify or edit the page to be even more "Noob" friendly.
:Try the 'Better / Alternative Code', you might understand that more. — Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:24.20.22.206|24.20.22.206]] ([[User talk:24.20.22.206|talk]] • [[Special:Contributions/24.20.22.206|contribs]])

Template:Unsigned

2012-04-25T19:29:14Z

Riking: fork wikipedia

— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:{{{1}}}|{{{1}}}]] ([[User talk:{{{1}}}|talk]] • [[Special:Contributions/{{{1}}}|contribs]]) {{{2|}}}<noinclude>
{{documentation}} </noinclude>

Talk:Making a Password Protected Door

2012-04-25T19:26:38Z

Riking: Undo revision 1343 by 24.20.222.206 (talk) -- revert deletion

== In response to 24.20.222.206 who reverted my changes and commented "Make code better, again" ==

How is it 'better' to leave the computer running when it's not needed?
Assuming this is the desired behaviour, why is it 'better' to reboot the computer each time instead of using a loop?
And assuming ''that'' is the desired behaviour, why is it 'better' to have the call to os.reboot() repeated inside the if blocks instead of once after the if?
<pre>
24.20.22.206:
Loop uses more memory. Also, there's no difference, do you really care that much?
</pre>
::I reverted changes from two users. This guide is supposed to be a reasonably low level tutorial. Simply slapping code on a page is not a tutorial, hence the previous version with screen shots is more noob friendly. Secondly, the latter version used variables that don't need to be variables. [[Special:Contributions/121.45.75.253|121.45.75.253]] 14:07, 16 April 2012 (UTC)

== I think this can be more "Noob" friendly ==

i am a noob and have just started to use Computer Craft. I was learning how to make a password protected lock and i understood all of it, until it said, " Now to start it, we have the computer call the function after it declares it." This confused me very much and i was hoping someone could clarify or edit the page to be even more "Noob" friendly.

24.20.22.206:
Try the 'Better / Alternative Code', you might understand that more.

OS (API)

2012-04-25T19:09:41Z

Riking: /* Event names */ added wick

''You may be looking for alternative OS's for ComputerCraft. If so, go to the [[list of oses|list of OSes]].''

The Operating System API allows for interfacing with the Lua based Operating System itself.
{| border="1" cellpadding="2" cellspacing="0"
!style="background:#EEE" width="200px"|Method name
!style="background:#EEE" width="*"|Description
|-
|[[os.version()]]
|Returns the version of the OS the computer is running.
|-
|[[os.computerID()]]
|Returns the unique ID of this computer.
|-
|[[os.run( environment, programpath, arguments )]]
|An advanced way of starting programs. A started program will have a given
Environment table which determines what functions it has available, as well as
any variables it will be able to access by default. You may prefer to use the
[[Shell (API)]] unless you need to do something special.
|-
|[[#api|os.loadAPI( name )]]
|Loads a lua script as an API, making it available to all programs.
|-
|[[#api|os.unloadAPI( name )]]
|Unloads a previously loaded API.
|-
|[[#pullEvent|os.pullEvent()]]
|Blocks until the computer has detected an event, then returns the event.
|-
|[[#pullEvent|os.pullEventRaw()]]
|Advanced version of pullEvent().
|-
|[[os.queueEvent()]]
|<no description given>
|-
|[[os.clock()]]
|Returns CPU time.
|-
|[[os.startTimer( timeout )]]
|Queues an event to be triggered after a number of seconds.
The ID of the timer is returned from this function to differentiate multiple
timers. Timers are one-shot, once they have fired an event you will need to
start another one if you need a recurring timer.
|-
|[[os.sleep( timeout )]]
|Makes the system wait a number of seconds before continuing in the program.
May also be used as simply "sleep( timeout )".
|-
|[[os.time()]]
|Returns the current Minecraft world time.
|-
|[[os.setAlarm( time )]]
|Queues an event to be triggered at the specific Minecraft world time.
|-
|[[os.shutdown()]]
|Turns off the computer.
|-
|[[os.reboot()]]
|Reboots the computer.
|}

== <div id="api">API</div> ==

API are programs which are loaded in to the OS itself, and expose functions
which other programs may use. The stock [[Category:APIs|APIs that ship with
ComputerCraft]] are loaded in this way, and may be replaced by a computer's
user or programs.

== <div id="pullEvent">os.pullEvent()</div> ==

os.pullEvent() causes the current program to pause, retrieving the next event
from the computer's queue of events. If there is no event to read, then the
program will stall until such an event becomes available. Note that if a
program has not attempted to pull an event in the past ten seconds, it will
be forcefully terminated to prevent CPU waste in SMP environments.

pullEvent returns the name of the event that was read, as well as up to
five parameters:

<code>
local event, p1, p2, p3, p4, p5 = os.pullEvent()
</code>

os.pullEvent() is usually run inside a 'while true do' loop.

An advanced version of this method <code>os.pullEventRaw</code> bypasses the
normal handling of events from the OS. You may use this to act on the
"Terminate" event (triggered when holding Ctrl-T) for custom termination logic.

=== Event names ===

*[[Raw key events|"key": keypress]]
*"rednet_message": recieved a rednet message
*"terminate" (? please verify name): Ctrl-T held

[[Category:APIs]]

OS (API)

2012-04-25T19:08:53Z

Riking:

''You may be looking for alternative OS's for ComputerCraft. If so, go to the [[list of oses|list of OSes]].''

The Operating System API allows for interfacing with the Lua based Operating System itself.
{| border="1" cellpadding="2" cellspacing="0"
!style="background:#EEE" width="200px"|Method name
!style="background:#EEE" width="*"|Description
|-
|[[os.version()]]
|Returns the version of the OS the computer is running.
|-
|[[os.computerID()]]
|Returns the unique ID of this computer.
|-
|[[os.run( environment, programpath, arguments )]]
|An advanced way of starting programs. A started program will have a given
Environment table which determines what functions it has available, as well as
any variables it will be able to access by default. You may prefer to use the
[[Shell (API)]] unless you need to do something special.
|-
|[[#api|os.loadAPI( name )]]
|Loads a lua script as an API, making it available to all programs.
|-
|[[#api|os.unloadAPI( name )]]
|Unloads a previously loaded API.
|-
|[[#pullEvent|os.pullEvent()]]
|Blocks until the computer has detected an event, then returns the event.
|-
|[[#pullEvent|os.pullEventRaw()]]
|Advanced version of pullEvent().
|-
|[[os.queueEvent()]]
|<no description given>
|-
|[[os.clock()]]
|Returns CPU time.
|-
|[[os.startTimer( timeout )]]
|Queues an event to be triggered after a number of seconds.
The ID of the timer is returned from this function to differentiate multiple
timers. Timers are one-shot, once they have fired an event you will need to
start another one if you need a recurring timer.
|-
|[[os.sleep( timeout )]]
|Makes the system wait a number of seconds before continuing in the program.
May also be used as simply "sleep( timeout )".
|-
|[[os.time()]]
|Returns the current Minecraft world time.
|-
|[[os.setAlarm( time )]]
|Queues an event to be triggered at the specific Minecraft world time.
|-
|[[os.shutdown()]]
|Turns off the computer.
|-
|[[os.reboot()]]
|Reboots the computer.
|}

== <div id="api">API</div> ==

API are programs which are loaded in to the OS itself, and expose functions
which other programs may use. The stock [[Category:APIs|APIs that ship with
ComputerCraft]] are loaded in this way, and may be replaced by a computer's
user or programs.

== <div id="pullEvent">os.pullEvent()</div> ==

os.pullEvent() causes the current program to pause, retrieving the next event
from the computer's queue of events. If there is no event to read, then the
program will stall until such an event becomes available. Note that if a
program has not attempted to pull an event in the past ten seconds, it will
be forcefully terminated to prevent CPU waste in SMP environments.

pullEvent returns the name of the event that was read, as well as up to
five parameters:

<code>
local event, p1, p2, p3, p4, p5 = os.pullEvent()
</code>

os.pullEvent() is usually run inside a 'while true do' loop.

An advanced version of this method <code>os.pullEventRaw</code> bypasses the
normal handling of events from the OS. You may use this to act on the
"Terminate" event (triggered when holding Ctrl-T) for custom termination logic.

=== Event names ===

*"key": keypress
*"rednet_message": recieved a rednet message
*"terminate" (? please verify name): Ctrl-T held

[[Category:APIs]]

Raw key events

2012-04-25T19:06:39Z

Riking: added keymapper api reference

The built-in os has a function to read incoming keystrokes. But it also implements the functions to move the cursor while typing. This is not always a desired feature; imagine a case in which you want to make a menu with a controllable cursor around the menu entries. The current read() function won't let you.

==Detecting keystrokes==
In case I made you think the os sucks, it doesn't (all the time). Because this os is not Windows, we can access lower-level functions, such as os.pullEvent(). And that's the one that we're going to use:
<pre>
function rawread()
bRead = true
while(bRead) do
local sEvent, param = os.pullEvent("key")
if(sEvent == "key") then
break
end
end
end
</pre>
This function waits for any key, then exits.

==Figuring out the key==
We can detect any key, but not which key. To find it out, we have to add some further logic to the code:
<pre>
function rawread()
bRead = true
while(bRead) do
local sEvent, param = os.pullEvent("key")
if(sEvent == "key") then
if(param == 28) then
print("Enter detected")
break
end
end
end
end
</pre>
This function waits for the Enter key to be pressed. If so, it writes "Enter detected" to the screen and exits.

However, this is only good for checking single keys. Also, what if you don't really want to look up the scan code on this page every time you code?
Fortunately there is a solution: the [[Raw key events/keymapper|keymapper API]]. See page for details.

==Key scan codes ==
The scan codes are typical DirectX numbers.
{|
|style="vertical-align: top"|
{| border="1" cellpadding="5" cellspacing="0"
|-
! |Key
! |Code
|-
| Escape
| 1
|-
| 1
| 2
|-
| 2
| 3
|-
| 3
| 4
|-
| 5
| 6
|-
| 7
| 8
|-
| 9
| 10
|-
| 0
| 11
|-
| Minus
| 12
|-
| Equals
| 13
|-
| Backspace
| 14
|-
| Tab
| 15
|-
| Q
| 16
|-
| W
| 17
|-
| E
| 18
|-
| R
| 19
|-
| T
| 20
|-
| Y
| 21
|-
| U
| 22
|-
| I
| 23
|-
| O
| 24
|-
| P
| 25
|}
|style="vertical-align: top"|
{| border="1" cellpadding="5" cellspacing="0"
|-
! |Key
! |Code
|-
| Left Bracket
| 26
|-
| Right Bracket
| 27
|-
| Enter
| 28
|-
| Left Control
| 29
|-
| A
| 30
|-
| S
| 31
|-
| D
| 32
|-
| F
| 33
|-
| G
| 34
|-
| H
| 35
|-
| J
| 36
|-
| K
| 37
|-
| L
| 38
|-
| Semicolon
| 39
|-
| Apostrophe
| 40
|-
| Tilde (~)
| 41
|-
| Left Shift
| 42
|-
| Back Slash
| 43
|-
| Z
| 44
|-
| X
| 45
|-
| C
| 46
|-
| V
| 47
|}
|style="vertical-align: top"|
{| border="1" cellpadding="5" cellspacing="0"
|-
! |Key
! |Code
|-
| B
| 48
|-
| N
| 49
|-
| M
| 50
|-
| Comma
| 51
|-
| Period
| 52
|-
| Forward Slash
| 53
|-
| Right Shift
| 54
|-
| Numpad *
| 55
|-
| Left Alt
| 56
|-
| Spacebar
| 57
|-
| Caps Lock
| 58
|-
| F1
| 59
|-
| F2
| 60
|-
| F3
| 61
|-
| F4
| 62
|-
| F5
| 63
|-
| F6
| 64
|-
| F7
| 65
|-
| F8
| 66
|-
| F9
| 67
|-
| F10
| 68
|}
|style="vertical-align: top"|
{| border="1" cellpadding="5" cellspacing="0"
|-
! |Key
! |Code
|-
| Num Lock
| 69
|-
| Scroll Lock
| 70
|-
| Numpad 7
| 71
|-
| Numpad 8
| 72
|-
| Numpad 9
| 73
|-
| Numpad -
| 74
|-
| Numpad 4
| 75
|-
| Numpad 5
| 76
|-
| Numpad 6
| 77
|-
| Numpad +
| 78
|-
| Numpad 1
| 79
|-
| Numpad 2
| 80
|-
| Numpad 3
| 81
|-
| Numpad 0
| 82
|-
| Numpad .
| 83
|-
| F11
| 87
|-
| F12
| 88
|-
| Numpad Enter
| 156
|-
| Right Control
| 157
|-
| Numpad /
| 181
|-
| Right Alt
| 184
|}
|style="vertical-align: top"|
{| border="1" cellpadding="5" cellspacing="0"
|-
! |Key
! |Code
|-
| Home
| 199
|-
| Up Arrow
| 200
|-
| Page Up
| 201
|-
| Left Arrow
| 203
|-
| Right Arrow
| 205
|-
| End
| 207
|-
| Down Arrow
| 208
|-
| Page Down
| 209
|-
| Insert
| 210
|-
| Delete
| 211
|-
| Left Mouse Button
| 256
|-
| Right Mouse Button
| 257
|-
| Middle Mouse/Wheel
| 258
|-
| Mouse Button 3
| 259
|-
| Mouse Button 4
| 260
|-
| Mouse Button 5
| 261
|-
| Mouse Button 6
| 262
|-
| Mouse Button 7
| 263
|-
| Mouse Wheel Up
| 264
|-
| Mouse Wheel Down
| 265
|}
|}
Source: [http://wiki.tesnexus.com/index.php/DirectX_Scancodes_And_How_To_Use_Them Nexus Wiki]

====Author(s)====
They deserve credit!
*Initial page - [[User:Wukl|Wukl]]

[[Category:Tutorials]]