ComputerCraft Wiki - User contributions [en]

User:Thesbros/Sandbox

2012-12-11T06:30:46Z

Thesbros: Created page with "{{Heading|Mah Sandbox}}"

Crafting Table

2012-12-10T06:36:12Z

Thesbros: Undo revision 4774 by Thesbros (talk) Didn't work?

http://www.minecraftwiki.net/wiki/Crafting_Table

Crafting Table

2012-12-10T06:35:52Z

Thesbros: Undo revision 4775 by Thesbros (talk)

#REDIRECT [[http://www.minecraftwiki.net/wiki/Crafting_Table]]

Crafting Table

2012-12-10T06:35:11Z

Thesbros:

#REDIRECT [http://www.minecraftwiki.net/wiki/Crafting_Table]

Crafting Table

2012-12-10T06:34:56Z

Thesbros: Redirect instead of link

#REDIRECT [[http://www.minecraftwiki.net/wiki/Crafting_Table]]

ComputerCraft

2012-12-09T18:24:20Z

Thesbros:

Crafting Table

2012-12-09T18:21:37Z

Thesbros: Undo revision 4751 by Jonjon1234 (talk) Not useless, the crafting grid uses it.

http://www.minecraftwiki.net/wiki/Crafting_Table

CcSensors

2012-12-09T06:15:57Z

Thesbros:

{{Outdated|reason='''This mod is 1.2.5 ONLY! It is very out-of-date!''' Documentation is ripped from source code. Information is provided "as-is" with no guarantee of accuracy.}}
{{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 guarantee 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
|-
|getProbe( side, sensor )
|returns a table of the available probes (eg: TargetInfo, LivingEntities, Players)
|-
|getSensorInfo( side, sensor, ... )
|returns the following information for a given sensor:
cardType, ActiveReadingID, Distance, Name, ActiveReading, ShortName, SensorRange, yCoord, zCoord, xCoord

|-
|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,probe,...)
|get a reading while setting the target and reading type for a given sensor. returns a dictionary [working]
|-
|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-12-09T06:15:46Z

Thesbros:

{{Outdated|reason='''This mod is 1.2.5 ONLY! It is very out-of-date!'''. Documentation is ripped from source code. Information is provided "as-is" with no guarantee of accuracy.}}
{{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 guarantee 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
|-
|getProbe( side, sensor )
|returns a table of the available probes (eg: TargetInfo, LivingEntities, Players)
|-
|getSensorInfo( side, sensor, ... )
|returns the following information for a given sensor:
cardType, ActiveReadingID, Distance, Name, ActiveReading, ShortName, SensorRange, yCoord, zCoord, xCoord

|-
|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,probe,...)
|get a reading while setting the target and reading type for a given sensor. returns a dictionary [working]
|-
|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-12-09T06:15:22Z

Thesbros: Oops

{{Outdated|reason='''This mod is 1.2.5 ONLY! It is very out-of-date!''' and documentation is ripped from source code. Information is provided "as-is" with no guarantee of accuracy.}}
{{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 guarantee 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
|-
|getProbe( side, sensor )
|returns a table of the available probes (eg: TargetInfo, LivingEntities, Players)
|-
|getSensorInfo( side, sensor, ... )
|returns the following information for a given sensor:
cardType, ActiveReadingID, Distance, Name, ActiveReading, ShortName, SensorRange, yCoord, zCoord, xCoord

|-
|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,probe,...)
|get a reading while setting the target and reading type for a given sensor. returns a dictionary [working]
|-
|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-12-09T06:15:11Z

Thesbros: Convert to Template:Outdated

{{Outdated|reason='''This mod is 1.2.5 ONLY! It is very out-of-date!''' and documentation is ripped from source code. Information is provided "as-is" with no guarantee of accuracy.
{{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 guarantee 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
|-
|getProbe( side, sensor )
|returns a table of the available probes (eg: TargetInfo, LivingEntities, Players)
|-
|getSensorInfo( side, sensor, ... )
|returns the following information for a given sensor:
cardType, ActiveReadingID, Distance, Name, ActiveReading, ShortName, SensorRange, yCoord, zCoord, xCoord

|-
|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,probe,...)
|get a reading while setting the target and reading type for a given sensor. returns a dictionary [working]
|-
|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]]

Paintutils.loadImage

2012-12-07T08:49:03Z

Thesbros:

{{lowercase}}
{{Function
|name=paintutils.loadImage
|args=[[String_(type)|string]] path
|api=paintutils
|returns=[[Boolean_(type)|boolean]] true on success, otherwise false
|addon=ComputerCraft
|desc=Loads an image (images created with the [[Paint|paint]] program)
|examples=
{{Example
|desc=The program loads the image 'bar' onto the variable 'image' and then draws it on the screen starting at position {3, 5}
|code=image = [[paintutils.loadImage("bar")]]
paintutils.drawImage(image, 3, 5)
}}
}}

[[Category:API_Functions]]

Paintutils.loadImage

2012-12-07T08:48:19Z

Thesbros:

{{lowercase}}
{{Function
|name=paintutils.loadImage
|args=[[String_(type)|(string)]] path
|api=paintutils
|returns=true on success, otherwise false
|addon=ComputerCraft
|desc=Loads an image (images created with the [[Paint|paint]] program)
|examples=
{{Example
|desc=The program loads the image 'bar' onto the variable 'image' and then draws it on the screen starting at position {3, 5}
|code=image = [[paintutils.loadImage("bar")]]
paintutils.drawImage(image, 3, 5)
}}
}}

[[Category:API_Functions]]

Paintutils.loadImage

2012-12-07T08:47:49Z

Thesbros:

{{lowercase}}
{{Function
|name=paintutils.loadImage
|args=(path)
|api=paintutils
|returns=true on success, otherwise false
|addon=ComputerCraft
|desc=Loads an image (images created with the [[Paint|paint]] program)
|examples=
{{Example
|desc=The program loads the image 'bar' onto the variable 'image' and then draws it on the screen starting at position {3, 5}
|code=image = [[paintutils.loadImage("bar")]]
paintutils.drawImage(image, 3, 5)
}}
}}

[[Category:API_Functions]]

Raw key events

2012-12-04T14:06:41Z

Thesbros: Undo revision 4613 by 91.230.85.2 (talk)

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()
while true 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.

==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
|-
| 4
| 5
|-
| 5
| 6
|-
| 6
| 7
|-
| 7
| 8
|-
| 8
| 9
|-
| 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
|-
|}
|}
Source: [http://wiki.tesnexus.com/index.php/DirectX_Scancodes_And_How_To_Use_Them Nexus Wiki]

[[Category:Tutorials]]

Category:APIs

2012-12-04T13:53:06Z

Thesbros: Undo revision 4609 by 72.242.229.2 (talk)

[[File:Apis.png|thumb|350px|API's being listed with the "apis" command run in a computer.]]An API (Application Programming Interface) is a collection of code that, rather than being run directly by the user as a program, is meant to be used by other programs. This is different from a function in that an API may contain many functions that perform related tasks; the API groups them together. It is a library of functions.
There are two reasons why one might want to use an API:
* The API may provide a function that you could write yourself if you had to, but using the one from the API means you don't have to do that work.

* The API may provide something it's impossible to do yourself because it has to be done in Java rather than Lua.

ComputerCraft itself ships with a collection of APIs of both types. For example:

* The [[color (API)|color API]] provides names for the various numbers used in RedPower bundled cable, and functions that manipulate those numbers. The names for the numbers are just variables, and the functions are written in Lua (you can find this in "rom/apis/colors"). You could write the same variables and functions in your own code if you wanted, but using the API saves you from doing that.

* The [[fs (API)|fs API]] provides functions to work with files. You couldn't write the functions from this API in Lua because they have to access the corresponding files in your real computer (the one running Minecraft), and the only way to do that from Lua is… through the fs API (or the [[IO (API)|io API]], but that's just a wrapper around fs).

All the stock APIs of the first kind, those that are implemented in Lua, can be found in your "mods/ComputerCraft/lua/rom/apis" directory. Inside Minecraft, on a ComputerCraft computer, these appear in the directory "rom/apis". All the built-in APIs of both kinds (Lua and Java) are automatically loaded, so you don't have to use "[[OS (API)|os]].loadAPI" on them.

ComputerCraft mods, for example mods that add custom peripherals, might also add APIs that help you work with those peripherals.

You can view a list of un-official API's at the [[:Category:Unofficial_APIs]] page.

Finally, you might find APIs written by other people that you can download, or you might write APIs yourself if you'll be using a function in many different programs and don't want to keep rewriting it. If you're playing single-player or you're running the multiplayer server, you can add those APIs to "rom/apis" and they will automatically be loaded on every computer in the world. Normally, though, you would leave the APIs somewhere else and use "os.loadAPI" to make them available to your program.

You can see a list of APIs built-in to ComputerCraft by typing "apis" in the terminal.

[[Category:Lists]]

Turtle.detectUp

2012-12-04T13:52:54Z

Thesbros: Undo revision 4608 by 184.171.168.202 (talk) Who's face?

{{lowercase}}
{{Function
|name=turtle.detectUp
|args=
|api=turtle
|returns=[[boolean_(type)|boolean]] If turtle has Detected a Block Above.
|addon=ComputerCraft
|desc=Detects if there is a Block Above.
|examples=
{{Example
|desc=Detects if there is a Block Above.
|code=turtle.detectUp()
}}
}}

[[Category:Lua_Core_Functions]]

Textutils.tabulate

2012-12-04T13:23:43Z

Thesbros:

{{lowercase}}
{{Function
|name=textutils.tabulate
|args= [[table (type)|table]] table1, [[table (type)|table]] table2, ...
|returns=Text printed on the screen
|api=textutils
|addon=ComputerCraft
|desc=Prints tables in an ordered form. Each table is a row, columns' width is auto-adjusted.
|examples=
{{Example
|desc=Prints two tables in an ordered form.
|code=textutils.tabulate({1,2,3},{"A","B","C"})
|output=Print:
1.0 2.0 3.0

A B C
}}
}}

[[Category:API_Functions]]

Turtle Stairbuilder (tutorial)

2012-12-04T13:13:11Z

Thesbros: Undo revision 4601 by 184.71.12.166 (talk)

==Introduction==
Welcome to this [[:Category:Tutorials|tutorial]] about Turtle Stairbuilders.

==Programming your Stairbuilder==
In this code we will program a stairbuilder that simply goes up a flat surface, when the wall ends it will create a stairway coming off of the wall

First we want it to determine the top of the wall
<code>
while turtle.detect() do
turtle.up()
end
</code>
next we want it to decend one block and create the staircase
<code>
while turtle.detect() do
turtle.up()
end
turtle.down()
turtle.back()
turtle.place()
while not turtle.detectDown() do
turtle.back()
turtle.down()
turtle.place()
end
print("Staircase Built")
</code>
And there's your code!

==Uses==

With a little modification this can be used in ravines to go up or down. It can be very useful in the nether if you're stuck or are fighting off a ghast. This program can also be used creatively in multiplayer RPG games to traverse difficult obstacles.

[[Category:Tutorials]]

ComputerCraft IRC

2012-12-04T12:20:36Z

Thesbros:

{{Stub}}
The ComputerCraft IRC is the official IRC. It's channel is #computercraft. If you are using an IRC client, the IP is: irc.esper.net:5555 A link to the webchat is [http://webchat.esper.net/?channels=#computercraft here.] Most development information is gained from this.

[[Category:Lists]]

Coroutine.create

2012-12-04T12:17:08Z

Thesbros:

{{lowercase}}
{{Function
|name=coroutine.create
|args=[[Function (type)|function]] function
|api=Coroutine
|returns=[[coroutine]] new coroutine
|addon=ComputerCraft
|desc=Creates a new coroutine
|examples=
{{Example
|desc=creates a coroutine.
|code=coroutine.create(function() print("Hello World") end)
}}
}}

[[Category:Lua_Core_Functions]]

Turtle.suck

2012-12-04T12:16:24Z

Thesbros: Undo revision 4588 by 184.171.168.202 (talk)

{{lowercase}}
{{Function
|name=turtle.suck
|args=
|returns=true if at least one item was moved into the turtle's inventory; false otherwise.
|api=turtle
|addon=ComputerCraft
|desc=If an item is in the square directly in front of the turtle, it picks up one of those items.
If a chest is in the square directly in front of the turtle, it picks up the items from the first non-empty slot, moving from top left to bottom right.
The items are moved into the currently selected slot, if there is room.
If the currently selected slot is filled up before all of the items are picked up, the remaining items are put in the next available slot.
If the currently selected slot is 16, it will loop around and try slot 1, and so on.

|examples=
{{Example
|desc=Picks up some items.
|code=turtle.suck()
}}
}}

[[Category:Lua_Core_Functions]]

String (API)

2012-12-04T11:54:52Z

Thesbros: Undo revision 4584 by 189.205.27.4 (talk) Om nom nom spam

The string API is a default Lua 5.1 API as defined [http://www.lua.org/manual/5.1/manual.html#5.4 here]. Please list any non-working functions below.

==Non-Working Functions==

===string.gmatch(string, pattern)===

Using any quantifier other than + will cause it to hang if that quantifier applies to the whole pattern and that pattern does not match the whole string.

Examples:
<pre>
"abcdef":gmatch("%a*") -- Works
"abc=def":gmatch("%a*") -- Hang
"abc=def":gmatch("%a.*") -- Works
"abc=def":gmatch("[%a.]*") -- Hang
"abc=def":gmatch("[^=]*") -- Hang
"abc=def":gmatch("([^=]*)=?") -- Works (Note: This produces the same result as the above pattern should)
"abcdef":gmatch("[^=]*") -- Works
"abc=def":gmatch("[^=]*=") -- Works
</pre>

===string.sub / string.find ===

Both string.sub and string.find work on their own, but calling string.find on a string returned by string.sub will return the index of the character in the original string, not the sub string you are referencing.

Example:
<pre>
local testString = "This is a sample string";
local testSubString = string.sub(testString,5);

local indexOfSample = string.find(testSubString,"sample");
</pre>

indexOfSample is returned 11 instead of the expected 7

Concatenating a blank string onto the end of the string causes new memory to be allocated and works properly again

<pre>
local testString = "This is a sample string";
local testSubString = string.sub(testString,5);

local indexOfSample = string.find(testSubString.."","sample");
</pre>

This is also a problem with using string.find on command line arguments, as this returns the index in the full command path instead of the specific argument.

[[Category:APIs]]

Download

2012-12-04T10:44:09Z

Thesbros: Undo revision 4566 by 86.96.226.15 (talk) Spambot

=== You can download the latest version of ComputerCraft [http://www.minecraftforum.net/topic/892282- here]. ===

==Changelog:==

{{Changelog}}

[[Category:Lists]]

Creating a simple name reading program

2012-12-04T10:41:21Z

Thesbros: Undo revision 4564 by 184.171.168.202 (talk) Dude, you're really messed up. AfterLifeLochie: Ban him?

== The Code ==
This will be a tutorial on making a program that will read a name.
This is the code:
<pre>
print("Enter Your Name: ")
local name = read()
print("Hello "..name..", that's a cool name.")
</pre>
The print is pretty obvious, it puts the text on the screen and makes a new line.
Now the 'local name = read()' sets 'name' as a variable which contains a string (piece of text) which the user typed, in this case it's his/her name.
And the last line will print some text, and the '"..name.."' concatenates (merges) the text before it with the text that the variable 'name' contains.

This is another version for my door:
<pre>
textutils.slowPrint("Enter Your Name: ")
local name = read()
print("Okay "..name..", door's open!")
rs.setOutput("right",true) -- this can be changed, "right" is the side of door / redstone
sleep(5)
os.shutdown()
</pre>

[[Category:Programs]][[Category:Tutorials]]

Coroutine.status

2012-12-04T10:29:25Z

Thesbros: Please stop replacing pages with 'Content missing.'

{{Function
|name=coroutine.status
|api=Coroutine
|returns=[[string]] status
|addon=ComputerCraft
|desc=Returns the status of the coroutine; returns "running", if the coroutine is running; "suspended" if the coroutine was yielded or not running; "normal" if the coroutine is active but not running (that is, it has resumed another coroutine); and "dead" if it finished its function.
|examples=
{{Example
|desc=Writes the status of the running coroutine.
|code=print(coroutine.status(coroutine.running()))
|output=running
}}
}}

[[Category:Lua_Core_Functions]]

Turtle.back

2012-12-04T10:18:09Z

Thesbros: \/

{{lowercase}}
{{Function
|name=turtle.back
|args=
|api=turtle
|returns=[[boolean_(type)|boolean]] whether the turtle succeeded in moving backwards
|addon=ComputerCraft
|desc=Attempts to move the turtle backwards.
|examples=
{{Example
|desc=Moves the turtle backwards
|code=print(turtle.back())
|output=true if the turtle could move backwards, false if there was something in the way
}}
}}

[[Category:Lua_Core_Functions]]

Concatenation

2012-12-04T10:17:59Z

Thesbros: \/

Concatenation is the process, in which you combine one or more strings.

To concatenate a string you use two periods.

{{Example
|desc=Concatenating strings.
|code=print("Hello ".."World".."!")
|output=Hello world!
}}
[[Category:Tutorials]]

Term.getCursorPos

2012-12-04T10:17:44Z

Thesbros: You mean "Destroyed page"?

{{lowercase}}
{{Function
|name=term.getCursorPos
|args=none
|returns=x, y
|api=term
|addon=ComputerCraft
|desc=Returns the location of the cursor on screen.
|examples=
{{Example
|desc=Prints the location of the cursor on screen.
|code=print( term.getCursorPos() )
}}
}}

[[Category:API_Functions]]

Download

2012-12-04T10:16:39Z

Thesbros: Undo revision 4547 by 200.230.182.130 (talk)

=== You can download the latest version of ComputerCraft [http://www.minecraftforum.net/topic/892282- here]. ===

==Changelog:==

{{Changelog}}

[[Category:Lists]]

Computer

2012-12-04T07:36:45Z

Thesbros: No need to be capitalized.

[[File:Computer_w_DiskDrive_w_Monitor.png|frame|428x241px|right|A 2x2 [[Monitor]], connected to a [[Computer]], with a [[Disk Drive]] connected.]]
The Computer (pictured) is the main block of ComputerCraft. From the Computer, you will be able to make programs, turn on and off Redstone, use Rednet and interface with bundled cables from RedPower, play games, and much more. The Computer runs an OS called [[CraftOS]].

[[Category:Blocks]]
[[Category:Consoles]]
== Recipe ==
{{Crafting grid
|A1=stone |B1=stone |C1=stone
|A2=stone |B2=Redstone |C2=stone
|A3=stone |B3=glass_pane |C3=stone
|Output=Computer
}}
== Usage ==
Place the Computer wherever you please, and just right click it to use.

== Keyboard Shortcuts ==
{| border="1" cellpadding="2" cellspacing="0"
!style="background:#EEE" width="200px"|Shortcut
!style="background:#EEE" width="*"|Usage
|-
|{{Keypress|key=CTRL}} + {{Keypress|key=T}}
|Terminates the current program.
|-
|{{Keypress|key=CTRL}} + {{Keypress|key=R}}
|Reboots the console.
|-
|{{Keypress|key=CTRL}} + {{Keypress|key=S}}
|Forcefully shuts down the computer.
|}
NOTE: You have to hold the keyboard shortcuts down for at least 1 second!

== Peripheral Functions ==
'''''computer'' stands for the variable you wrapped the computer to.'''
''Example:'' computer = peripheral.wrap( "top" )

{| class="wikitable"
!style="background:#EEE" width="210px"|Method name
!style="background:#EEE" width="*"|Description
|-
|computer.turnOn()
|Turns on the Computer or Turtle.
|-
|computer.shutdown()
|Shuts off the Computer or Turtle.
|-
|computer.reboot()
|Reboots the Computer or Turtle.
|-
|computer.getID()
|Gets the ID of the Computer or Turtle.
|}

OS (API)

2012-12-04T07:21:41Z

Thesbros: Undo revision 4536 by 92.231.204.8 (talk)

The Operating System API allows for interfacing with the Lua based Operating System itself.

<table style="width: 100%; border: solid 1px black; margin: 2px; border-spacing: 0px;">
<tr><td colspan="2" style="font-weight: bold; font-size: large; padding-bottom: .3em; border-bottom: solid #C9C9C9 1px; background: #D3FFC2; line-height:28px;">
[[File:Grid_disk.png|24px]]  
OS (API)
</td></tr>

<tr><td style="width: 350px; background: #E0E0E0; padding: .4em; font-weight:bold;">Method Name</td><td style="background: #E0E0E0; padding: .4em; font-weight:bold;">Description</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[os.version]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Returns the version of the OS the computer is running.</td></tr>

<tr style="background-color: #E8E8E8;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[os.getComputerID]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Returns the unique ID of this computer. [[os.computerID]]() also behaves exactly the same as [[os.getComputerID]]().</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[os.getComputerLabel]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Returns the label of this computer.</td></tr>

<tr style="background-color: #E8E8E8;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[os.setComputerLabel]]( label )</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Set the label of this computer.</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[os.run]]( environment, programpath, arguments )</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">An advanced way of starting programs. A started program will have a given <var>environment</var> 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.</td></tr>

<tr style="background-color: #E8E8E8;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[#api|os.loadAPI]]( name )</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Loads a Lua script as an API in it's own namespace (see example). It will be available to '''all''' programs that run on the terminal.</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[#api|os.unloadAPI]]( name )</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Unloads a previously loaded API.</td></tr>

<tr style="background-color: #E8E8E8;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[Os.pullEvent|os.pullEvent]]( target-event )</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Blocks until the computer receives an event, or if <var>target-event</var> is specified, will block until an instance of <var>target-event</var> occurs. [[Os.pullEvent|os.pullEvent]]( target-event ) returns the event and any parameters the event may have. If a <var>target-event</var> is specified, the computer will not break for any other events (except termination).</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[#pullEvent|os.pullEventRaw]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Advanced version of pullEvent(). [[#pullEvent|os.pullEventRaw]]() will block until an event occurs, and then returns the event (any any parameters the event may have). Unlike [[Os.pullEvent|os.pullEvent]]( target-event ), this function will not break for system events, and can be used to handle termination events.</td></tr>

<tr style="background-color: #E8E8E8;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[os.queueEvent]]( event, param1, param2, ... )</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Adds an event to the event queue with the name <var>event</var> and the given parameters</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[os.clock]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Returns CPU time.</td></tr>

<tr style="background-color: #E8E8E8;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[os.startTimer]]( timeout )</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Queues an event to be triggered after a number of seconds (<var>timeout</var>). 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.</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[os.sleep]]( timeout )</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Makes the system wait a number of seconds before continuing in the program. [[os.sleep]]( timeout ) may also be used as simply "sleep( timeout )".</td></tr>

<tr style="background-color: #E8E8E8;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[os.time]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Returns the current Minecraft world time.</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[os.setAlarm]]( time )</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Queues an event to be triggered at the specified Minecraft world <var>time</var>.</td></tr>

<tr style="background-color: #E8E8E8;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[os.shutdown]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Turns off the computer.</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[os.reboot]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Reboots the computer.</td></tr>
</table>

[[Category:APIs]]

== API ==

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.

The following is an example of a valid implementation of an API, and, it's usage after being registered:
<code>
-- "apiTest" file
function foo(bar)
print(bar)
end

-- "program" file
os.loadAPI("apiTest")
apiTest.foo("this is a test")
</code>

== <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.

os.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.

User talk:Thesbros

2012-12-02T13:19:28Z

Thesbros:

IRC Bot test

Turtle

2012-11-30T10:46:33Z

Thesbros:

{{NeedsWork|This document is pending revision by [[User:AfterLifeLochie|AfterLifeLochie]]. '''Please do not remove this notice without checking the entire document first.'''}}

'''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 has, 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 so it can later be used for farming.
An example of a use for this would be using it to till, plant, and harvest your wheat farm and dropping product in a chest for you.
For example, if a farm three wheat, then, it will drop a chest and I will get three wheat in the chest

==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 with a crafting table can craft items if they have the correct materials to do so.

==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 its inventory. Turtles can also attack with any tool, where the 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]]

Advanced Computer

2012-11-19T16:50:41Z

Thesbros:

[[File:AdvancedComputerPaint.png|frame|right|An advanced computer running Paint, an exclusive program]]The advanced computer is a [[computer]] that has mouse and colour API support. More exclusive features may be added in another update. They resemble the traditional computer console, but are golden coloured to match their crafting [[recipes|recipe]].
==Recipe==
{{Crafting grid
|A1=Gold_Ingot |B1=Gold_Ingot |C1=Gold_Ingot
|A2=Gold_Ingot |B2=redstone_dust |C2=Gold_Ingot
|A3=Gold_Ingot |B3=glass_pane |C3=Gold_Ingot
|Output=Advanced_Computer
}}
==Exclusive Functions==
* term.setTextColour(colours._color)
* term.setBackgroundColour(colours._color)
* (where _color is the color, like blue.)
NOTE: English from the US uses "colors", while any other English uses "colours".
[[Category:Blocks]]
[[Category:Consoles]]

==Exclusive Programs & APIs==
*[[Paint]]
*[[paintutils]] (API)

Getting Started

2012-11-15T08:59:05Z

Thesbros: Undo revision 3758 by 83.23.227.78 (talk)

== Prerequisite: Installing the mods ==
'''It is very important to read everything carefully before asking questions.'''
'''Also, the latest version of this mod may not be compatible with the current Minecraft release.'''

# Install [http://jenkins.minecraftforge.net/job/forge/forge-recommended/ Minecraft Forge Recommended Build]
# Download the latest version of [http://computercraft.info ComputerCraft]
# Copy OR extract the .zip file into *minecraft folder*\mods\. (Tip: If on Windows, on the main screen of Minecraft, go to 'Texture Packs' and click on 'Open texture pack folder'. Go up one folder, there's your Minecraft folder. If on Mac, open Finder, hit Command+Shift+G and type ~/Library/ then hit enter, open 'Application Support' then open 'minecraft')


== Step 1: Crafting your first console ==
The recipe is simple: 
{{Crafting grid
|A1=stone |B1=stone |C1=stone
|A2=stone |B2=redstone |C2=stone
|A3=stone |B3=glass pane |C3=stone
|Output=console
}}
 

Right click on the console to use it. 
Some important keys to remember:
{| border="1" cellpadding="2" cellspacing="0"
!style="background:#EEE" width="200px"|Shortcut
!style="background:#EEE" width="*"|Usage
|-
|CTRL + T
|Closes the current program.
|-
|CTRL + R
|Reboots the console.
|-
|CTRL + S
|Forcefully shuts down the computer.
|}
NOTE: You have to hold the keyboard shortcuts down for at least 1 second! 
These are forced (CTRL+T can be disabled by a program).

== Step 2: Wiring it all up ==
The console accepts many forms of redstone. For simple structures, such as a password protected door, only a single line of redstone is needed.
However, this mod can do much more. If you need to connect multiple wires to one side, you can just use RedPower's cables.

== Step 3: Programming your system ==
If you've programmed anything before this shouldn't be hard. It'll feel very comfortable.

NOTE: You may also want to make a [[Floppy Disk]] or two to use along with your machine

Type
edit <filename>
in the terminal to open the included feature-rich  text editor. To get the hang of Lua if you're new, use
edit /rom/programs/hello
to view the code of a simple program 'hello'.

Navigating is easy.
> ls
rom
> cd rom
rom> ls
apis help programs
startup
rom> cd programs
rom/programs> cd /
>
To say it in English: ls '''l'''i'''s'''ts the files and folders in a directory, while cd changes the '''c'''urrent '''d'''irectory. '''/''' is the root of the computer.

== Step 4: Test it ==
Make sure that your program is bug-proof before using it as something important. A system controlling the state of an IndustrialCraft² Mark-III Nuclear Reactor to prevent it from overheating shouldn't crash every now and then with "Too long without yielding".

== Step 5: Extend it ==
Give back your part to the community. Help others on the forums or improve the wiki. Or, make your own OS or shell to run on the computers and share it with everybody. You can even create your own peripheral blocks using the API to create even a bigger system. A mainframe, for example.

Advanced Monitor

2012-11-14T13:26:17Z

Thesbros:

The Advanced Monitor is a new, improved version of the [[monitor]]. It has the ability to show coloured text and programs on the screen. It is also golden colored on it's sides, similar to the [[advanced computer]]. For available colors, see [http://computercraft.info/wiki/index.php?title=Colors Colors API].
==Recipe==
{{Crafting grid
|A1=Gold_Ingot |B1=Gold_Ingot |C1=Gold_Ingot
|A2=Gold_Ingot |B2=redstone_dust |C2=Gold_Ingot
|A3=Gold_Ingot |B3=glass_pane |C3=Gold_Ingot
|Output=Advanced_Monitor
}}
==Using an Advanced Monitor==
''See [[Peripheral (API)#Monitor|Peripheral (API)]] for more details.''

To use an Advanced Monitor, you need to call a method using the Peripheral API. This is one example:

peripheral.call("side", "function", var1, var2, ...)

For example:

peripheral.call("top", "write", "Hello World!")

You can also "wrap" the peripheral side to a variable:

local monitor = peripheral.wrap("top")

Now, you can call functions that way.

monitor.write("Hello World!")

There are two new functions (four including the british-spelled color (colour)):

[[term.setTextColor|setTextColor]]([[color (API)|(color)]])

[[term.setBackgroundColor|setBackgroundColor]]([[color (API)|(color)]])

Advanced Monitor

2012-11-14T13:25:21Z

Thesbros:

The Advanced Monitor is a new, improved version of the [[monitor]]. It has the ability to show coloured text and programs on the screen. It is also golden colored on it's sides, similar to the [[advanced computer]]. For available colors, see [http://computercraft.info/wiki/index.php?title=Colors Colors API].
==Recipe==
{{Crafting grid
|A1=Gold_Ingot |B1=Gold_Ingot |C1=Gold_Ingot
|A2=Gold_Ingot |B2=redstone_dust |C2=Gold_Ingot
|A3=Gold_Ingot |B3=glass_pane |C3=Gold_Ingot
|Output=Advanced_Monitor
}}
==Using an Advanced Monitor==
''See [[Peripheral (API)#Monitor|Peripheral (API)]] for more details.''

To use an Advanced Monitor, you need to call a method using the Peripheral API. This is one example:

peripheral.call("side", "function", var1, var2, ...)

For example:

peripheral.call("top", "write", "Hello World!")

You can also "wrap" the peripheral side to a variable:

local monitor = peripheral.wrap("top")

Now, you can call functions that way.

monitor.write("Hello World!")

There are four new functions:

[[term.setTextColor|setTextColor]]([[color (API)|(color)]])

[[term.setTextColour|setTextColour]]([[colour (API)|(colour)]])

[[term.setBackgroundColor|setBackgroundColor]]([[color (API)|(color)]])

[[term.setBackgroundColour|setBackgroundColour]]([[colour (API)|(colour)]])

Main Page

2012-11-05T14:41:53Z

Thesbros: :)

#redirect [[ComputerCraft Wiki - Home]]

Talk:HTTP (API)

2012-11-05T14:28:31Z

Thesbros:

"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]]) 

== HTTP API ==

Is there a way to make it so that this function can be used by a certain rank such as donor, without having to resort to making computercraft donor only?
Do you mean like have it so only a certain rank (like with PermissionsEX?) can use the HTTP API? If so, that's not possible without the ComputerCraft code. (on server-side) --[[User:Thesbros|Thesbros]] 18:27, 5 November 2012 (MSK)

Talk:HTTP (API)

2012-11-05T14:27:44Z

Thesbros:

Talk:HTTP (API)

2012-11-05T14:27:32Z

Thesbros:

"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]]) 

== HTTP API ==

Is there a way to make it so that this function can be used by a certain rank such as donor, without having to resort to making computercraft donor only?
Do you mean like have it so only a certain rank (like with PermissionsEX?) can use the HTTP API? If so, that's not possible without the ComputerCraft code. (on server-side) --[[User:Thesbros|Thesbros]] 18:27, 5 November 2012 (MSK)

Talk:HTTP (API)

2012-11-05T14:27:06Z

Thesbros:

"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]]) 

== HTTP API ==

Is there a way to make it so that this function can be used by a certain rank such as donor, without having to resort to making computercraft donor only?
Do you mean like have it so only a certain rank (like with PermissionsEX?) can use the HTTP API? If so, that's not possible without the ComputerCraft code. (on server-side) --[[User:Thesbros|Thesbros]] 18:27, 5 November 2012 (MSK)

Main Page

2012-11-05T06:43:18Z

Thesbros: Hi there spambot.

#redirect [[ComputerCraft Wiki - Home]]

Peripheral (API)

2012-11-04T12:31:32Z

Thesbros: /* Monitor */

The peripheral API is for interacting with external [http://en.wikipedia.org/wiki/Peripheral peripherals], such as the disk drive and monitor. 
[[Console|Consoles]] and [[Turtle|Turtles]] are also considered peripherals and you can interface two adjacent computers, although in a more limited fashion compared to [[Rednet (API)|rednet]]. Both Computers and Turtles provide the same methods: ''turnOn'', ''shutdown'', ''reboot'', ''getID''.

==Methods==
{| class="wikitable"
!style="background:#EEE" width="210px"|Method name
!style="background:#EEE" width="*"|Description
|-
|[[peripheral.isPresent]]( side )
|Returns '''true''' if a peripheral is present on ''side''.
|-
|[[peripheral.getType]]( side )
|Returns the type or peripheral present on ''side'', nothing returned if ''side'' is empty.
|-
|[[peripheral.getMethods]]( side )
|Returns a table containing all methods for peripheral on ''side''.
|-
|[[peripheral.call]]( side, methodName, param1, param2, ... )
|Sends a function call to peripheral located on ''side''. Return values match those of called method. 
'''Note:''' ''methodName'' is a string.
|-
|[[peripheral.wrap]]( side )
|Returns a handle to the peripheral located on ''side''. If assigned to a variable, it can be used to call all methods available from that peripheral, as if calling '''peripheral.call()''', e.g.: 
m = [[peripheral.wrap]]("left") 
m.someMethod() 
''- is the same as -'' 
[[peripheral.call]]("left","someMethod")
|}

==Events==
{| class="wikitable"
!style="background:#EEE" width="210px"|Event name
!style="background:#EEE" width="*"|Description
!style="background:#EEE" width="*"|Parameters
|-
|peripheral
|Fired when peripheral is attached
|side
|-
|peripheral_detach
|Fired when peripheral is removed
|side
|}
==Monitor==
List of methods:

'''''monitor'' stands for the variable you wrapped the monitor to.'''
''Example:'' monitor = peripheral.wrap( "top" )

{| class="wikitable"
!style="background:#EEE" width="210px"|Method name
!style="background:#EEE" width="*"|Description
|-
|[[term.write|''monitor''.write]]()
|Write to the Monitor's screen.
|-
|[[term.scroll|''monitor''.scroll]]( n )
|Scrolls the monitor screen.
|-
|[[term.setCursorPos|''monitor''.setCursorPos]]( x, y )
|Sets the cursor position on the Monitor.
|-
|[[term.setCursorBlink|''monitor''.setCursorBlink]]( b )
|Enables or disables cursor blinking.
|-
|[[term.getCursorPos|''monitor''.getCursorPos]]()
|Returns two arguments containing the x and the y position of the cursor on the Monitor.
|-
|[[term.getSize|''monitor''.getSize]]()
|Returns two arguments containing the x and the y values stating the size of the Monitor.
|-
|[[term.clear|''monitor''.clear]]()
|Clears the Monitor.
|-
|[[term.clearLine|''monitor''.clearLine]]()
|Clears the line the cursor is on.
|-
|''monitor''.setTextScale( scale )
|Sets the size of the text on the Monitor. Textscale can be between 0.5 and 5.0, with increments of 0.5
|}

==Printer==
List of methods:

'''''printer'' stands for the variable you wrapped the printer to.'''
''Example:'' printer = peripheral.wrap( "right" )

{| class="wikitable"
!style="background:#EEE" width="200px"|Method name
!style="background:#EEE" width="*"|Description
|-
|''printer''.[[printer.newPage|newPage]]()
|Starts a new page. Returns true if page got started, false if not.
|-
|''printer''.[[printer.endPage|endPage]]()
|Ends the page and prints the page to the output tray. Returns true if page was ended, false if not.
|-
|''printer''.[[printer.write|write]]( text )
|Writes text to the paper, works the same way as [[term.write()]]
|-
|''printer''.[[printer.setPageTitle|setPageTitle]]( text )
|Sets the title of the page.
|-
|''printer''.[[printer.getPaperLevel|getPaperLevel]]()
|Returns the amount of paper available in the paper tray.
|-
|''printer''.[[printer.getInkLevel|getInkLevel]]()
|Returns the amount of ink in the ink slot.
|-
|''printer''.[[printer.getCursorPos|getCursorPos]]()
|Returns the coordinates of the cursor on the paper, works the same way as [[term.getCursorPos()]]
|-
|''printer''.[[printer.setCursorPos|setCursorPos]]( x, y )
|Sets the cursor pos.
|-
|''printer''.[[printer.getPageSize|getPageSize]]()
|Returns the size of the paper, works the same way as [[term.getSize()]]
|}

==Computers==
List of methods:

'''''computer'' stands for the variable you wrapped the computer to.'''
''Example:'' computer = peripheral.wrap( "top" )

{| class="wikitable"
!style="background:#EEE" width="210px"|Method name
!style="background:#EEE" width="*"|Description
|-
|''computer''.turnOn()
|Turns on the Computer or Turtle.
|-
|''computer''.shutdown()
|Shuts off the Computer or Turtle.
|-
|''computer''.reboot()
|Reboots the Computer or Turtle.
|-
|''computer''.getID()
|Gets the ID of the Computer or Turtle.
|}
[[Category:APIs]]

Turtle.select

2012-11-04T11:28:13Z

Thesbros: Outdated picture

{{lowercase}}
{{Function
|name=turtle.select
|args=[[int (type)|int]] slotNumber (1-16 in ComputerCraft 1.4+, otherwise 1-6)
|api=turtle
|returns=[[boolean]] whether the slot number specified is greater than nine or not.
|addon=ComputerCraft
|desc=Attempts to select the specified slot.
|examples=
{{Example
|desc=Selects the specified slot
|code=print(turtle.select(5))
|output=true
}}
}}

Turtle.select

2012-11-04T11:27:17Z

Thesbros: >:(

{{lowercase}}
{{Function
|name=turtle.select
|args=[[int (type)|int]] slotNumber
|api=turtle
|returns=[[boolean]] whether the slot number specified is greater than nine or not.
|addon=ComputerCraft
|desc=Attempts to select the specified slot.
|examples=
{{Example
|desc=Selects the specified slot
|code=print(turtle.select(5))
|output=true
}}

A picture reference[http://i.imgur.com/1BNQH.png]
}}

Turtle.back

2012-11-04T11:26:25Z

Thesbros: Damnit spambots

{{lowercase}}
{{Function
|name=turtle.back
|args=
|api=turtle
|returns=[[boolean]] whether the turtle succeeded in moving backwards
|addon=ComputerCraft
|desc=Attempts to move the turtle backwards.
|examples=
{{Example
|desc=Moves the turtle backwards
|code=print(turtle.back())
|output=true if the turtle could move backwards, false if there was something in the way
}}
}}

Stone

2012-11-04T11:25:04Z

Thesbros: Undo revision 3601 by 91.121.27.33 (talk)

For more information, please see the offical Minecraft wiki, [http://www.minecraftwiki.net/wiki/Stone here.]

Turtle.digUp

2012-11-04T11:24:42Z

Thesbros: Undo revision 3599 by 91.121.27.33 (talk)

{{lowercase}}
{{Function
|name=turtle.digUp
|args=
|api=turtle
|returns=[[boolean]] whether the turtle succeeded in digging.
|addon=ComputerCraft
|desc=Attempts to dig the block above of the turtle.
|examples=
{{Example
|desc=Digs the block above the turtle.
|code=print(turtle.digUp())
|output=true if the turtle could dig the block, false if it could not or no block present.
}}
}}