OpenComputers: Rebooted - User contributions [en]

Item/tablet

2026-09-10T06:00:00Z

Michiyo:

= Tablet =

[[File:tablet.png|128px|tablet.png]]

Tablets are built by placing a [[Item/tablet case|Tablet Case]] into an [[Block/assembler|Assembler]], configuring as desired and assembling it. Tablets act as portable computers that cannot directly interact with the world - for example [[Item/redstone card|Redstone Cards]] do ''not'' work in them. A number of upgrades, however, do, such as the [[Item/sign upgrade|Sign Upgrade]] or the [[Item/piston upgrade|Piston Upgrade]].

You can sneak-click with a tablet in your hand to access the disk drive slot, and the power button to toggle the power off/on.

Tablets can be put into a [[Block/charger|Charger]] to refill their energy and to access the first hard disk built into the tablet from a computer connected to the charger - in this setup, the charger will act similar to a disk drive, with the tablet being the floppy disk. This can be very useful in case you forgot to install an OS on the hard drive built into the tablet, or after bricking a tablet's OS.

''Since version 1.7.3 for minecraft 1.12'' Tablets can '''also''' be charged by Forge Energy compatible machines, such as Thermal Expansion's Energetic Infuser.

== Contents ==

{{:Item/contents}}

Template:WIP

2026-09-01T21:05:57Z

Michiyo:

⚠ {{{1}}} ⚠

<noinclude>
== Usage ==

Use this template to mark content that is still a work in progress.

<pre>
{{WIP|This section is still being worked on.}}
</pre>

Displays as:

{{WIP|This section is still being worked on.}}

== Parameters ==

; <code>1</code>
: The message to display between the warning icons.

== Example ==

<pre>
{{WIP|Documentation is incomplete and may change.}}
</pre>

[[Category:Article message templates]]
</noinclude>

2026-09-01T20:50:45Z

Michiyo:

{{WIP|We are currently in the process of unifying the separate block/item pages and component API pages together for ease of navigation. If you find the dedicated component API page is missing, check the item page. Thank you for your patience during this transition.}}

{| class="oc-contents-table"
! colspan="2" | Links
|-
! [[Main Page|OpenComputers]]
|
|-
! General
| [[Openos|Install and Use OpenOS]] - [[Crossmod interoperation|Crossmod Interoperation]] - [[Lua conventions|Lua Conventions]] - [[Computer users|Computer Users]]
|}

{{:Block/contents}}
{{:Item/contents}}
{{:API/contents}}
{{:Component/contents}}
{{:Addon/contents}}
{{:Tutorial/contents}}

{|
! Other Languages
! Page
|-
| Simplified Chinese
| [[Start/zh|简体中文（Simplified Chinese）]]
|}

Template:WIP

2026-09-01T20:50:36Z

Michiyo: Created page with "⚠ {{{1}}} ⚠ <noinclude> == Usage == Use this template to mark content that is still a work in progress. <pre> {{WIP|This section is still being worked on.}} </pre> Displays as: {{WIP|This section is still being worked on.}} == Parameters == ; <code>1</code> : The message to display between the warning icons. == Example == <pre> {{WIP|Documentation is incomplete and may change.}} </pre>..."

⚠ {{{1}}} ⚠

<noinclude>
== Usage ==

Use this template to mark content that is still a work in progress.

<pre>
{{WIP|This section is still being worked on.}}
</pre>

Displays as:

{{WIP|This section is still being worked on.}}

== Parameters ==

; <code>1</code>
: The message to display between the warning icons.

== Example ==

<pre>
{{WIP|Documentation is incomplete and may change.}}
</pre>

[[Category:Article message templates]]
</noinclude>

Projector

2026-09-01T07:28:26Z

Michiyo:

= Projector =

[[File:projector.png|Projector]]

The projector is a long-range, flat display controlled by a computer. It can either render a 320x200 pixel framebuffer directly, or emulate a normal OpenComputers <code>screen</code> component with a 160x50 character display.

The projected image is not a physical block and does not need a wall or other screen block behind it. The projector raycasts in its facing direction and places the display on the first collidable block it reaches, up to 12.5 blocks away. If no block is hit, it uses the maximum distance. The projection is scaled with distance, so a nearby surface produces a smaller image. A tiny offset from the target surface prevents z-fighting.

== Placement and modes ==

The projector faces away from the player when placed. Its [[Item/scrench|scrench]] has a special function: right-clicking the projector toggles between pixel mode and screen mode instead of rotating the block. The selected mode is saved with the projector.

Only the component for the active mode is visible on the OpenComputers network:

* Pixel mode exposes a <code>projector</code> component and hides the <code>screen</code> component.
* Screen mode exposes a native <code>screen</code> component and hides the <code>projector</code> component.

The two component addresses are separate. Use <code>component.list("projector")</code> or <code>component.list("screen")</code> after changing modes; do not expect the projector's address to be the screen's address.

== Pixel mode ==

Pixel mode provides a 320x200 RGBA framebuffer. Coordinates are one-based, with <code>(1, 1)</code> at the upper-left corner. Colors may be supplied as <code>0xRRGGBB</code> for an opaque color or <code>0xAARRGGBB</code> for an explicit alpha value. Color <code>0</code> is transparent black.

The projector component provides these callbacks:

{| class="wikitable"
! Callback
! Description
|-
| <code>getResolution()</code>
| Returns <code>320, 200</code>.
|-
| <code>isProjecting()</code>
| Returns whether the projector is on and powered.
|-
| <code>turnOn()</code> / <code>turnOff()</code>
| Enable or disable projection.
|-
| <code>get(x, y)</code>
| Returns the RGB color at a pixel.
|-
| <code>set(x, y, color)</code>
| Sets one pixel.
|-
| <code>fill(x, y, width, height, color)</code>
| Fills a rectangle.
|-
| <code>clear()</code>
| Clears the framebuffer to transparent black.
|-
| <code>setRaw(data)</code>
| Sets row-major RGBA bytes. There are four bytes per pixel; incomplete data clears the remaining pixels.
|}

Pixel mode consumes energy while the projector is on. Large updates are sent to clients as compressed framebuffer updates, so a saved framebuffer can be restored when its chunk is loaded.

Example:

<syntaxhighlight lang="lua">
local component = require("component")
local projector = component.proxy(component.list("projector")())

projector.clear()
projector.fill(1, 1, 320, 200, 0xFF101820)
projector.fill(20, 20, 280, 160, 0xFF204060)
projector.set(25, 25, 0xFFFFCC00)
</syntaxhighlight>

== Screen mode ==

Screen mode emulates a native OpenComputers T3 screen:

* Resolution: 160x50 characters
* Maximum color depth: 8-bit
* Standard <code>screen</code> and <code>gpu</code> APIs
* Normal screen text, color, palette, mouse, and keyboard behavior

Use a graphics card to draw to the projected screen just as with any other OpenComputers screen. If it is the only screen available, the GPU may already be bound to it; binding explicitly makes a program unambiguous.

<syntaxhighlight lang="lua">
local component = require("component")
local gpu = component.gpu
local screenAddress = component.list("screen")()

gpu.bind(screenAddress)
gpu.setResolution(160, 50)
gpu.setDepth(8)
gpu.setBackground(0x102030)
gpu.setForeground(0xFFFFFF)
gpu.fill(1, 1, 160, 50, " ")
gpu.set(2, 2, "Hello from the projector")
</syntaxhighlight>

Right-clicking the visible projected screen opens the normal OpenComputers screen interface. The interface accepts mouse and keyboard input. An OpenComputers [[Block/keyboard|keyboard]] placed next to the projector can also be used for normal in-world screen input.

The screen's text buffer is saved with the projector, and the emulated screen component is restored when the projector's chunk is loaded.

== Power and troubleshooting ==

The projector must be connected to a powered OpenComputers network. In pixel mode, check for the <code>projector</code> component. In screen mode, check for the <code>screen</code> component instead. The inactive mode is intentionally absent from component listings.

If a program cached a component address before switching modes, enumerate the active component again. Component addresses can also change when a component is recreated, so programs should prefer component type/name discovery over hard-coding an address.

Projector

2026-09-01T07:27:43Z

Michiyo:

= Projector =

[[File:projector.png|Projector]]

The projector is a long-range, flat display controlled by a computer. It can either render a 320x200 pixel framebuffer directly, or emulate a normal OpenComputers <code>screen</code> component with a 160x50 character display.

The projected image is not a physical block and does not need a wall or other screen block behind it. The projector raycasts in its facing direction and places the display on the first collidable block it reaches, up to 12.5 blocks away. If no block is hit, it uses the maximum distance. The projection is scaled with distance, so a nearby surface produces a smaller image. A tiny offset from the target surface prevents z-fighting.

== Placement and modes ==

The projector faces away from the player when placed. Its [[Item/scrench|scrench]] has a special function: right-clicking the projector toggles between pixel mode and screen mode instead of rotating the block. The selected mode is saved with the projector.

Only the component for the active mode is visible on the OpenComputers network:

* Pixel mode exposes a <code>projector</code> component and hides the <code>screen</code> component.
* Screen mode exposes a native <code>screen</code> component and hides the <code>projector</code> component.

The two component addresses are separate. Use <code>component.list("projector")</code> or <code>component.list("screen")</code> after changing modes; do not expect the projector's address to be the screen's address.

== Pixel mode ==

Pixel mode provides a 320x200 RGBA framebuffer. Coordinates are one-based, with <code>(1, 1)</code> at the upper-left corner. Colors may be supplied as <code>0xRRGGBB</code> for an opaque color or <code>0xAARRGGBB</code> for an explicit alpha value. Color <code>0</code> is transparent black.

The projector component provides these callbacks:

{| class="wikitable"
! Callback
! Description
|-
| <code>getResolution()</code>
| Returns <code>320, 200</code>.
|-
| <code>isProjecting()</code>
| Returns whether the projector is on and powered.
|-
| <code>turnOn()</code> / <code>turnOff()</code>
| Enable or disable projection.
|-
| <code>get(x, y)</code>
| Returns the RGB color at a pixel.
|-
| <code>set(x, y, color)</code>
| Sets one pixel.
|-
| <code>fill(x, y, width, height, color)</code>
| Fills a rectangle.
|-
| <code>clear()</code>
| Clears the framebuffer to transparent black.
|-
| <code>setRaw(data)</code>
| Sets row-major RGBA bytes. There are four bytes per pixel; incomplete data clears the remaining pixels.
|}

Pixel mode consumes energy while the projector is on. Large updates are sent to clients as compressed framebuffer updates, so a saved framebuffer can be restored when its chunk is loaded.

Example:

<syntaxhighlight lang="lua">
local component = require("component")
local projector = component.proxy(component.list("projector")())

projector.clear()
projector.fill(1, 1, 320, 200, 0xFF101820)
projector.fill(20, 20, 280, 160, 0xFF204060)
projector.set(25, 25, 0xFFFFCC00)
</syntaxhighlight>

== Screen mode ==

Screen mode emulates a native OpenComputers T3 screen:

* Resolution: 160x50 characters
* Maximum color depth: 8-bit
* Standard <code>screen</code> and <code>gpu</code> APIs
* Normal screen text, color, palette, mouse, and keyboard behavior

Use a graphics card to draw to the projected screen just as with any other OpenComputers screen. If it is the only screen available, the GPU may already be bound to it; binding explicitly makes a program unambiguous.

<syntaxhighlight lang="lua">
local component = require("component")
local gpu = component.gpu
local screenAddress = component.list("screen")()

gpu.bind(screenAddress)
gpu.setResolution(160, 50)
gpu.setDepth(8)
gpu.setBackground(0x102030)
gpu.setForeground(0xFFFFFF)
gpu.fill(1, 1, 160, 50, " ")
gpu.set(2, 2, "Hello from the projector")
</syntaxhighlight>

Right-clicking the visible projected screen opens the normal OpenComputers screen interface. The interface accepts mouse and keyboard input. An OpenComputers [[Keyboard|keyboard]] placed next to the projector can also be used for normal in-world screen input.

The screen's text buffer is saved with the projector, and the emulated screen component is restored when the projector's chunk is loaded.

== Power and troubleshooting ==

The projector must be connected to a powered OpenComputers network. In pixel mode, check for the <code>projector</code> component. In screen mode, check for the <code>screen</code> component instead. The inactive mode is intentionally absent from component listings.

If a program cached a component address before switching modes, enumerate the active component again. Component addresses can also change when a component is recreated, so programs should prefer component type/name discovery over hard-coding an address.

Projector

2026-09-01T07:26:26Z

Michiyo: /* Placement and modes */

= Projector =

[[File:projector.png|Projector]]

The projector is a long-range, flat display controlled by a [[Computer|computer]]. It can either render a 320x200 pixel framebuffer directly, or emulate a normal OpenComputers <code>screen</code> component with a 160x50 character display.

The projected image is not a physical block and does not need a wall or other screen block behind it. The projector raycasts in its facing direction and places the display on the first collidable block it reaches, up to 12.5 blocks away. If no block is hit, it uses the maximum distance. The projection is scaled with distance, so a nearby surface produces a smaller image. A tiny offset from the target surface prevents z-fighting.

== Placement and modes ==

The projector faces away from the player when placed. Its [[Item/scrench|scrench]] has a special function: right-clicking the projector toggles between pixel mode and screen mode instead of rotating the block. The selected mode is saved with the projector.

Only the component for the active mode is visible on the OpenComputers network:

* Pixel mode exposes a <code>projector</code> component and hides the <code>screen</code> component.
* Screen mode exposes a native <code>screen</code> component and hides the <code>projector</code> component.

The two component addresses are separate. Use <code>component.list("projector")</code> or <code>component.list("screen")</code> after changing modes; do not expect the projector's address to be the screen's address.

== Pixel mode ==

Pixel mode provides a 320x200 RGBA framebuffer. Coordinates are one-based, with <code>(1, 1)</code> at the upper-left corner. Colors may be supplied as <code>0xRRGGBB</code> for an opaque color or <code>0xAARRGGBB</code> for an explicit alpha value. Color <code>0</code> is transparent black.

The projector component provides these callbacks:

{| class="wikitable"
! Callback
! Description
|-
| <code>getResolution()</code>
| Returns <code>320, 200</code>.
|-
| <code>isProjecting()</code>
| Returns whether the projector is on and powered.
|-
| <code>turnOn()</code> / <code>turnOff()</code>
| Enable or disable projection.
|-
| <code>get(x, y)</code>
| Returns the RGB color at a pixel.
|-
| <code>set(x, y, color)</code>
| Sets one pixel.
|-
| <code>fill(x, y, width, height, color)</code>
| Fills a rectangle.
|-
| <code>clear()</code>
| Clears the framebuffer to transparent black.
|-
| <code>setRaw(data)</code>
| Sets row-major RGBA bytes. There are four bytes per pixel; incomplete data clears the remaining pixels.
|}

Pixel mode consumes energy while the projector is on. Large updates are sent to clients as compressed framebuffer updates, so a saved framebuffer can be restored when its chunk is loaded.

Example:

<syntaxhighlight lang="lua">
local component = require("component")
local projector = component.proxy(component.list("projector")())

projector.clear()
projector.fill(1, 1, 320, 200, 0xFF101820)
projector.fill(20, 20, 280, 160, 0xFF204060)
projector.set(25, 25, 0xFFFFCC00)
</syntaxhighlight>

== Screen mode ==

Screen mode emulates a native OpenComputers T3 screen:

* Resolution: 160x50 characters
* Maximum color depth: 8-bit
* Standard <code>screen</code> and <code>gpu</code> APIs
* Normal screen text, color, palette, mouse, and keyboard behavior

Use a graphics card to draw to the projected screen just as with any other OpenComputers screen. If it is the only screen available, the GPU may already be bound to it; binding explicitly makes a program unambiguous.

<syntaxhighlight lang="lua">
local component = require("component")
local gpu = component.gpu
local screenAddress = component.list("screen")()

gpu.bind(screenAddress)
gpu.setResolution(160, 50)
gpu.setDepth(8)
gpu.setBackground(0x102030)
gpu.setForeground(0xFFFFFF)
gpu.fill(1, 1, 160, 50, " ")
gpu.set(2, 2, "Hello from the projector")
</syntaxhighlight>

Right-clicking the visible projected screen opens the normal OpenComputers screen interface. The interface accepts mouse and keyboard input. An OpenComputers [[Keyboard|keyboard]] placed next to the projector can also be used for normal in-world screen input.

The screen's text buffer is saved with the projector, and the emulated screen component is restored when the projector's chunk is loaded.

== Power and troubleshooting ==

The projector must be connected to a powered OpenComputers network. In pixel mode, check for the <code>projector</code> component. In screen mode, check for the <code>screen</code> component instead. The inactive mode is intentionally absent from component listings.

If a program cached a component address before switching modes, enumerate the active component again. Component addresses can also change when a component is recreated, so programs should prefer component type/name discovery over hard-coding an address.

Projector

2026-09-01T07:23:41Z

Michiyo: Created page with "= Projector = Projector The projector is a long-range, flat display controlled by a computer. It can either render a 320x200 pixel framebuffer directly, or emulate a normal OpenComputers <code>screen</code> component with a 160x50 character display. The projected image is not a physical block and does not need a wall or other screen block behind it. The projector raycasts in its facing direction and places the display on the first c..."

= Projector =

[[File:projector.png|Projector]]

The projector is a long-range, flat display controlled by a [[Computer|computer]]. It can either render a 320x200 pixel framebuffer directly, or emulate a normal OpenComputers <code>screen</code> component with a 160x50 character display.

The projected image is not a physical block and does not need a wall or other screen block behind it. The projector raycasts in its facing direction and places the display on the first collidable block it reaches, up to 12.5 blocks away. If no block is hit, it uses the maximum distance. The projection is scaled with distance, so a nearby surface produces a smaller image. A tiny offset from the target surface prevents z-fighting.

== Placement and modes ==

The projector faces away from the player when placed. Its [[Item/wrench|scrench]] has a special function: right-clicking the projector toggles between pixel mode and screen mode instead of rotating the block. The selected mode is saved with the projector.

Only the component for the active mode is visible on the OpenComputers network:

* Pixel mode exposes a <code>projector</code> component and hides the <code>screen</code> component.
* Screen mode exposes a native <code>screen</code> component and hides the <code>projector</code> component.

The two component addresses are separate. Use <code>component.list("projector")</code> or <code>component.list("screen")</code> after changing modes; do not expect the projector's address to be the screen's address.

== Pixel mode ==

Pixel mode provides a 320x200 RGBA framebuffer. Coordinates are one-based, with <code>(1, 1)</code> at the upper-left corner. Colors may be supplied as <code>0xRRGGBB</code> for an opaque color or <code>0xAARRGGBB</code> for an explicit alpha value. Color <code>0</code> is transparent black.

The projector component provides these callbacks:

{| class="wikitable"
! Callback
! Description
|-
| <code>getResolution()</code>
| Returns <code>320, 200</code>.
|-
| <code>isProjecting()</code>
| Returns whether the projector is on and powered.
|-
| <code>turnOn()</code> / <code>turnOff()</code>
| Enable or disable projection.
|-
| <code>get(x, y)</code>
| Returns the RGB color at a pixel.
|-
| <code>set(x, y, color)</code>
| Sets one pixel.
|-
| <code>fill(x, y, width, height, color)</code>
| Fills a rectangle.
|-
| <code>clear()</code>
| Clears the framebuffer to transparent black.
|-
| <code>setRaw(data)</code>
| Sets row-major RGBA bytes. There are four bytes per pixel; incomplete data clears the remaining pixels.
|}

Pixel mode consumes energy while the projector is on. Large updates are sent to clients as compressed framebuffer updates, so a saved framebuffer can be restored when its chunk is loaded.

Example:

<syntaxhighlight lang="lua">
local component = require("component")
local projector = component.proxy(component.list("projector")())

projector.clear()
projector.fill(1, 1, 320, 200, 0xFF101820)
projector.fill(20, 20, 280, 160, 0xFF204060)
projector.set(25, 25, 0xFFFFCC00)
</syntaxhighlight>

== Screen mode ==

Screen mode emulates a native OpenComputers T3 screen:

* Resolution: 160x50 characters
* Maximum color depth: 8-bit
* Standard <code>screen</code> and <code>gpu</code> APIs
* Normal screen text, color, palette, mouse, and keyboard behavior

Use a graphics card to draw to the projected screen just as with any other OpenComputers screen. If it is the only screen available, the GPU may already be bound to it; binding explicitly makes a program unambiguous.

<syntaxhighlight lang="lua">
local component = require("component")
local gpu = component.gpu
local screenAddress = component.list("screen")()

gpu.bind(screenAddress)
gpu.setResolution(160, 50)
gpu.setDepth(8)
gpu.setBackground(0x102030)
gpu.setForeground(0xFFFFFF)
gpu.fill(1, 1, 160, 50, " ")
gpu.set(2, 2, "Hello from the projector")
</syntaxhighlight>

Right-clicking the visible projected screen opens the normal OpenComputers screen interface. The interface accepts mouse and keyboard input. An OpenComputers [[Keyboard|keyboard]] placed next to the projector can also be used for normal in-world screen input.

The screen's text buffer is saved with the projector, and the emulated screen component is restored when the projector's chunk is loaded.

== Power and troubleshooting ==

The projector must be connected to a powered OpenComputers network. In pixel mode, check for the <code>projector</code> component. In screen mode, check for the <code>screen</code> component instead. The inactive mode is intentionally absent from component listings.

If a program cached a component address before switching modes, enumerate the active component again. Component addresses can also change when a component is recreated, so programs should prefer component type/name discovery over hard-coding an address.

MediaWiki:Common.css

2026-08-30T16:31:26Z

Michiyo:

/* CSS placed here will be applied to all skins */
.client-darkmode .mw-parser-output img,
.client-darkmode .mw-parser-output .image {
filter: invert(1) hue-rotate(180deg);
}
/* Undo DarkMode's inversion for images */
.client-darkmode .mw-parser-output img,
.client-darkmode .mw-parser-output .image,
.client-darkmode .mw-logo-icon,
.client-darkmode #p-logo .mw-wiki-logo {
filter: invert(1) hue-rotate(180deg) !important;
}
.oc-contents-table {
width: 100%;
table-layout: fixed;
}

.oc-contents-table th:nth-child(1),
.oc-contents-table td:nth-child(1) {
width: 12%;
}

.oc-contents-table th:nth-child(2),
.oc-contents-table td:nth-child(2) {
width: 16%;
}

.oc-contents-table th:nth-child(3),
.oc-contents-table td:nth-child(3) {
width: 72%;
}
.oc-contents-table {
border-collapse: collapse;
margin: 0 0 0.75em 0;
}

.oc-contents-table th,
.oc-contents-table td {
vertical-align: top;
}

/* Force MediaWiki's built-in table of contents to the right */
#toc,
.toc {
float: right;
clear: right;

width: 20em;
max-width: 30%;

margin: 0 0 1em 1.5em;
}

/* Keep very large TOCs from becoming absurdly tall */
#toc .tocnumber,
#toc .toctext {
display: inline;
}

/* Narrow/mobile screens: return TOC to normal document flow */
@media screen and (max-width: 850px) {
#toc,
.toc {
float: none;
clear: both;

width: auto;
max-width: none;

margin: 1em 0;
}
}

/* OpenComputers documentation navigation tables */
.oc-contents-table {
width: 100%;
max-width: 1400px;
margin: 1em auto;

border: 1px solid #a2a9b1;
border-collapse: separate;
border-spacing: 0;

background: #f8f9fa;
font-size: 0.95em;
line-height: 1.55;
}

/* Main column headings */
.oc-contents-table > tbody > tr:first-child > th {
padding: 0.6em 0.9em;

background: #eaecf0;
border-bottom: 1px solid #a2a9b1;

text-align: left;
font-weight: bold;
}

/* General cell spacing */
.oc-contents-table th,
.oc-contents-table td {
padding: 0.55em 0.9em;
vertical-align: top;
}

/* First column: Components / API / Items / etc. */
.oc-contents-table tr > th:first-child:not(:only-child) {
width: 10em;
}

/* Category column */
.oc-contents-table tr > th:nth-child(2) {
width: 13em;

background: #f1f3f5;
border-left: 1px solid #c8ccd1;
border-right: 1px solid #c8ccd1;

text-align: right;
white-space: nowrap;
}

/* Documentation/link area */
.oc-contents-table td {
background: #fff;
}

/* Separate category rows */
.oc-contents-table tr + tr > th,
.oc-contents-table tr + tr > td {
border-top: 1px solid #eaecf0;
}

/* Make links breathe a little */
.oc-contents-table td a {
line-height: 1.8;
}

/* Don't let visited links make these navigation boxes ugly */
.oc-contents-table a:visited {
color: #36c;
}

/* Narrow displays */
@media screen and (max-width: 850px) {
.oc-contents-table {
font-size: 0.9em;
}

.oc-contents-table tr > th:first-child,
.oc-contents-table tr > th:nth-child(2) {
width: auto;
white-space: normal;
}
}

MediaWiki:Common.css

2026-08-30T16:29:48Z

Michiyo: Undo revision 1727 by Michiyo (talk)

/* CSS placed here will be applied to all skins */
.client-darkmode .mw-parser-output img,
.client-darkmode .mw-parser-output .image {
filter: invert(1) hue-rotate(180deg);
}
.oc-contents-table {
width: 100%;
table-layout: fixed;
}

.oc-contents-table th:nth-child(1),
.oc-contents-table td:nth-child(1) {
width: 12%;
}

.oc-contents-table th:nth-child(2),
.oc-contents-table td:nth-child(2) {
width: 16%;
}

.oc-contents-table th:nth-child(3),
.oc-contents-table td:nth-child(3) {
width: 72%;
}
.oc-contents-table {
border-collapse: collapse;
margin: 0 0 0.75em 0;
}

.oc-contents-table th,
.oc-contents-table td {
vertical-align: top;
}

/* Force MediaWiki's built-in table of contents to the right */
#toc,
.toc {
float: right;
clear: right;

width: 20em;
max-width: 30%;

margin: 0 0 1em 1.5em;
}

/* Keep very large TOCs from becoming absurdly tall */
#toc .tocnumber,
#toc .toctext {
display: inline;
}

/* Narrow/mobile screens: return TOC to normal document flow */
@media screen and (max-width: 850px) {
#toc,
.toc {
float: none;
clear: both;

width: auto;
max-width: none;

margin: 1em 0;
}
}

/* OpenComputers documentation navigation tables */
.oc-contents-table {
width: 100%;
max-width: 1400px;
margin: 1em auto;

border: 1px solid #a2a9b1;
border-collapse: separate;
border-spacing: 0;

background: #f8f9fa;
font-size: 0.95em;
line-height: 1.55;
}

/* Main column headings */
.oc-contents-table > tbody > tr:first-child > th {
padding: 0.6em 0.9em;

background: #eaecf0;
border-bottom: 1px solid #a2a9b1;

text-align: left;
font-weight: bold;
}

/* General cell spacing */
.oc-contents-table th,
.oc-contents-table td {
padding: 0.55em 0.9em;
vertical-align: top;
}

/* First column: Components / API / Items / etc. */
.oc-contents-table tr > th:first-child:not(:only-child) {
width: 10em;
}

/* Category column */
.oc-contents-table tr > th:nth-child(2) {
width: 13em;

background: #f1f3f5;
border-left: 1px solid #c8ccd1;
border-right: 1px solid #c8ccd1;

text-align: right;
white-space: nowrap;
}

/* Documentation/link area */
.oc-contents-table td {
background: #fff;
}

/* Separate category rows */
.oc-contents-table tr + tr > th,
.oc-contents-table tr + tr > td {
border-top: 1px solid #eaecf0;
}

/* Make links breathe a little */
.oc-contents-table td a {
line-height: 1.8;
}

/* Don't let visited links make these navigation boxes ugly */
.oc-contents-table a:visited {
color: #36c;
}

/* Narrow displays */
@media screen and (max-width: 850px) {
.oc-contents-table {
font-size: 0.9em;
}

.oc-contents-table tr > th:first-child,
.oc-contents-table tr > th:nth-child(2) {
width: auto;
white-space: normal;
}
}

MediaWiki:Common.css

2026-08-30T16:28:09Z

Michiyo:

/* CSS placed here will be applied to all skins */
/* Do not invert normal images in dark mode */
.client-darkmode .mw-parser-output img,
.client-darkmode .mw-parser-output .image {
filter: none !important;
}
.oc-contents-table {
width: 100%;
table-layout: fixed;
}

.oc-contents-table th:nth-child(1),
.oc-contents-table td:nth-child(1) {
width: 12%;
}

.oc-contents-table th:nth-child(2),
.oc-contents-table td:nth-child(2) {
width: 16%;
}

.oc-contents-table th:nth-child(3),
.oc-contents-table td:nth-child(3) {
width: 72%;
}
.oc-contents-table {
border-collapse: collapse;
margin: 0 0 0.75em 0;
}

.oc-contents-table th,
.oc-contents-table td {
vertical-align: top;
}

/* Force MediaWiki's built-in table of contents to the right */
#toc,
.toc {
float: right;
clear: right;

width: 20em;
max-width: 30%;

margin: 0 0 1em 1.5em;
}

/* Keep very large TOCs from becoming absurdly tall */
#toc .tocnumber,
#toc .toctext {
display: inline;
}

/* Narrow/mobile screens: return TOC to normal document flow */
@media screen and (max-width: 850px) {
#toc,
.toc {
float: none;
clear: both;

width: auto;
max-width: none;

margin: 1em 0;
}
}

/* OpenComputers documentation navigation tables */
.oc-contents-table {
width: 100%;
max-width: 1400px;
margin: 1em auto;

border: 1px solid #a2a9b1;
border-collapse: separate;
border-spacing: 0;

background: #f8f9fa;
font-size: 0.95em;
line-height: 1.55;
}

/* Main column headings */
.oc-contents-table > tbody > tr:first-child > th {
padding: 0.6em 0.9em;

background: #eaecf0;
border-bottom: 1px solid #a2a9b1;

text-align: left;
font-weight: bold;
}

/* General cell spacing */
.oc-contents-table th,
.oc-contents-table td {
padding: 0.55em 0.9em;
vertical-align: top;
}

/* First column: Components / API / Items / etc. */
.oc-contents-table tr > th:first-child:not(:only-child) {
width: 10em;
}

/* Category column */
.oc-contents-table tr > th:nth-child(2) {
width: 13em;

background: #f1f3f5;
border-left: 1px solid #c8ccd1;
border-right: 1px solid #c8ccd1;

text-align: right;
white-space: nowrap;
}

/* Documentation/link area */
.oc-contents-table td {
background: #fff;
}

/* Separate category rows */
.oc-contents-table tr + tr > th,
.oc-contents-table tr + tr > td {
border-top: 1px solid #eaecf0;
}

/* Make links breathe a little */
.oc-contents-table td a {
line-height: 1.8;
}

/* Don't let visited links make these navigation boxes ugly */
.oc-contents-table a:visited {
color: #36c;
}

/* Narrow displays */
@media screen and (max-width: 850px) {
.oc-contents-table {
font-size: 0.9em;
}

.oc-contents-table tr > th:first-child,
.oc-contents-table tr > th:nth-child(2) {
width: auto;
white-space: normal;
}
}

Tutorials

2026-08-30T16:21:58Z