-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] <error when breaking a block> #1400
Comments
unable to reproduce this on Paper 1.20.4 This bug was fixed in 1.175.0 from 1.174.0 so not sure @MonG3n |
I managed to produce it again! Is it possible that it's just my item's configuration that's wrong? |
@MonG3n as mentioned please use codeblocks or take a screenshot, ur config isnt readable here As mentioned please ensure that this is on 1.175.0 and use a Paper not Purpur server and see |
I mess something up, is that why it's not good for me? Or what is the reason? |
@MonG3n i am not sure i cannot replicate this |
yeah sadly i am out of ideas not too sure how to further approach this sadly |
I have checked...
Description
When I try to knock out an oraxen custom block, the console keeps sending warnings and won't let me knock out the object, only in creative mode.
Steps to reproduce
When I click on an oraxen custom block it sends a warning. If I start hitting a custom oraxen block it will spam without stopping.
Plugin Version
[17:54:26 INFO]: Oraxen version 1.175.0
ProtocolLib Version
ProtocolLib version 5.2.1-SNAPSHOT-689
Server Software & Version
[17:55:23 INFO]: Current: git-Purpur-2176 (MC: 1.20.4)*
How breaking is the bug?
Non-breaking Bug - Plugin still usable, but certain features unavailable
The text was updated successfully, but these errors were encountered: