Sangar

From what I can tell, the lack of os.sleep/event.pull in the while loop is the difference. Event listeners are triggered from within event.pull (which is what os.sleep calls).

OpenComputers Version 1.5.3 is now available. Bugfix galore. As always, remember to make a backup of your world before updating. Download on Curse. Added: Allow getting array with input / output for all colors for bundled redstone. Fixed: Initial color value for cables when placed as multiparts. Fixed: Potential NPE in robot update logic. Fixed: Potential NPE in item cost computation. Fixed: Potential NPE in directory listing. Fixed: LuaJ fallback. Fixed: Screens potentially preventing chunks to unload. Fixed: Sound handler potentially leaking memory. Fixed: Angel upgrade. Edit: Oh, al

Welp, that's a bug. I'm afraid I saw this just after pushing the 1.5.3 release, so you'll have to grab the latest build from Jenkins for the fix.

Not much to add to what has already been said, just to make it a bit clearer via an analogy: you're basically complaining that the Fusion Reactor is too complicated to build after jumping into ReactorCraft and having no experience with RotaryCraft whatsoever ;-) While the wiki tends to be slightly out of date, it's not remotely as bad as you make it out to be. EEPROMs are simply a relatively recent addition to the mod, so there's not much on it in the wiki yet. The wiki also relies on people actually adding info to it; I'm afraid I simply don't have the time and endurance to develop the mod *

Ah, another link in hiding, thanks. Updated.

Hint: have the page in the NEI item list with the OC items open when you're in the assembler GUI, it'll highlight whatever item fits into the slot hovered by your cursor. So if you hover an upgrade slot it'll highlight all upgrades that can go into that slot. And yeah, Minecraft logic. Who'd have thought a stack of chests would fit inside a chest

You can already color cables, just like you can dye cases and screens: simply use a dye on the block.

The signal will only be queued if there are any components that actually populate the table with information, so for now when you have a geolyzer or nav upgrade built into your tablet. When that's the case, hold right-click while targeting the block until you hear the beep, that's when the signal is queued.

Run `ls /bin` to get a list of programs shipped with OpenOS. You might also want to check out MaximilianVINCENT's tutorial on that topic.

OpenComputers Version 1.5.1 is now available. Mostly bugfixes, some improvements. As always, remember to make a backup of your world before updating. Download on Curse. Added: Allow swapping EEPROM in MCU by shift-rightclicking the block with the EEPROM to insert in hand. Added: Man file for rc script system (Magik6k). Changed [MC1.7.10]: Backported change to robot movement / execution logic so that it runs in a tick handler instead of the tile entity's update method. Changed: Improved rc script system (Magik6k). Fixed [MC1.7.10]: Broken flight height computation. Fixed [MC1.7.10]: Robo

Why? You should never need the actual numeric ID. You can get it, though, if you set debug.insertIdsInConverters=true in the config.

function lib.fun1() { print("It worked!") } That's not valid Lua. So it'll fail loading the library - you can use local lib, reason = require("libname") if not lib then print(reason) return end To print the error and "soft fail", or local lib = assert(require("libname")) to generate an error if the lib fails to load. You may need to reboot when changing the library or manually unload it (package.loaded["libname"] = nil) or the system will re-use a cached version.

You'll need a tier two redstone card in the computer, then you can use component.redstone.setWirelessFrequency to set the frequency the card should operate on - it can only operate on one frequency at a time. To send a signal to the set frequency you can then use component.redstone.setWirelessOutput(true). To read the value for the current frequency, use component.redstone.getWirelessInput().

To access multiple components of the same type, you'll need to get the proxy for the components mannually, since there can only be one primary component after all. To do that, either use component.proxy(address) with manually providing the addresses or use component.list("note_block") to iterate the list of connected components, e.g. for address in component.list("note_block") do local proxy = component.proxy(address) proxy.trigger() -- or whatever else you want to do with the component end

Mostly bugfixes since the beta. Changelog copied for convenience, because you really should read it. Really. READ THE CHANGE LOG! As always, remember to make a backup of your world before updating. Download on Curse. This update contains some major changes, so be sure to read the change log. Also, due to these changes, this version may have some neat new bugs hidden in it, in particular in the way robots' and drones' inventories work and how they interact with the world. Added: eeprom.getData/setData for storing a 256-sized byte array. Changed: Microcontrollers are now fully sided, i.e.

The timer list is a local variable, it's not in the table returned by require("event"), so that won't work. In general this isn't trivial, because a number of libraries depend on the event library to work (such as for keeping a primary component to name one). The best bet would probably wrapping your actual program code in a pcall and clear up any timers / event listeners after that returns. I.e. function main(...) -- Your actual code. end pcall(main, ...) -- Clean up timers, listeners, ...

Have a look at http://ocdoc.cil.li/tutorial:custom_oses

Time for another beta! Moreso than usual, do make a backup of your world before updating. READ THE CHANGE LOG! This update contains some major changes, so be sure to read the change log. Also, due to these changes, this version may have some neat new bugs hidden in it, in particular in the way robots' and drones' inventories work and how they interact with the world. I did a good bit of testing, but would like to get a few more eyeballs on this before I'm declaring it somewhat stable. Added: eeprom.getData/setData for storing a 256-sized byte array. Changed: Microcontrollers are now ful

The mail server moved last month, so that's probably related (IP changed).

OpenComputers 1.4.9 is now available. Just a few bug fixes. As always, remember to make a backup of your world before updating. For downloads see Curse. Fixed: Cables having a chance of not yielding output when being disassembled. Fixed: Tablet disassembly. Fixed: Tablets being charged even if there was no power. Fixed: Potential NPE in MCU tooltip.

You'll need to place a tank controller into the adapter and use that to get information about the fluid in the tank. I'm not sure without testing if the adapter would have to be next to a valve / the bottom center block or if any part of the tank will work, so you might want to try placing it at different parts of the tank, too.

OpenComputers 1.4.8 is now available. Minor maintenance. Unless something major pops up before 1.5 goes final, this will be the last 1.4 release. As always, remember to make a backup of your world before updating. For downloads see Curse. Added: yes.lua program to OpenOS (hunator). Changed: Default power conversion values for RF. Needed adjustment after other mods now natively produce RF. Fixed: Improved block rendering a bit, should behave properly with shaders now (thanks a ton to Ivorius for pointers).

If you want to control CC turtles using OC computers you'll need a CC computer somewhere that's next to an OC switch or access point, so it can forward CC network messages to OC and vice versa. The switch will show up as a CC peripheral that simulates CC's modem API, so you can open ports, send messages and receive messages as events.

Those are some very sexy patterned GUIs! I'd recommend http://unicode-table.com/ for getting a quick overview, though. Only then check the image lookup tables to see how it'd actually look in-game.

1. No, it used to be that, a long, long time ago. Now it uses a 6-8-5 palette. This means 240 "hardcoded" colors and 16 "palette" colors (which default to greyscale, but can be changed, just like the tier two palette). 2. No. The colors are what they are. The only values that can change are the ones in the palette, and they only will when you explicitly change them yourself. 3. When changing to indexed color mode you can define a custom color table. If you have to do this manually that'll be a pain, however there's an option to load/save tables, so maybe somewhere on the internet someo