Tsuser1 / Modern-LWC

Welcome to the future of LWC, get ready to get back into this classic plugin!
MIT License
29 stars 14 forks source link

pistons can remove some protections #88

Closed seema84 closed 5 years ago

seema84 commented 5 years ago

Version: 2.1.3-dev-e9744bb

pistons can move protected doors,trapdoors, fance gates (and maybe more)

pop4959 commented 5 years ago

Unable to replicate the issue. Do you have hopper protection disabled in the config? If not, please post it here via a hastebin.

seema84 commented 5 years ago

protections: denyHoppers: false

pop4959 commented 5 years ago

Full config please. Use a service like pastebin. If you do not wish to share it publicly, please join the discord and send it to us in a private message.

pop4959 commented 5 years ago

Again unable to replicate the issue, using the config file sent via Discord (changing only the login credentials). Perhaps this is a plugin conflict. Have you tried testing whether this occurs on a clean server, with only LWC installed?

seema84 commented 5 years ago

Thats not a config issue. On a fresh Server with only Modern LWC (and a fresh config) its the same problem.

pop4959 commented 5 years ago

What kind of server are you running this on? Also, a video may help. No luck replicating this whatsoever. Can't fix something until the source of the problem is known.

seema84 commented 5 years ago

Paper version git-Paper-492 (MC: 1.13.2)

pop4959 commented 5 years ago

Ok finally confirmed (after discussing this with you on Discord). You left out some important details in this issue about how to cause this to occur. Now I see, but in the future please give a more thorough report. I will try to fix this soon.

seema84 commented 5 years ago

If you had tested all the possibilities (with pistons), you would have found it.

pop4959 commented 5 years ago

This should be fixed now in the latest development build.

In response to your last comment though, please actually make a proper report next time, by filling out the issue template. I spent a lot more time than I needed to because you did not describe the problem clearly. Many people report issues that are non-existent (caused by their server / other plugins), and if this were one of those cases I would not ever have found the bug regardless of the amount of testing. It is important that you give enough information. Please bear that in mind next time. Thanks!

Closing now