This mod adds only 2 blocks to the game. One monitors whatever it's facing, the other can output redstone signals or change filters on create machines.

Usage

Windows curl is NOT the same as MacOS and Linux curl. Use WSL if you're testing on windows

for the blue block (the monitor), you can get a JSON output of whatever it's monitoring like this curl http://<IP>:<port|27100>/<ID>

or if it's password protected curl http://<IP>:<port|27100>/<ID>?password=<password>

This supports most mod's blocks that have NBT as well as FE electrics.

for the red one (the output), you can set a redstone signal, pulse, or set create filters.

set redstone strength curl -X POST http://<IP>:<port|27100>/<ID> -d '{"redstone":<0-15>}'

pulse the block … -d '{"pulse":}''

set a create machine's filter … -d '{"filter":""}'

or multiple (must have a create filter in the filter slot) ... -d '{"filter":["item ID 1","item ID 2"...]}'

clear filter ... -d '{"clearFilter":true}'

Considerations:

• The mod is pretty much useless in a singleplayer world
• A dedicated server with a chunkloading mod is recommended
• for access outside of your LAN, consider using a mesh VPN, such as Tailscale, or port forwarding. For public servers hosted at your home, use IP shielding local to you
• while the attack surface on the hosting hardware should (in principal, I won't leave the possibility out) be very limited. There can be in-game infrastructure attacks if you leave your websocket outputs without a password and the ID gets leaked, if both get leaked, or if whatever interface you made is publicly accessible and someone fools with it. Guard the interface with Tailscale over using port forwarding.
• attack surface can increase if the HTTP actuator is used for an Open Computer, especially when they fix the internet card on dedicated servers. Treat those like you would Government infrastructure and make sure no one in game can read the NBT off the actuator after it's set.
• at current, the CC: Tweaked <-> OC2 bridge is rather experimental.