Proxy connected to powered redstone writer and an interface ~~on the same proxy causes an exception and~~ on the same network causes exception log spam. (1.12 confirmed/1.16 confirmed)
Icoza opened this issue · 1 comments
2021-06-15.07-52-40.mp4
Edit: I wasn't able to reproduce the exception being thrown on interface placement.
Each time a proxy is placed on this setup, a single exception will be written to the log. If you are pointing a proxy to redstone dust; when you connect the redstone writer to the interface, it spams the log until the server/client crash or you're able to break a cable.
Setup: 
When redstone dust is placed where the proxy is pointing, the spam should start.
Edit: After stopping the spam by breaking the cable, if you then break the redstone writer this error will be spammed until you break another component. After breaking another component, the server/client will crash with exception in server tick loop.
Edit 2: 1.16 log requires same steps to reproduce.
