Redstone IO peripheral block.

A block that connects to a wired network and allows its sides to be set to redstone output or read input as a computer can already. This block could be considerer an IO expander and would allow for more complex interaction between computers and redstone. Examples of usage would include multi story buildings lighting controlled grid being controlled from one computer or advanced MIDI note block set ups.

Thank you for your consideration.
Nalfar

I suppose if you specifically wanted to use a peripheral for this - as opposed to just sticking another computer in your network, which, as you point out, would already do the job just fine - you could use this one.

Bomb Bloke, on 05 April 2014 - 01:49 AM said:

I suppose if you specifically wanted to use a peripheral for this - as opposed to just sticking another computer in your network, which, as you point out, would already do the job just fine - you could use this one.

Thanks for your suggestion I will look into that mod. Using a full blown computer just to flick a on off switch is a bit over kill and adds another security vulnerability to a network. peripherals are more secure as they have no terminal interface that a user can manipulate. they cant right click it.

if i have 16x16 note blocks powered by its won computer the computational overhead caused by running many simultaneously will also become an isue. thanks dan for the optimizations btw they are making a big difference and are appreciated by us low spec users.

Hmm. Are you familiar with the "bundled" functions available in the redstone API? If not, they're well worth looking into, as they allow one system to potentially handle 6x16 redstone signals without need of other peripherals.

It's also worth pointing out that ComputerCraft computers (and by extension turtles) don't run "simultaniously". Instead, there's one Lua VM, which switches between each device running in your world and runs their code until they pause (at which time it switches to the next, runs only that systems code until it pauses, and so on). This is why if a device doesn't yield within ten seconds of its last pause it'll crash - because allowing it to continue indefinitely would literally lock up every system in the world.