This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
>What steps will reproduce the problem?1.Have both Variabletriggers and Nolagg.2.In VT, create a trigger that makes a redstone torch disappear.3.Check the circuit to see if it turned off because of the torch's disappearance.
>What is the expected output? What do you see instead?The pistons are supposed to turn off and so on, but the wires stay lit instead, with no power source.
>What version of the product are you using?Latest 1.6.2 release
>Do you have an error log of what happened?No error was shown. It seems legitimate, as mechanics are not logged.
>Please provide any additional information below.I believe it started happening when i got your plugin. Maybe some redstone buffering component of yours?
<p>Here is a screenshot of the logic breaking.</p>
I honestly don't know what could go wrong here, all I can say is that it MIGHT be the chunks component, as that gets the closest to touching the transmission of block information to clients. It doesn't affect physics though, which is what confuses me here.
To post a comment, please login or register a new account.