BlockProt

BlockProt

17.2k Downloads

[Bug]: Even if it's not locked, it doesn't destroy the block.

hoehoetvhss opened this issue · 14 comments

commented

Version of BlockProt

Plugins Version: 1.0.0 Beta 2 / Server Version: git-Paper-349

Description of the bug

https://youtu.be/pV2cSgwiroc

Steps to reproduce

  1. Check that there is no lock.
  2. If there is no lock, try to destroy it.

Additional context

Also, not only the reading table but also all locked blocks are targeted.

commented

유저

The user in the video has the authority of the above picture.

commented

플러그인 목록

In addition, the plugin being used in the server can be found in the picture above.

commented

When BlockProt was removed and tried again, it was destroyed normally.

commented

Hmm seems weird. I've updated my Paper version and rebuilt the plugin but I cannot reproduce this. Is there maybe some other plugin doing this for some reason? Maybe try removing the BlockProt plugin for a short period of time and see if you can break the block then. Sorry for any inconveniences.

commented

Is there a possibility of collision with the Anti Cheat Plugin?

commented

Which anti cheat are you using? I'll try it out myself then (and other plugins you're using).

commented

I'm currently running a server with both those plugins installed and I can break anything fine. As it seems you're saying everything suddenly stopped working, did you change anything else just before it started happening?

commented

I'll try removing the plug-in that looks like it's going to crash once and reply.

commented

https://youtu.be/GFjjuLDz3pI

The video above is a video tested by installing only BlockProt

commented

Idk why this would be. It works absolutely perfectly fine for me, even with none of my other plugins installed. Maybe your build broke somehow? Just to be sure:
blockprot-spigot-1.0.0-beta.2-all.zip

Sorry about this btw.

commented

maybe its because your hardware isn't up to date, which may hinder the plugin from working on your pc

commented

My server may have a problem once, so I'll delete the server itself and try again.

commented

It is identified as a bug caused by world damage, and this does not happen when making a new server.

Thank you for helping me.