ComputerCraft Wiki - User contributions [en]

User talk:Thesbros

2013-01-20T13:29:43Z

Eric: /* X is not an API */ Derp

IRC Bot test

== Change "ComputerCraft‎; (+22)" (CID:4756) ==

Your change on the page "ComputerCraft" (CID:4756) deleted the redirect "ComputerCraft" to "Main Page". This is a critical redirect, as there are more than fifty pages that link to the ComputerCraft page.

In future, please check using the "What Links Here" tool on the left sidebar before marking pages for deletions, or, deleting redirects - and ultimately, check with an Administrator before completely removing the redirect. Tagging a redirect page with the <nowiki>{{delete}}</nowiki> does not prevent redirection (and helps retain integrity), but alerts us to the need (or not) to delete said page. ''[[User:AfterLifeLochie|AfterLifeLochie]] 00:18, 10 December 2012 (MSK)''

== Crafting Table ==

ThesBros, is there any chance of adding content to the crafting table page? Or just making it redirect to the MC wiki please?
[[User:Jonjon1234|Jonjon1234]] 01:18, 10 December 2012 (MSK)

== X is not an API ==

How do you define API? Something that can be loaded with <code>os.loadAPI</code>? Well, then [[Monitor (API)|<code>monitor</code>]] is not an API, nor is [[Printer (API)|<code>printer</code>]].

To me, it seems reasonable to say that anything returned by <code>peripheral.wrap</code> is a [[Category:Peripheral APIs|Peripheral API]], and by association, an API. Both [[workbench (API)]] and [[modem (API)]] are returned by peripheral.wrap.
[[User:Eric|Eric]] 17:11, 20 January 2013 (MSK)

Mouse drag (event)

2013-01-20T13:25:54Z

Eric: Missing braces

{{NeedsWork|A demonstration on the use and handling of this event would be beneficial. ''[[User:AfterLifeLochie|AfterLifeLochie]] 16:00, 30 November 2012 (MSK)''}}

{{Event
|name=mouse_drag
|desc=Fired when the mouse is dragged (implies that a [[mouse_click_(event)|mouse_click]] event has already occurred).
|return1=The mouse button that was clicked.
|return2=The X-coordinate of the mouse (in screen-characters).
|return3=The Y-coordinate of the mouse (in screen-characters).
|examples=
{{Example
|desc=Print the new co-ordinates of the mouse every time a ''mouse_drag'' event occurs.
|code=
while true do
_, button, xPos, yPos = os.pullEvent("[[mouse_drag_(event)|mouse_drag]]")
[[print]]("mouse_drag => " .. [[tostring]](button) .. ": " ..
"X: " .. [[tostring]](xPos) .. ", " ..
"Y: " .. [[tostring]](yPos))
end
|output=The X and Y position of the mouse during the drag.
}}
{{Example
|desc=Draws a single pixel on the screen, which is moved to the mouse position when mouse is clicked and dragged on the screen
|code=
x = 5
y = 5
while true do
[[term.clear]]()
[[term.setBackgroundColor]]( colors.black )
[[paintutils.drawPixel]]( x, y, colors.red )

event, button, xPos, yPos = os.pullEvent("[[mouse_drag_(event)|mouse_drag]]")

if button == 1 then -- left button was clicked
x = xPos
y = yPos
end
end
|output=
}}
}}

User talk:Thesbros

2013-01-20T13:11:36Z

Eric: /* X is not an API */

IRC Bot test

== Change "ComputerCraft‎; (+22)" (CID:4756) ==

Your change on the page "ComputerCraft" (CID:4756) deleted the redirect "ComputerCraft" to "Main Page". This is a critical redirect, as there are more than fifty pages that link to the ComputerCraft page.

In future, please check using the "What Links Here" tool on the left sidebar before marking pages for deletions, or, deleting redirects - and ultimately, check with an Administrator before completely removing the redirect. Tagging a redirect page with the <nowiki>{{delete}}</nowiki> does not prevent redirection (and helps retain integrity), but alerts us to the need (or not) to delete said page. ''[[User:AfterLifeLochie|AfterLifeLochie]] 00:18, 10 December 2012 (MSK)''

== Crafting Table ==

ThesBros, is there any chance of adding content to the crafting table page? Or just making it redirect to the MC wiki please?
[[User:Jonjon1234|Jonjon1234]] 01:18, 10 December 2012 (MSK)

== X is not an API ==

How do you define API? Something that can be loaded with <code>os.loadAPI</code>? Well, then [[Monitor (API)|<code>monitor</code>]] is not an API, nor is [[Printer (API)|<code>monitor</code>]].

To me, it seems reasonable to say that anything returned by <code>peripheral.wrap</code> is a [[Category:Peripheral APIs|Peripheral API]], and by association, an API. Both [[workbench (API)]] and [[modem (API)]] are returned by peripheral.wrap.
[[User:Eric|Eric]] 17:11, 20 January 2013 (MSK)

User talk:Thesbros

2013-01-20T13:10:43Z

Eric: /* X is not an API */ new section

IRC Bot test

== Change "ComputerCraft‎; (+22)" (CID:4756) ==

Your change on the page "ComputerCraft" (CID:4756) deleted the redirect "ComputerCraft" to "Main Page". This is a critical redirect, as there are more than fifty pages that link to the ComputerCraft page.

In future, please check using the "What Links Here" tool on the left sidebar before marking pages for deletions, or, deleting redirects - and ultimately, check with an Administrator before completely removing the redirect. Tagging a redirect page with the <nowiki>{{delete}}</nowiki> does not prevent redirection (and helps retain integrity), but alerts us to the need (or not) to delete said page. ''[[User:AfterLifeLochie|AfterLifeLochie]] 00:18, 10 December 2012 (MSK)''

== Crafting Table ==

ThesBros, is there any chance of adding content to the crafting table page? Or just making it redirect to the MC wiki please?
[[User:Jonjon1234|Jonjon1234]] 01:18, 10 December 2012 (MSK)

== X is not an API ==

I've reverted your changes for now so that my content doesn't get deleted yet.

How do you define API? Something that can be loaded with <code>os.loadAPI</code>? Well, then [[Monitor (API)|<code>monitor</code>]] is not an API, nor is [[Printer (API)|<code>monitor</code>]].

To me, it seems reasonable to say that anything returned by <code>peripheral.wrap</code> is a [[Category:Peripheral APIs|Peripheral API]], and by association, an API.
[[User:Eric|Eric]]

Turtle

2013-01-20T10:37:27Z

Eric: /* Recipes */ Prettier table

'''Turtles''' are essentially robots, and were added in the 1.3 update. They run an OS, like the [[Computer|Computers]], 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 expanded the turtle's ability to use tools. Turtles are capable of using pickaxes, hoes, axes, shovels and swords. The update added "Crafty Turtles", which have the ability to craft using their inventory - and part of this upgrade saw the number of inventory slots in the Turtle raised to 16 - over the previous 9 slot inventory. The 1.4 update also included a new fuel system for the turtles.

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 [[Disk Drive]]. As such, they need a [[Disk Drive]] placed beside them to access [[Floppy Disk|Floppy Disks]]. However, if the Turtle is of the Wireless family, the [[Disk Drive]] (and other peripherals) must be placed on a side other than the side the [[Modem|wireless modem]] is on.

==Power source==
Turtles require fuel to operate - this means Turtles must be powered from 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, and as such, they do not need to be re-charged, or receive 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 <var>turtleNeedsFuel</var> to <var>0</var>.

==Farming==
Turtles equipped with a [[diamond 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 any product in a chest for you.

==Mining==
Turtles crafted with a [[diamond pickaxe]], [[diamond axe]], or [[diamond shovel]], can break blocks, chop wood, mine stone and ores, 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, the Turtle receives the item directly into it's inventory. Different tools yield different drops - for example, an axe can break anything, but it won't drop ores.

==Crafting==
Turtles with a [http://www.minecraftwiki.net/wiki/Crafting_Table Crafting Table] can craft items if they have the correct materials to do so, and all other slots outside the crafting-zone are empty.

==Melee==
Turtles equipped with a [[diamond 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 [[diamond axe]] is the second best after the [[diamond sword]].

==Recipes==

{|
|+'''Crafting ingredients'''
|-
|Turtle
|{{Crafting grid
|A1=iron_ingot |B1=iron_ingot |C1=iron_ingot
|A2=iron_ingot |B2=Computer |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, however the crafting table can act as a tool, or peripheral.
<br>The following tools can be equipped to a turtles: [[diamond pickaxe]], [[diamond axe]], [[diamond shovel]], [[diamond hoe]] and [[diamond sword]]
<br>The following peripherals can be equipped to a turtles: [[modem|wireless modem]] and [[Workbench|crafting tables]].
<br>Diamond tools must be unused (i.e. not have a durability bar showing) to combine with a turtle.
<br><br>'''Turtle recipe and examples for equipping a turtle with tools and peripherals.'''
{| class="wikitable"
! !! None !! Crafty !! Wireless
|-
! scope="row"| 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
}}
|-
! scope="row"| 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
}}
|-
! scope="row"| 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
}}
|-
! scope="row"| 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
}}
|-
! scope="row"| 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
}}
|-
! scope="row"| 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
}}
|-
! scope="row"| Crafty
|See Above
|N/A
|{{Crafting grid
|A2=Modem |B2=turtle |C2=workbench
|Output=Wireless_Crafty_Turtle
}}
|}
[[Category:Blocks]]

Category:Peripheral APIs

2013-01-20T10:29:25Z

Eric:

APIs obtained by invoking <code>peripheral.wrap(side)</code>

[[Category: APIs]]

Computer (API)

2013-01-20T10:22:19Z

Eric: Created page with "'''''computer'' stands for the variable you wrapped the computer to.''' ''Example:'' computer = peripheral.wrap( "top" ) {| class="wikitable" !Method name !Description |- |co..."

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

{| class="wikitable"
!Method name
!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: Peripheral APIs]]

Advanced Computer

2013-01-20T10:21:57Z

Eric: /* Peripheral Functions */

{{Block
|name=Advanced Computer
|image=Iso_Advanced_Computer.png
|id=4095
|damage-value=The ID of the Computer.
|is-peripheral=Yes
}}
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 |C2=Gold_Ingot
|A3=Gold_Ingot |B3=glass_pane |C3=Gold_Ingot
|Output=Advanced_Computer
}}

==Exclusive Functions==
[[File:AdvancedComputerPaint.png|frame|right|An advanced computer running Paint, an exclusive program]]
[[Advanced Computer|Advanced Computers]] and [[Advanced Monitor|Advanced Monitors]] both have access to color-setting functions in the [[Term (API)]]. In contrast, the standard [[Computer|Computers]] and [[Monitor|Monitors]] do not have access to color-setting functions.

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

== See also ==
[[Computer (API)]]

[[Category:Blocks]][[Category:Consoles]]

Printer (API)

2013-01-20T10:15:55Z

Eric:

The Printer API allows you to interact with printers.

<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]]  
Printer (API)
</td></tr>
<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.getPaperLevel]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Returns the amount of paper available in the paper tray.</td></tr>

<tr style="background-color: #E8E8E8;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.newPage]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Starts a new page. Returns true if page got started, false if not.</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.endPage]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Ends the page and prints the page to the output tray. Returns true if page was ended, false if not.</td></tr>

<tr style="background-color: #E8E8E8;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.write]]([[string]] text)</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Writes text to the paper, works the same way as [[term.write|term.write()]]</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.setPageTitle]]([[string]] title)</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Sets the title of the page.</td></tr>

<tr style="background-color: #E8E8E8;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.getInkLevel]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Returns the amount of ink in the ink slot.</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.getCursorPos]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Returns the coordinates of the cursor on the paper, works the same way as [[term.getCursorPos|term.getCursorPos()]]</td></tr>

<tr style="background-color: #E8E8E8;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.setCursorPos]]([[int (type)|int]] x, [[int (type)|int]] y)</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Sets the cursor pos, works the same way as [[term.setCursorPos|term.setCursorPos()]]</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.getPageSize]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Returns the size of the paper, works the same way as [[term.getSize|term.getSize()]]</td></tr>
</table>

==Note==
All printer functions are to be used ''after'' wrapping the printer in a peripheral.
'''example''': printer = peripheral.wrap("left")

[[Category:Peripheral APIs]]

Printer (API)

2013-01-20T10:12:07Z

Eric:

The Printer API allows you to interact with printers.

<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]]  
Printer (API))
</td></tr>
<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.getPaperLevel]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Returns the amount of paper available in the paper tray.</td></tr>

<tr style="background-color: #E8E8E8;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.newPage]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Starts a new page. Returns true if page got started, false if not.</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.endPage]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Ends the page and prints the page to the output tray. Returns true if page was ended, false if not.</td></tr>

<tr style="background-color: #E8E8E8;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.write]]([[string]] text)</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Writes text to the paper, works the same way as [[term.write|term.write()]]</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.setPageTitle]]([[string]] title)</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Sets the title of the page.</td></tr>

<tr style="background-color: #E8E8E8;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.getInkLevel]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Returns the amount of ink in the ink slot.</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.getCursorPos]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Returns the coordinates of the cursor on the paper, works the same way as [[term.getCursorPos|term.getCursorPos()]]</td></tr>

<tr style="background-color: #E8E8E8;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.setCursorPos]]([[int (type)|int]] x, [[int (type)|int]] y)</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Sets the cursor pos, works the same way as [[term.setCursorPos|term.setCursorPos()]]</td></tr>

<tr style="background-color: #FFFFFF;"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">[[printer.getPageSize]]()</td>
<td style="border-top: solid #C9C9C9 1px; padding: .4em;">Returns the size of the paper, works the same way as [[term.getSize|term.getSize()]]</td></tr>
</table>

==Note==
All printer functions are to be used ''after'' wrapping the printer in a peripheral.
'''example''': printer = peripheral.wrap("left")

[[Category:Peripheral APIs]]

Printer

2013-01-20T10:11:47Z

Eric: /* Peripheral Functions */

{{Block
|name=Printer
|image=Iso_Printer.png
|id=4094
|damage-value=Un-used.
|is-peripheral=Yes
}}
The printer was added in the [[ComputerCraft]] 1.42 update. The printer is placed next to a computer, and allows for printing text onto paper with any color of ink.

== Recipe ==
{{Crafting grid
|A1=stone |B1=stone |C1=stone
|A2=stone |B2=Redstone |C2=stone
|A3=stone |B3=Ink_Sac |C3=stone
|Output=printer
}}
== Usage ==
To use a printer, place it adjacently but not diagonally next to a computer (left, right, top, bottom, front, or back side). Place any color ink in the single left slot, and paper in any of the top slots.

If you are using blocks to pull/insert items from the printer the different slots are available from these sides:
Paper tray is accessible from the top, output paper tray is accessible from the front or bottom, and the ink slot is accessible from the back or sides.

[[File:PrinterGUI.png|thumb|256px|GUI of the Printer]]

== See also ==
[[Printer (API)]]

[[Category:Blocks]][[Category:Peripherals]]

Category:Peripheral APIs

2013-01-20T10:10:37Z

Eric: Created page with "Category: APIs"

[[Category: APIs]]

Monitor

2013-01-20T10:05:59Z

Eric: /* Peripheral Functions */

{{Block
|name=Monitor
|image=Iso_Monitor.png
|id=4094
|damage-value=0
|is-peripheral=Yes
}}
The '''Monitor''' is a block that can display text on its front side. When several screen blocks are placed on the same plane, it will form a single monitor. It is useful for displaying information at a server spawn, showing a program on the monitor, and even showing the status of an IC2 reactor! (provided you have [[CcSensors]] installed)

==Recipe==
{{Crafting grid
|A1=stone |B1=stone |C1=stone
|A2=stone |B2=glass_pane |C2=stone
|A3=stone |B3=stone |C3=stone
|Output=Monitor
}}
[[Category:Blocks]]

==Using the Monitor==
[[File:Computer_w_DiskDrive_w_Monitor.png|frame|428x241px|right|A 2x2 [[Monitor]], connected to a [[Computer]], with a [[Disk Drive]] connected.]]
The command used to control a monitor: monitor [top, bottom, left, right, front or back] [the name of the command to display]

So, in this case, if you typed "hello" in the name of the program part, the monitor would display "Hello World!".

==Using the Monitor within the Lua interface==
The monitor can be summoned through a command or through coding with the Lua command.

The command used to control a monitor within the Lua interface: shell.run("monitor" "[top, bottom, left, right, front or back]" "[the name of the command to display]")

For example, here is a way of summoning the monitor through a command:

<tt>[[print]]("Hello Monitor!")

[[Shell (API)|shell]].[[Shell.run|run]]("monitor", "right", "hello")</tt>

== See also ==
[[Monitor (API)]]

[[Category:Blocks]][[Category:Peripherals]]

Advanced Monitor

2013-01-20T10:05:00Z

Eric: /* Peripheral Functions */

{{Block
|name=Advanced Monitor
|image=Iso_Advanced_Monitor.png
|id=4094
|damage-value=Un-used (clarify?)
|is-peripheral=Yes
}}
The Advanced Monitor is a new, improved version of the [[Monitor]].

In contrast with the standard [[Monitor]], the Advanced Monitor has the ability to show colored text and programs on the screen, and the Advanced Monitor is golden (like the [[Advanced Computer]]), rather than the default stone grey color of the standard [[Monitor]].

For a list of the available colors on both [[Advanced Computer|Advanced Computers]] and the [[Advanced Monitor|Advanced Monitors]], see [[Colors_(API)#Colors|Colors API]].

==Recipe==
{{Crafting grid
|A1=Gold_Ingot |B1=Gold_Ingot |C1=Gold_Ingot
|A2=Gold_Ingot |B2=glass_pane |C2=Gold_Ingot
|A3=Gold_Ingot |B3=Gold_Ingot |C3=Gold_Ingot
|Output=Advanced_Monitor |OA=4
}}

==Using an Advanced Monitor==
The Advanced Monitor behaves exactly the same as the standard [[Monitor]] - except the Advanced Monitor is able to render text with a foreground and background [[Colors (API)#color|color]].

The Advanced Monitor introduces two new methods: ''[[term.setTextColor|monitor.setTextColor]]([[colors (API)#colors|color]])'' and ''[[term.setBackgroundColor|monitor.setBackgroundColor]]([[colors (API)#colors|color]])''. These functions allow you to draw text with a specific foreground and background color. Please note that both spellings of the word color are accepted.

To use an Advanced Monitor, you need to either call a method, or wrap the monitor using the Peripheral API. For this example, we have an Advanced Monitor connected to the top of our [[Computer]]:

-- Immediately invoke a method without wrapping
peripheral.call("top", "write", "Hello World!")

-- You can also "wrap" the peripheral side to a variable:
local monitor = peripheral.wrap("top")
monitor.write("Hello World!")

== See also ==
[[Monitor (API)]]

[[Category:Blocks]][[Category:Peripherals]]

Monitor.setTextScale

2013-01-20T10:03:11Z

Eric:

{{lowercase}}
{{Function
|name=monitor.setTextScale
|args=[[int (type)|int]] scale
|api=monitor
|addon=ComputerCraft
|desc=Sets the size of all text on the monitor.
|examples=
{{Example
|desc=Sets the monitor's text scale to 2.
|code=monitor.setTextScale(2)
|output=none
}}
}}

[[Category:API_Functions]]

Turtle (API)

2013-01-20T08:59:19Z

Eric: Format cleanup

The Turtle API is used to work with your [[Turtle|Turtles]].

===Key===
{| class="wikitable"
! Color !! Turtles that can perform this
|-
| White ||All
|-{{row-lightgreen}}
|Green || Crafty
|-{{row-lightyellow}}
| Yellow || Mining, Felling, Digging, Farming
|-{{row-lightred}}
| Red || Any tool
|}


===API===
{| class="wikitable"
! width="100px" | Return
! width="200px" | Method name
! Description
! Min version
|-{{row-lightgreen}}
|{{type|bool}} success
|[[turtle.craft]]( quantity )
|Craft items using ingredients anywhere in the Turtle's inventory and place results in the active slot. If a quantity is specified, it will craft only up to that many items, otherwise, it will craft as many of the items as possible.
|
|-
|{{type|bool}} success
|[[turtle.forward]]()
|Let the Turtle move forward
|
|-
|{{type|bool}} success
|[[turtle.back]]()
|Let the Turtle move back
|
|-
|{{type|bool}} success
|[[turtle.up]]()
|Let the Turtle move up
|
|-
|{{type|bool}} success
|[[turtle.down]]()
|Let the Turtle move down
|
|-
| true
|[[turtle.turnLeft]]()
|The Turtle turns left
|
|-
| true
|[[turtle.turnRight]]()
|The Turtle turns right
|
|-
|{{type|bool}} success
|[[turtle.select]](slotNum)
|The Turtle selects the given Slot (1 is top left, 16 (9 in 1.33 and earlier) is bottom right)
|
|-
|{{type|int}} result
|[[turtle.getItemCount]](slotNum)
|Counts how many items are in the given Slot
|
|-
|{{type|int}} result
|[[turtle.getItemSpace]](slotNum)
|Counts how many remaining items you need to fill the stack in the given Slot
|
|-{{row-lightred}}
|{{type|bool}} success
|[[turtle.attack]]()
|Attacks in front of the turtle.
| 1.4
|-{{row-lightred}}
|{{type|bool}} success
|[[turtle.attackUp]]()
|Attacks over the turtle.
| 1.4
|-{{row-lightred}}
|{{type|bool}} success
|[[turtle.attackDown]]()
|Attacks under the turtle.
| 1.4
|-{{row-lightyellow}}
|{{type|bool}} success
|[[turtle.dig]]()
|Breaks the Block in front. With hoe: tills the dirt in front of it.
|
|-{{row-lightyellow}}
|{{type|bool}} success
|[[turtle.digUp]]()
|Breaks the Block above. With hoe: tills the dirt above it.
|
|-{{row-lightyellow}}
|{{type|bool}} success
|[[turtle.digDown]]()
|Breaks the Block below. With hoe: tills the dirt below it.
|
|-
|{{type|bool}} success
|[[turtle.place]](signText)
|Places a Block of the selected slot in front. Engrave signText on signs if provided.
| 1.4
|-
|{{type|bool}} success
|[[turtle.placeUp]]()
|Places a Block of the selected slot above
|
|-
|{{type|bool}} success
|[[turtle.placeDown]]()
|Places a Block of the selected slot below
|
|-
|{{type|bool}} result
|[[turtle.detect]]()
|Detects if there is a Block in front. Does not detect mobs.
|
|-
|{{type|bool}} result
|[[turtle.detectUp]]()
|Detects if there is a Block above
|
|-
|{{type|bool}} result
|[[turtle.detectDown]]()
|Detects if there is a Block below
|
|-
|{{type|bool}} result
|[[turtle.compare]]()
|Detects if the block in front is the same as the one in the currently selected slot
|
|-
|{{type|bool}} result
|[[turtle.compareUp]]()
|Detects if the block above is the same as the one in the currently selected slot
|
|-
|{{type|bool}} result
|[[turtle.compareDown]]()
|Detects if the block below is the same as the one in the currently selected slot
|
|-
|{{type|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
|-
|{{type|bool}} success
|[[turtle.drop]](count)
|Drops all items in the selected slot, or if count is specified, drops that many items.<br />[>= 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.
|
|-
|{{type|bool}} success
|[[turtle.drop|turtle.dropUp]](count)
|Drops all items in the selected slot, or if count is specified, drops that many items.<br />[>= 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.
|
|-
|{{type|bool}} success
|[[turtle.drop|turtle.dropDown]](count)
|Drops all items in the selected slot, or if count is specified, drops that many items.<br />[>= 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.
|
|-
|{{type|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
|-
|{{type|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
|-
|{{type|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
|-
|{{type|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.<br />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
|-
|{{type|int}} fuel
|[[turtle.getFuelLevel]]()
|Returns the current fuel level of the turtle, this is the number of blocks the turtle can move.<br />If turtleNeedFuel = 0 then it yields "unlimited".
| 1.4
|-
|{{type|bool}} success
|[[turtle.transferTo]](slot, quantity)
|Transfers items from the selected slot to the specified slot in the [quantity] inputted.
| 1.45
|}

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

Term (API)

2013-01-20T08:45:58Z

Eric: Changed table style to come from template

The Terminal API provides functions for writing text to the terminal and monitors, and drawing ASCII graphics.

Methods in ''italics'' are available only to [[Advanced Computer|Advanced Computers]] and [[Advanced Monitor|Advanced Monitors]].

{{API table|Term|image=Grid disk.png|2=

{{API table/row|[[term.write]](text)
|Writes text to the screen.|odd}}

{{API table/row|[[term.clear]]()
|Clears the entire screen}}

{{API table/row|[[term.clearLine]]()
|Clears the line the cursor is on|odd}}

{{API table/row|[[term.getCursorPos]]()
|Returns two arguments containing the x and the y position of the cursor.}}

{{API table/row|[[term.setCursorPos]](x, y)
|Sets the cursor's position.|odd}}

{{API table/row|[[term.setCursorBlink]](bool)
|Disables the blinking or turns it on.}}

{{API table/row|[[term.isColor]]()
|Returns if the computer supports color. (Used to determine whether or not an [[Advanced Computer]] is being used)|odd}}

{{API table/row|[[term.getSize]]()
|Returns two arguments containing the x and the y values stating the size of the screen. (Good for if you're making something to be compatible with both [[Turtle]]s and [[Computer]]s.)}}

{{API table/row|[[term.scroll]](n)
|Scrolls the terminal ''n'' lines.|odd}}

{{API table/row|[[term.redirect]](target)
|Redirects terminal output to a monitor or other redirect target. (Use [[peripheral.wrap]] to acquire a monitor "object".)}}

{{API table/row|[[term.restore]]()
|Restores terminal output to the previous target.|odd}}

{{API table/row|''[[term.setTextColor]]([[Colors (API)|color]])''
|Sets the text-color of the terminal. Available only to [[Advanced Computer|Advanced Computers]] and [[Advanced Monitor]]s.}}

{{API table/row|''[[term.setBackgroundColor]]([[Colors (API)#Colors|color]])''
|Sets the background color of the terminal. Available only to [[Advanced Computer|Advanced Computers]] and [[Advanced Monitor]]s.|odd}}
}}

[[Category:APIs]]

Template:API table/row

2013-01-20T08:41:44Z

Eric: Created page with "<tr style="background-color: {{#ifeq:{{{3|}}}|odd|#FFFFFF|#E8E8E8}};"><td style="border-top: solid #C9C9C9 1px; padding: .4em;">{{{1}}}</td> <td style="border-top: solid #C9C9..."

Template:API table

2013-01-20T08:39:32Z

Eric:

<table style="width: 100%; border: solid 1px black; margin: 2px; border-spacing: 0px;">
<tr><th colspan="2" style="font-weight: bold; font-size: large; padding-bottom: .3em; border-bottom: solid #C9C9C9 1px; background: #D3FFC2; line-height:28px; text-align: left">
[[File:{{{image}}}|24px]]  {{{1}}} (API)</th></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>
{{{2}}}
</table>

Template:API table

2013-01-20T08:38:40Z

Eric:

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

Template:API table

2013-01-20T08:37:19Z

Eric: WIP

Os.pullEvent

2013-01-20T08:31:44Z

Eric: Indicate argument is optional

{{lowercase}}
{{Function
|name=os.pullEvent
|args=[{{type|string}} filter]
|api=OS
|returns={{type|string}} event, variable parameters(see table below)
|addon=ComputerCraft
|desc=Waits (yields) until an event occurs
|examples=
{{Example
|desc=The program requires to wait for a keypress to do something:
|code=[[Function (type)|function]] clear()
[[term.clear]]()
[[term.setCursorPos]] (1,1)
end
while true do
clear()
[[print]] ("Press E to do something.")
local event, param1 = os.pullEvent ("char") -- limit os.pullEvent to the char event
if param1 == "e" then -- if the returned value was 'e'
clear()
[[write]] ("Name: ")
local name = [[read]]()
[[print]] (name)
break
else
clear()
[[print]] ("Wrong button!")
[[os.sleep|sleep]] (1.5) -- I don't like a whole 2 seconds but 1 second is too short
end
end
}}
}}

=== Common syntax ===

event, param1, param2, param3 = os.pullEvent()

Note: This is one of the most commonly used functions that can return multiple values.
It works like any other function call (such as "input = read()") except that you can get more than one piece of information back.

== How it works ==
When os.pullEvent() is called, the computer waits until an event occurs.
Events can be triggered by several different things, such as a key being pressed or a redstone input changing.
They are usually triggered by ComputerCraft itself, when it needs to notify the computer that something happened.
They can also be triggered by peripherals, or by your program calling [[os.queueEvent]].

More complicated input, such as "the user typing a line of text," does ''not'' correspond to an event.
[[read]] handles this inside itself by waiting for the user to press a key, then updating the screen, moving the cursor, etc.

Events have a type (which is a string) and 0-5 parameters (which are often but not always strings).
No built-in events use more than 3 parameters.

When an event occurs, the event type, followed by the parameters, will be returned. If you have:

event, button, x, y = os.pullEvent()

and the user clicks the mouse at coordinates 5,4 then:
* event will be set to "mouse_click" (the event type)
* button will be set to 0 (the first parameter)
* x will be set to 5 (the second parameter)
* y will be set to 4 (the third parameter)

Note that in this example, we didn't specify a filter. If you specify a filter, then all events of different types will be ignored.
If the user inserts a disk, instead of clicking the mouse, then event will be "disk", button will be the side the disk drive is on, and x and y will be nil.

If we wanted to only wait for mouse clicks we could use:

event, button, x, y = os.pullEvent("mouse_click")

which will ignore any events that are not mouse clicks.

If you assign more variables than necessary, the extra ones will be set to nil.
If you assign fewer variables than necessary, the extra parameters will be discarded.

==Event types==
{| class="wikitable" width="100%"
! rowspan="2" | Name
! rowspan="2" | Description
! colspan="3" | Parameters
|-
! 1 !! 2 !! 3
|-
! scope="row" | [[char (event)|char]]
|Fired when text is typed on the keyboard
| {{type|string}} the letter typed
|
|
|-
! scope="row" | [[key (event)|key]]
|Fired when a key is pressed on the keyboard
|{{type|number}} numerical keycode
|
|
|-
! scope="row" | [[timer (event)|timer]]
|Fired when a timeout started by [[os.startTimer]]() completes
|{{type|number}} Value of the timer as returned by os.startTimer()
|
|
|-
! scope="row" | [[alarm (event)|alarm]]
|Fired when a time passed to [[os.setAlarm]]() is reached
|{{type|number}} Value of the alarm as returned by os.setAlarm()
|
|
|-
! scope="row" | [[redstone (event)|redstone]]
|Fired when the state of any of the redstone inputs change
|
|
|
|-
! scope="row" | [[terminate (event)|terminate]]
|Fired when a combination of keys CTRL and T is pressed and held for three seconds.
You will not normally see this event, as it is handled inside os.pullEvent.
|
|
|
|-
! scope="row" | [[disk (event)|disk]]
|Fired when a disk is inserted into an adjacent disk drive
|{{type|string}} side
|
|
|-
! scope="row" | [[disk_eject (event)|disk_eject]]
|Fired when a disk is removed from an adjacent disk drive
|{{type|string}} side
|
|
|-
! scope="row" | [[peripheral (event)|peripheral]]
|Fired when peripheral is attached
|{{type|string}} side
|
|
|-
! scope="row" | [[peripheral_detach (event)| peripheral_detach]]
|Fired when peripheral is removed
|{{type|string}} side
|
|
|-
! scope="row" | [[rednet_message (event)|rednet_message]]
|Fired when a rednet message is received from the [[Rednet_(API)|rednet API]]
|{{type|number}} senderID
|{{type|string}} message
|{{type|number}} distance travelled
|-
! scope="row" | [[http_success (event)|http_success]]
|Fired when an attempt to receive text from / post text on a website is successful.
You will not normally see this event as it is handled inside http.get.
|{{type|string}} url of the site
|{{type|table}} text on the site
|
|-
! scope="row" | [[http_failure (event)|http_failure]]
|Fired when an attempt to receive text from / post text on a website is unsuccessful
You will not normally see this event as it is handled inside http.get.
|{{type|string}} url of the site
|
|
|-
! scope="row" | [[mouse_click (event)|mouse_click]]
|Fired when a mouse button is pressed
|{{type|number}} mouse button
|{{type|number}} x coordinate
|{{type|number}} y coordinate
|-
! scope="row" | [[mouse_scroll (event)|mouse_scroll]]
|Fired when a mousewheel is scrolled.
|{{type|number}} scroll direction (-1 for up, 1 for down)
|{{type|number}} x coordinate(in screen chars)
|{{type|number}} y coordinate(in screen chars)
|-
! scope="row" | [[mouse_drag (event)|mouse_drag]]
|Fired when the mouse is moved after clicking.
|{{type|number}} mouse button
|{{type|number}} x coordinate(in screen chars)
|{{type|number}} y coordinate(in screen chars)
|-
! scope="row" | [[monitor_touch (event)|monitor_touch]]
|Fired when a player right click on an advanced monitor connected.
|{{type|string}} side
|{{type|number}} x coordinate(in screen chars)
|{{type|number}} y coordinate(in screen chars)
|}

== Guides ==
[http://www.computercraft.info/forums2/index.php?/topic/1516-ospullevent-what-is-it-and-how-is-it-useful/page__view__findpost__p__11156 ''Onionnion's Guide on os.pullEvent()'']

[[Category:Lua_Core_Functions]]

Os.pullEvent

2013-01-20T04:22:09Z

Eric: less -> fewer, tidy up

{{lowercase}}
{{Function
|name=os.pullEvent
|args=([[string]]) filter
|api=OS
|returns={{type|string}} event, variable parameters(see table below)
|addon=ComputerCraft
|desc=Waits (yields) until an event occurs
|examples=
{{Example
|desc=The program requires to wait for a keypress to do something:
|code=[[Function (type)|function]] clear()
[[term.clear]]()
[[term.setCursorPos]] (1,1)
end
while true do
clear()
[[print]] ("Press E to do something.")
local event, param1 = os.pullEvent ("char") -- limit os.pullEvent to the char event
if param1 == "e" then -- if the returned value was 'e'
clear()
[[write]] ("Name: ")
local name = [[read]]()
[[print]] (name)
break
else
clear()
[[print]] ("Wrong button!")
[[os.sleep|sleep]] (1.5) -- I don't like a whole 2 seconds but 1 second is too short
end
end
}}
}}

=== Common syntax ===

event, param1, param2, param3 = os.pullEvent()

Note: This is one of the most commonly used functions that can return multiple values.
It works like any other function call (such as "input = read()") except that you can get more than one piece of information back.

== How it works ==
When os.pullEvent() is called, the computer waits until an event occurs.
Events can be triggered by several different things, such as a key being pressed or a redstone input changing.
They are usually triggered by ComputerCraft itself, when it needs to notify the computer that something happened.
They can also be triggered by peripherals, or by your program calling [[os.queueEvent]].

More complicated input, such as "the user typing a line of text," does ''not'' correspond to an event.
[[read]] handles this inside itself by waiting for the user to press a key, then updating the screen, moving the cursor, etc.

Events have a type (which is a string) and 0-5 parameters (which are often but not always strings).
No built-in events use more than 3 parameters.

When an event occurs, the event type, followed by the parameters, will be returned. If you have:

event, button, x, y = os.pullEvent()

and the user clicks the mouse at coordinates 5,4 then:
* event will be set to "mouse_click" (the event type)
* button will be set to 0 (the first parameter)
* x will be set to 5 (the second parameter)
* y will be set to 4 (the third parameter)

Note that in this example, we didn't specify a filter. If you specify a filter, then all events of different types will be ignored.
If the user inserts a disk, instead of clicking the mouse, then event will be "disk", button will be the side the disk drive is on, and x and y will be nil.

If we wanted to only wait for mouse clicks we could use:

event, button, x, y = os.pullEvent("mouse_click")

which will ignore any events that are not mouse clicks.

If you assign more variables than necessary, the extra ones will be set to nil.
If you assign fewer variables than necessary, the extra parameters will be discarded.

==Event types==
{| class="wikitable" width="100%"
! rowspan="2" | Name
! rowspan="2" | Description
! colspan="3" | Parameters
|-
! 1 !! 2 !! 3
|-
! scope="row" | [[char (event)|char]]
|Fired when text is typed on the keyboard
| {{type|string}} the letter typed
|
|
|-
! scope="row" | [[key (event)|key]]
|Fired when a key is pressed on the keyboard
|{{type|number}} numerical keycode
|
|
|-
! scope="row" | [[timer (event)|timer]]
|Fired when a timeout started by [[os.startTimer]]() completes
|{{type|number}} Value of the timer as returned by os.startTimer()
|
|
|-
! scope="row" | [[alarm (event)|alarm]]
|Fired when a time passed to [[os.setAlarm]]() is reached
|{{type|number}} Value of the alarm as returned by os.setAlarm()
|
|
|-
! scope="row" | [[redstone (event)|redstone]]
|Fired when the state of any of the redstone inputs change
|
|
|
|-
! scope="row" | [[terminate (event)|terminate]]
|Fired when a combination of keys CTRL and T is pressed and held for three seconds.
You will not normally see this event, as it is handled inside os.pullEvent.
|
|
|
|-
! scope="row" | [[disk (event)|disk]]
|Fired when a disk is inserted into an adjacent disk drive
|{{type|string}} side
|
|
|-
! scope="row" | [[disk_eject (event)|disk_eject]]
|Fired when a disk is removed from an adjacent disk drive
|{{type|string}} side
|
|
|-
! scope="row" | [[peripheral (event)|peripheral]]
|Fired when peripheral is attached
|{{type|string}} side
|
|
|-
! scope="row" | [[peripheral_detach (event)| peripheral_detach]]
|Fired when peripheral is removed
|{{type|string}} side
|
|
|-
! scope="row" | [[rednet_message (event)|rednet_message]]
|Fired when a rednet message is received from the [[Rednet_(API)|rednet API]]
|{{type|number}} senderID
|{{type|string}} message
|{{type|number}} distance travelled
|-
! scope="row" | [[http_success (event)|http_success]]
|Fired when an attempt to receive text from / post text on a website is successful.
You will not normally see this event as it is handled inside http.get.
|{{type|string}} url of the site
|{{type|table}} text on the site
|
|-
! scope="row" | [[http_failure (event)|http_failure]]
|Fired when an attempt to receive text from / post text on a website is unsuccessful
You will not normally see this event as it is handled inside http.get.
|{{type|string}} url of the site
|
|
|-
! scope="row" | [[mouse_click (event)|mouse_click]]
|Fired when a mouse button is pressed
|{{type|number}} mouse button
|{{type|number}} x coordinate
|{{type|number}} y coordinate
|-
! scope="row" | [[mouse_scroll (event)|mouse_scroll]]
|Fired when a mousewheel is scrolled.
|{{type|number}} scroll direction (-1 for up, 1 for down)
|{{type|number}} x coordinate(in screen chars)
|{{type|number}} y coordinate(in screen chars)
|-
! scope="row" | [[mouse_drag (event)|mouse_drag]]
|Fired when the mouse is moved after clicking.
|{{type|number}} mouse button
|{{type|number}} x coordinate(in screen chars)
|{{type|number}} y coordinate(in screen chars)
|-
! scope="row" | [[monitor_touch (event)|monitor_touch]]
|Fired when a player right click on an advanced monitor connected.
|{{type|string}} side
|{{type|number}} x coordinate(in screen chars)
|{{type|number}} y coordinate(in screen chars)
|}

== Guides ==
[http://www.computercraft.info/forums2/index.php?/topic/1516-ospullevent-what-is-it-and-how-is-it-useful/page__view__findpost__p__11156 ''Onionnion's Guide on os.pullEvent()'']

[[Category:Lua_Core_Functions]]

Template:Type

2013-01-20T04:19:42Z

Eric: Simple template for indicating a variable type