Opencomputers物品与手册翻译重制

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/accesspoint.md

@@ -0,0 +1,13 @@
+# Access Point
+
+![AAA](oredict:oc:accessPoint)
+
+*This block is deprecated and will be removed in a future version.* Craft it into a [relay](relay.md) to avoid losing it.
+
+The access point is the wireless version of the [switch](switch.md). It can be used to separate subnetworks so that machines in them will not see [components](../general/computer.md) in other networks, while still allowing to send network messages to the machines in other networks.
+
+In addition to that, this block can act as a repeater: it can re-send wired messages as wired messages to other devices; or wireless messages as wired or wireless messages. 
+
+[Switches](switch.md) and access point do *not* keep track of which packets they relayed recently, so avoid cycles in your network or you may receive the same packet multiple times. Due to the limited buffer size of switches, packet loss can occur when trying to send network messages too frequently. You can upgrade your switches and access points to increase the speed at which they relay messages, as well as their internal message queue size.
+
+Packets are only re-sent a certain number of times, so chaining an arbitrary number of [switches](switch.md) or access points is not possible. By default, a packet will be re-sent up to five times.

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/adapter.md

@@ -0,0 +1,8 @@
+# Adapter
+
+![Now with 100% more everything.](oredict:oc:adapter)
+
+The adapter allows [computers](../general/computer.md) to interact with blocks from vanilla Minecraft or other mods. Supported blocks adjacent to the adapter will show up as components in [computers](../general/computer.md) connected to the adapter.
+
+In addition to this, the adapter provides a slot for a few select upgrades. For example, the [inventory controller upgrade](../item/inventoryControllerUpgrade.md) allows computers to query more information from an inventory adjacent to the adapter, similar to when the upgrade is installed in a device (such as a [robot](robot.md) or [drone](../item/drone.md)), and a [tank controller upgrade](../item/tankControllerUpgrade.md) provides similar functionality for fluid tanks next to the adapter.
+Furthermore, you can insert a bound [MFU](../item/mfu.md) to interact with blocks a few spaces away.

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/assembler.md

@@ -0,0 +1,13 @@
+# Assembler
+
+![Harder, better, faster, stronger.](oredict:oc:assembler)
+
+The assembler is an advanced workstation that can be used to build more complex electronic devices, such as [robots](robot.md), [drones](../item/drone.md) and [tablets](../item/tablet.md). They require a large amount of energy to assemble devices, so it is recommended to power them sufficiently with a [capacitor bank](capacitor.md).
+
+To build a device using an assembler, insert the base part for that device. For [robots](robot.md), that is a [computer case](case1.md) of any tier; and for [tablets](../item/tablet.md), a [tablet case](../item/tabletCase1.md). As with all OpenComputers inventories, the parts that can be inserted into specific slots; hovering over a slot highlights the parts in your inventory that can go into the slot. If you have NEI open, filtered to show OpenComputers items, compatible items will be highlighted in NEI as well. Continue to insert any parts you would like the device to contain. Take particular care to provide an operating system, or a way to install one later on (for robots you can install a [disk drive](diskDrive.md) to insert and remove [floppies](../item/floppy.md) later on, for example). For most devices, their [EEPROM](../item/eeprom.md) can be changed later on, by crafting the device together with a different [EEPROM](../item/eeprom.md) to insert in them. Existing [EEPROM](../item/eeprom.md) on the device will be returned to your inventory.
+
+Also note that for [robots](robot.md) to have a [screen](screen1.md), you will need to install a [screen (tier 1)](screen1.md) in them, and to allow typing on the [screen](screen1.md), you will need to install a [keyboard](keyboard.md). For [tablets](../item/tablet.md), the [screen](screen1.md) is pre-installed in the [tablet case](../item/tabletCase1.md), but you will need to install a [keyboard](keyboard.md) if you wish to type on the [tablet](../item/tablet.md).
+
+Once everything is in place, press the start button and wait for the device to be assembled and charged. It is important to remember that you *cannot* change the device after it has been assembled. If you forgot something or made a mistake, you will have to disassemble the device using the [disassembler](disassembler.md), which has a slight chance of breaking parts in the process.
+
+A final note on complexity: the tier of an item determines how much complexity it requires, with tier 1 items requiring 1 complexity, tier 2 requiring 2 and tier 3 requiring 3. Container upgrades are the exception, where the complexity is twice the tier of the container (eg: a tier 2 [upgrade containers](../item/upgradeContainer1.md) requires 4 complexity, and likewise for [card containers](../item/cardContainer1.md)).

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/cable.md

@@ -0,0 +1,9 @@
+# Cable
+
+![Salad.](oredict:oc:cable)
+
+The cable serves as a way of connecting [computers](../general/computer.md) and machines that are far apart. If you have a compact build where all components touch each other (directly or indirectly, most blocks also behave the same way as cables) you will usually not need cables.
+
+Cables can be colored using any kind of dye. Colored cables will only connect to cables of the same color and to light gray colored cables - the default color. This can be useful for running cables for multiple subnetworks in parallel, without using covers.
+
+If necessary, cables can be covered using Forge MultiPart covers, or Immibis Microblocks covers. Keep in mind that [3D prints](print.md) are Forge MultiPart compatible, so it is possible to print custom covers, if desired.

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/capacitor.md

@@ -0,0 +1,9 @@
+# Capacitor
+
+![It's over 9000.](oredict:oc:capacitor)
+
+The capacitor stores energy to be used by the network, acting as an energy buffer when needed. Unlike conversion from other mod's energy to OpenComputers' internal energy type (using a [power converter](powerConverter.md) for example), transferring energy inside a single subnetwork is instantaneous. Having an internal energy buffer will be useful for tasks that require a lot of energy, such as [assembling](assembler.md) and/or [charging](charger.md) devices such as [robots](robot.md) or [drones](../item/drone.md). 
+
+The storage efficiency of capacitors increases with the number of capacitors in direct contact or in the vicinity. For example, two capacitors directly next to each other will have a higher storage capacity than the sum of two separated capacitors. This adjacency bonus applies for capacitors up to two blocks away, and is reduced as the distance between capacitors increases.
+
+The capacitor can be connected to a [power distributor](powerDistributor.md) to provide power to other [computers](../general/computer.md) or machines on the network.

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/case1.md

@@ -0,0 +1,37 @@
+# Computer Case
+
+![Just in case.](oredict:oc:case1)
+
+Computer cases come in three different tiers, which limits the components that can be inserted into them. An additional tier also exists for use in creative mode only. Computer cases can also be placed inside an [assembler](assembler.md) to build [robots](robot.md).
+
+The maximum tier of the component that can be inserted into any slot of a computer case can be seen as a small roman numeral in the corner of a tier-limited slot. A tier 2 slot can take a tier 1 component, for instance.
+
+The tier 1 case can house up to and including the following components:
+- 2x tier 1 expansion cards (such as [graphics cards](../item/graphicsCard1.md), [network cards](../item/lanCard.md), etc)
+- 1x tier 1 [CPU](../item/cpu1.md)
+- 2x tier 1 [RAM](../item/ram1.md)
+- 1x tier 1 [HDD](../item/hdd1.md)
+
+The tier 2 case can house up to and including the following components:
+- 1x tier 1 Expansion card (such as [graphics cards](../item/graphicsCard1.md), [network cards](../item/lanCard.md), etc)
+- 1x tier 2 Expansion card
+- 1x tier 2 [CPU](../item/cpu2.md)
+- 2x tier 2 [RAM](../item/ram3.md)
+- 1x tier 1 [HDD](../item/hdd1.md)
+- 1x tier 2 [HDD](../item/hdd2.md)
+
+The tier 3 case can house up to and including the following components:
+- 1x tier 3 Expansion card (such as [graphics cards](../item/graphicsCard1.md), [network cards](../item/lanCard.md), etc)
+- 2x tier 2 Expansion card
+- 1x tier 3 [CPU](../item/cpu3.md)
+- 2x tier 3 [RAM](../item/ram5.md)
+- 1x tier 2 [HDD](../item/hdd2.md)
+- 1x tier 3 [HDD](../item/hdd3.md)
+- 1x [floppy disk](../item/floppy.md)
+
+The tier 4 (Creative) case can house the following components:
+- 3x tier 3 Expansion cards (such as [graphics cards](../item/graphicsCard1.md), [network cards](../item/lanCard.md), etc)
+- 1x tier 3 [CPU](../item/cpu3.md)
+- 2x tier 3 [RAM](../item/ram5.md)
+- 2x tier 3 [HDD](../item/hdd3.md)
+- 1x [floppy disk](../item/floppy.md)

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/case2.md

@@ -0,0 +1 @@
+#REDIRECT case1.md

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/case3.md

@@ -0,0 +1 @@
+#REDIRECT case1.md

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/casecreative.md

@@ -0,0 +1 @@
+#REDIRECT case1.md

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/chameliumblock.md

@@ -0,0 +1,7 @@
+# Block of Chamelium
+
+![So... blank.](oredict:oc:chameliumBlock)
+
+A few pieces of [chamelium](../item/chamelium.md) can be combined to provide a monochrome block for decorative purposes. Chamelium blocks can also be dyed with any of the 16 Minecraft colors. 
+
+Using the Chamelium block as a texture for [3D prints](print.md) provides a clean white surface for applying tints.

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/charger.md

@@ -0,0 +1,9 @@
+# Charger
+
+![All right, let's do this.](oredict:oc:charger)
+
+The charger is used to charge devices such as [robots](robot.md), [drones](../item/drone.md) and [tablets](../item/tablet.md). A charger has to be activated by applying a redstone signal to it. The charge speed is based on the applied redstone signal's strength, with a strength of 15 meaning a charge speed of 100%.
+
+Note that this logic can be inversed by hitting the charger with a [wrench](../item/wrench.md). In inversed mode, the charger defaults to 100% charge speed, decreasing in charge speed as the strength of the redstone signal increases. 
+
+When a [tablet](../item/tablet.md) is placed in the charger, the first [hard drive](../item/hdd1.md) is also exposed to [computers](../general/computer.md) connected to the charger, similar to how [floppies](../item/floppy.md) in [disk drives](diskDrive.md) are. This allows transferring of data between the [computer](../general/computer.md) and [tablet](../item/tablet.md).

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/disassembler.md

@@ -0,0 +1,7 @@
+# Disassembler
+
+![Build it, tear it down.](oredict:oc:disassembler)
+
+The disassembler can be used to deconstruct most items in OpenComputers into their original parts. This is mostly useful to reclaim materials from old parts that are no longer useful, or to deconstruct devices that are either no longer needed or were incorrectly built (e.g. [robots](robot.md) without an [operating system](../general/openOS.md)).
+
+Disassembling items takes a long time, and some energy. There is also a slight chance of losing a component (which is applied on a component by component basis). 

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/diskdrive.md

@@ -0,0 +1,9 @@
+# Disk Drive
+
+![Going round and round and...](oredict:oc:diskDrive)
+
+The disk drive can be used to read [floppy disks](../item/floppy.md) using a [computer](../general/computer.md) connected to the disk drive. This is useful to get started, since the lower tier [computer cases](case1.md) do not have a built-in floppy slot, and you'll need an operating system to boot up the [computer](../general/computer.md). An [OpenOS](../general/openOS.md) disk can be crafted using an empty [floppy disk](../item/floppy.md) and a [manual](../item/manual.md).
+
+It can also be installed in [robots](robot.md) to allow inserting [floppy disks](../item/floppy.md) into the [robot](robot.md). This can be very useful since the only other way to transfer data to and from a robot is using networking - for example using [network cards](../item/lanCard.md).
+
+[Disks](../item/floppy.md) can be inserted and removed without opening the disk drive's GUI by sneak-activating the disk drive (shift-right click) with the [floppy disk](../item/floppy.md) in hand.

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/geolyzer.md

@@ -0,0 +1,7 @@
+# Geolyzer
+
+![It rocks.](oredict:oc:geolyzer)
+
+The geolyzer can be used by [computers](../general/computer.md) to scan the terrain surrounding the geolyzer for the blocks' approximate hardness. This can be useful to generate maps of the area to display on [hologram projectors](hologram1.md) as well as to detect potentially valuable blocks (ores are usually harder than dirt and stone). Geolyzer scan results have a certain amount of noise added; in theory, multiple scans can be performed to determine a more accurate reading of a block's hardness level.
+
+The geolyzer can also be installed in [robots](robot.md) and [tablets](../item/tablet.md) as an upgrade to allow them to scan their surroundings. Performing a scan will consume some energy, though, so using it excessively will drain the device's batteries.

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/hologram1.md

@@ -0,0 +1,7 @@
+# Hologram Projector
+
+![Is this the real life? Is this just fantasy?](oredict:oc:hologram1)
+
+The hologram projector is a volumetric display, i.e. it provides a three dimensional array of voxels that can be individually enabled or disabled by a connected [computer](../general/computer.md). The second tier projector, while having the same resolution as the tier 1 projector, supports displaying the individual voxels in three different user-definable colors.
+
+Holograms can be rotated along their vertical axis by hitting them with a [wrench](../item/wrench.md) on their top or bottom. This can save some effort, so that the output doesn't have to be transformed on the software side. Holograms can also be scaled up or down as desired. 

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/hologram2.md

@@ -0,0 +1 @@
+#REDIRECT hologram1.md

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/index.md

@@ -0,0 +1,48 @@
+# Blocks
+
+This index lists all of the documented blocks in OpenComputers. If you're looking for an item, check out the [item index](../item/index.md) instead.
+
+Keep in mind that some of these may not be available, depending on the recipe set used.
+
+## Computers
+* [Computer Case](case1.md)
+* [Microcontroller](microcontroller.md)
+* [Rack](rack.md)
+* [Robot](robot.md)
+
+## Components
+
+### Input / Output
+* [Hologram Projector](hologram1.md)
+* [Keyboard](keyboard.md)
+* [Screen](screen1.md)
+
+### Storage
+* [Disk Drive](diskdrive.md)
+* [RAID](raid.md)
+
+### Extensions
+* [Adapter](adapter.md)
+* [Geolyzer](geolyzer.md)
+* [Motion Sensor](motionsensor.md)
+* [Redstone I/O](redstone.md)
+* [Transposer](transposer.md)
+* [Waypoint](waypoint.md)
+
+## Assembly / Printing
+* [3D Print](print.md)
+* [3D Printer](printer.md)
+* [Assembler](assembler.md)
+* [Block of Chamelium](chameliumblock.md)
+* [Disassembler](disassembler.md)
+
+## Networking
+* [Cable](cable.md)
+* [Net Splitter](netsplitter.md)
+* [Relay](relay.md)
+
+## Power management
+* [Capacitor](capacitor.md)
+* [Charger](charger.md)
+* [Power Converter](powerconverter.md)
+* [Power Distributor](powerdistributor.md)

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/keyboard.md

@@ -0,0 +1,7 @@
+# Keyboard
+
+![QWERTY](oredict:oc:keyboard)
+
+A keyboard is needed to type text on [screens](screen1.md), be they in the world or built into devices such as [robots](robot.md) or [tablets](../item/tablet.md).
+
+For a keyboard to work with a [screen](screen1.md) in the world, it has to be placed next to the [screen](screen1.md), facing that [screen](screen1.md), or placed directly on the [screen](screen1.md) (on top or on one of its sides). You can tell that a keyboard is "connected" to a [screen](screen1.md) if the [screen's](screen1.md) GUI opens up when using the keyboard.

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/microcontroller.md

@@ -0,0 +1,7 @@
+# Microcontroller
+
+![Don't belittle it.](block:OpenComputers:microcontroller)
+
+Microcontrollers are built using a [microcontroller case](../item/microcontrollerCase1.md) in the [assembler](assembler.md). They have less functionality compared to [computers](../general/computer.md), but are cheaper to build. In particular, they *can not* interact with external components.
+
+Microcontrollers can take various components, such as [CPUs](../item/cpu1.md), [memory (RAM)](../item/ram1.md), and Expansion cards. Microcontrollers are unable to contain a [hard disk drive](../item/hdd1.md), but do contain a slot for an [EEPROM](../item/eeprom.md), which can be programmed for very specific tasks. They have an advantage over [computer cases](case1.md), in that they can also make use of some upgrades, such as the [piston upgrade](../item/pistonUpgrade.md).

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/motionsensor.md

@@ -0,0 +1,7 @@
+# Motion Sensor
+
+![Don't. Blink.](oredict:oc:motionSensor)
+
+The motion sensor allows [computers](../general/computer.md) to detect movement of living entities. If an entity moves faster than a set threshold, a signal will be injected into [computers](../general/computer.md) connected to the motion sensor. The threshold can be configured using the component API that the motion sensor exposes to connected computers.
+
+Movement is only detected if it happens within a radius of eight blocks around the motion sensor, and if there is a direct line of sight from the block to the entity that moved.

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/netsplitter.md

@@ -0,0 +1,7 @@
+# Net Splitter
+
+![*.net *.split](oredict:oc:netSplitter)
+
+The net splitter is a device that allows controlling connectivity between subnetworks. Unlike the [relay](relay.md) or [power converter](powerConverter.md) it directly connects adjacent subnetworks, i.e. components can be accessed. Each side's connectivity can be toggled using a wrench (e.g. the [scrench](../item/wrench.md)). When a redstone signal is applied to the net splitter, all sides' connectivity is inverted.
+
+This block can therefore be used to toggle connectivity to certain parts of a component network. Use a [redstone I/O block](redstone.md) or [redstone cards](../item/redstoneCard1.md) to automate the net splitter.

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/powerconverter.md

@@ -0,0 +1,5 @@
+# Power Converter
+
+![One of us? One of us!](oredict:oc:powerConverter)
+
+The power converter serves as the fastest way to convert energy from other mods' power systems to OpenComputers' internal energy. If you only run a simple computer, you probably won't need a converter. If you have a large capacitor bank that you only drain every now and then, you probably won't need one, either. However, if you wish to directly power an [assembler](assembler.md) or [charger](charger.md), it is usually a good idea to use a converter instead of directly connecting them to external power.

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/powerdistributor.md

@@ -0,0 +1,5 @@
+# Power Distributor
+
+![Power to the masses.](oredict:oc:powerDistributor)
+
+The power distributor distributes a shared power storage (such as a [capacitor](capacitor.md)), allowing several subnetworks to share their energy without components being exposed to computers in other networks. It operates by regularly "balancing" the energy in all subnetworks it is connected to, so that the *relative* amount of energy is the same in them. 

projects/1.12.2/assets/opencomputers/opencomputers/doc/en_us/block/print.md

@@ -0,0 +1,11 @@
+# 3D Print
+
+![Any way you want me.](block:OpenComputers:print)
+
+3D prints are created using a [3D printer](printer.md). They are primarily intended for decorative purposes, but can also be created in such a way that they react to or emit redstone signals, allowing for a little bit extra functionality.
+
+3D prints can be recycled by putting them as input into a [3D printer](printer.md). This will re-use some of the [chamelium](../item/chamelium.md) that was used to print them. Color that was used to print the model will not be recycled.
+
+Holding the key for OpenComputers' extended tooltips (default is `Shift`), a print's active state will be shown, if any.
+
+Printed blocks are also Forge MultiPart compatible. If present, multiple prints can be placed into a single block-space, unless they do not collide, and the total number of shapes in the block-space does not exceed the limit for a single model. Due to the nature of Forge MultiPart, prints can therefore also be placed into the same block-space as any other Forge MultiPart compatible block, such as torches, levers, cables or red alloy wires from Project Red, for example.