This plugin messes up another one... #244


  • New
  • Defect
Open
Assigned to _ForgeUser7105870
  • Pixelmod created this issue Aug 21, 2013

    >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?

  • Pixelmod added the tags New Defect Aug 21, 2013
  • Pixelmod added an attachment Redstone_erratum.png Aug 21, 2013

    Redstone_erratum.png

    <p>Here is a screenshot of the logic breaking.</p>

  • _ForgeUser7105870 posted a comment Jan 1, 2014

    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.