BloodyRum

Great job! This system seems amazing.. Although I was rather disappointed it doesn't only use in-game Lua, thats understandable. Keep working on great things.

Can you show us the error?

.suckFromSlot is a feature of the Inventory Controller, you need one in your robot to use it local component = require "component" local controller = component.inventory_controller controller.suckFromSlot(1, 5, 1)

Thank you! Now one more question. To refer to the inventory controller by address I would replace "component.inventory_controller" with "component.Address" ?

Anyone knows how to do this? Heres the code I tried component = require("component") barrel = component.mcp_mobius_betterbarrel stack = barrel.getInventorySize() --I have an inventory Controller in the adapter print(stack) And the Error I get when I try to run it /BarrelTest:3: attempt to call field 'getInventorySize' (a nil value) stack traceback: /BarrelTest:3: in main chunk (...tail calls...)

I would love to see this added. Experienced coder you say? Here is a project for you. To make a supercomputer that has 1-2 "nodes" of full servers. Then write an API so the nodes act like namespaces. And the API would shift the variables around using the network. The think is the code has to know when to grab a variable and when to send one. 100 Brownie points if you can make an API for this along with an example program.

The best thing for you to do Is to convert it yourself one line at a time. That will allow you to gain more OpenComputers knowledge yourself, And when you do find something you 100% cant figure out without help is went you should ask around on irc. If you really don't want to convert it yourself then just install cc and use that.

I do belive this is a great idea! But what if the person making the robot decides to be "smart" and make a 1x1x1 Robot that is unrealistic? How will it render tools? How will it render parts that it has installed? Besides a couple flaws this idea would be great to add. (With drones this might not be a good idea at all, because they are entities)

Thats because the computer then switches to a different screen. So lets say screen #1 is the screen you want to use. When you boot the computer it chooses a random screen to use. Then after it gets past "Initializing components" it picks a new screen called screen #2 or something else. When you break the cable the computer sees that it only has on screen to use so it gos back to that one. In order to have it work correctly on the screen you have to force the computer to bind to screen #1.

The Robot cant interact with "external devices" so your best bet with Opencomputers would be have one or two computers that read the Redstone signal then send it over a wireless network card then received by the Robot.

bind(address: string): boolean[, string] Tries to bind the GPU to a screen with the specified address. Returns true on success, false and an error message on failure. A GPU can only be bound to one screen at a time. All operations on it will work on the bound screen. If you wish to control multiple screens at once, you'll need to put more than one graphics card into your computer. That was taking right from the wiki. Type that into a lua prompt or make an autorun command for it.

OC Only has one type of cable available. In real life there is different cable types and uses. My Ideas are. Cheap Cable Transports power at lower rate. (Like IC2s copper or tin cable) Sends messages at about 1 Block per Tick Gold Cable Transports power at a high rate. Sends messages at about 2 Blocks per Tick Fiber Cable Transports no power. Sends messages instantly like current cables. To work around have slow screen update speeds from slow cable make putting the blocks together act like fiber Cable. Or have Cable like CAT5e or CAT6 or even some scuzzy cables

Im guessing that you did not make this yourself? If you just need a simple program to make it go on when power is low and off when power is high (It does not waste Yellorite) then I have a program for you. (Also smaller so with some studying it might help you get a better grip on lua.) As for the error, I need to get a copy of the error, and its easier to make your own program most of the time. Thats why I made mine.

Thank you. Now it looks like something a ten year old can do. (Not joking nor being Sarcastic) But it should be easily done with something like 1. Make special X Block and put EEPROM Into it 2. Enter something like "edit (EEPROM Add)" 3. Enter code then remove EEPROM With Arduino the coding is "simple" much like OpenComputers. Snippet of Arduino code int hour11 = 1; int hour21 = 2; int hour22 = 3; int hour23 = 4; int hour24 = 5; int minute11 = 6; int minute12 = 7; int minute13 = 8; int minute21 = 9; int minute22 = 10; int minute23 = 11; int minute24 = 12; int hour1 = 0; in

I did not mean Microcontrollers are harder then they should I mean programming the EEPROM is too hard. In real life Microcontrollers are easy (At least for me besides the pesky soldering) to use and upload info too. When I decide to write a code for Arduino I just plug it in using a simple USB cable then open the programming application for it and write. As for what Kevink525 Said That "Reading of course is kind of impossible." its not. I mean it "kind" of is but with some good logic and some setup you can find the code or reverse engineer it. Writing to the EEPROM should be easy but Readi

That seams more difficult then it should be. Is there any plans to make it act like a floppy in a block that reads it?

Simple how do I program the EEPROM to use in the Microcontrollers. Also any advice for using a Microcontroller in Minecraft?

I'm trying to get a little program set up to out the cords of the screen pixels when I click them. I looked around but still could not find one. One that I did find on Open-computers forum did not work. Here is my code. function touchsig(_, x, y, _, _) print("Xcord: " .. x .. "Ycord: " .. y) end while true do event.listen("touch", touchsig) end Whenever I run it I get. /cords:5: attempt to index global 'event' (a nil value) stack traceback:\ /cords:5: in main chunk (...tail calls...) Any Ideas on how to fix this? Also off topic but I'm doing this because I want to