[WARNING] Plugin caused dupe glitch (NoLagg + ShowcaseStandalone)

Discussion in 'Bukkit Discussion' started by foldagerdk, Jun 19, 2012.

Thread Status:
Not open for further replies.
  1. Offline


    Plugin caused duplication glitch:

    Using both NoLagg and ShowcaseStandalone at once, can be a dangerous thing to do.
    Here's why:

    If two showcases of the same item is too close to each other, NoLagg will try to stack these, to cause less lag. However, this opens up for a duplication glitch. Usually ShowcaseStandalone prevents people from picking up the items, but when NoLagg is added, these items that are showcased will get stacked on one of the showcase areas. The one with no items will keep trying to add an item to it, which will be moved automatically to the area where it stacks. When there is more than one item, a player can toss a diamond to a diamond stack, and the protected diamonds will lose their protection. Therefore, a player can just pick these up, and walk away.
    This might also be possible if the player just tosses an item of the same kind as the showcase, to a single showcase.
  2. Offline


    Hmmm, thanks for the warning. I think i will be turning off NoLagg for a moment, i wasn't very happy with the plugin either so. Thanks!
  3. Offline


    No problem :)
  4. Offline


    I'm going to assume you notified the owners of those plugins before just posting it on the open forum...
  5. Offline


    Well just change the stacking radius to .5 untill you submit a real ticket to the coder of NoLagg.
  6. Offline


    Looks like a cool glitch! *finds server which uses both*
  7. Offline


    pretty much
  8. Offline


    Wasn't online for a while, but it is a bit weird that this happens. BKCommonLib keeps track of:
    • BleedingMobs
    • Showcase
    • ShowcaseStandalone
    To ignore certain items during item stacking, buffering and limiting. I have no idea why it fails to cancel out ShowcaseStandalone now...no warnings in the log about 'failed to verify item and has been disabled'?
Thread Status:
Not open for further replies.

Share This Page