Hey I have an issue with the plugin. So, players with the permissions needed to use /openinv can open their own inventory and duplicate their items by putting them in their inventory and hitting the escape key really quickly. I tried it myself and got a stack of diamond blocks out of one diamond block.
Hey I have an issue with the plugin. So, players with the permissions needed to use /openinv can open their own inventory and duplicate their items by putting them in their inventory and hitting the escape key really quickly. I tried it myself and got a stack of diamond blocks out of one diamond block.
No, I was in survival. However, it seems to just be a bug caused by one of
my custom plugins. Sorry for the trouble!
On Sun, May 20, 2018 at 4:42 PM, Adam <notifications@github.com> wrote:
> Still awaiting replication information. You weren't in creative, were you?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/lishid/OpenInv/issues/84#issuecomment-390510909>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AkjxqM_Y6dkqcXVb994lfO2O4bjD4OTiks5t0dUxgaJpZM4UFcAj>
> .
>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hey I have an issue with the plugin. So, players with the permissions needed to use /openinv can open their own inventory and duplicate their items by putting them in their inventory and hitting the escape key really quickly. I tried it myself and got a stack of diamond blocks out of one diamond block.
Can't reproduce. Server version/OpenInv version?
The perm
OpenInv.openselfexists, so you can use that as a bandaid.Ah, thank you! I couldn't find that :D
Still awaiting replication information. You weren't in creative, were you?
No, I was in survival. However, it seems to just be a bug caused by one of
my custom plugins. Sorry for the trouble!
On Sun, May 20, 2018 at 4:42 PM, Adam notifications@github.com wrote:
Ah, okay, thanks. I know there used to be a couple bugs related to it, but I was fairly sure they'd all been ironed out.