Forums

i'm currecly useing CC becuse of the fact that the speed of witch lua commands is run is based on a speed factor in the processor item limiting the update speed of a program OC is better that CC in all otherways then this, CC does not limit speed (not on purpes anyway) nor does it limit the amout of RAM a spesific computer can use (allso CC have made too much of an effort optimiseing the mod for servers makeing CC look like a simplyfired version of OC - witch i supose it is)   anyway of removieing (i know that ain't going to happen) the limit or at least let the computers run faster?

The Guard - security system The Guard is a base security control program I've written in 2016. It allows you to use some of the security devices from the OpenSecurity mod. It has modular architecture - all features are implemented in independent modules that can be replaced. It has action-driven - you can specify how everything behaves using the action system. Features modular architecture action-driven configurable behavior redstone support (Redstone I/O blocks) support of security devices from OpenComputes: keypads biometric readers RFID card readers turrets entity detectors motion sensors alarms Further reading The guard has its own wiki, on which you can find the installation instructions as well as the example configuration and other information. If somebody is interested in writing a new module, I can create a wiki page with API documentation (basic information is provided in the_guard.lua file). WIKI Disclaimer Although I have tested this program, a few issues might have slipped through. In that case feel free to report them in this thread or, even better, on the issue tracker if you have Gitlab account. If there's an error, be sure to include log contents (logs button on the right side of the program's interface) containing that error. Screenshots

Lua is single threaded. Meaning that only one chunck of code can ever run at a time. Coroutines are considered co-operative in that they yield to allow others to compute before they themselves finish. The idea is that we can do a little work we need right now and do it quickly, then yield so others can do the same, hence co-operative. Threads are fancy coroutines, but they are still limited to cooperation, so they must yield if you wish to begin another. Use term.read or io.read or os.sleep.... etc. 

Do you sleep/yeild in the while true loops?

I believe this is actually by design so that OC(particularly robots) isn't considered too 'OP'