// the find
MikaylaFischler/cc-mek-scada
Configurable ComputerCraft SCADA system for multi-reactor control of Mekanism fission reactors with a GUI, automatic safety features, waste processing control, and more! Please be sure to take a look at the Wiki tab, this project has lots of docs!
A full SCADA implementation in Lua for controlling Mekanism fission reactors inside Minecraft via CC: Tweaked. It mirrors real industrial control system architecture — PLCs, RTUs, supervisory computers, a coordinator HMI — all running on in-game ComputerCraft computers. The audience is Minecraft modpack players who want automated, safety-interlocked nuclear power rather than just toggling reactors by hand.
The architecture is genuinely faithful to real SCADA concepts: separate PLC, RTU, supervisor, and coordinator roles with defined communication boundaries, not just one script doing everything. HMAC message authentication via a bundled pure-Lua crypto library (lua-lockbox) is a real security feature for an in-game network, and the configurable transmission range limit adds another layer. The graphics subsystem is a proper retained-mode UI library with reusable components, indicators, controls, and theming — significantly more structured than typical ComputerCraft projects. Separate versioned components with their own release badges and a custom installer (ccmsi.lua) means users can update individual pieces without reinstalling everything.
The project is explicitly closed to contributions until out of beta, which limits the community's ability to fix bugs or add hardware support — a real constraint for a Minecraft mod project where the upstream (Mekanism) keeps changing. The bundled lockbox crypto library is vendored with no apparent pinning or update mechanism, so security fixes upstream won't flow in automatically. Testing coverage is thin: a handful of manual test scripts with no automated test runner, which matters for safety-critical logic like the reactor emergency shutdown conditions. The modbus implementation is described as 'vaguely-modbus,' meaning it won't interoperate with anything outside this project and the protocol divergence isn't documented.