Pale Oak Logs Unstrippable
Before I start binary searching this, anyone experience this bug or have any ideas? (I've attached a video as well)
23 Replies
Thanks for asking your question!
Make sure to provide as much helpful information as possible such as logs/what you tried and what your exact issue is
Make sure to mark solved when issue is solved!!!
/close
!close
!solved
!answered
Requested by ibotmealot#0
You’re in vanish
happens outside of vanish as well, it was reported to me by a player
as suggested in syscraft, Athena would let you find it without the "long" process of binary searching
thats nice
one of the most painful things is figuring out wtf is touching the events
yeah trying that now
any idea what the event would be, tried using PlayerInteractEvent as suggested but it didn't seem to pickup anything
also thought I should add the other wood types DO work, just not the pale oak
what version is the server and what version is the client
both 1.21.4
latest purpur build and I'm on fabric, but I've had other people have the same issue
it is playerinteractevent
make a fresh server, using the same server jar with no plugins,
try to strip the wood
if it works, we atleast know its definitly a plugin thats doing it
tho it might be worth checking geyser and viaversion
just with them protocol hacking, they might be preventing it to stop a crash of some form
make sure they are both on the latest version of each
just made a new server, same plugins & datapacks and it works
:pain:
now that is weird
dumb question, on the new server are you opped?
!close
Closed post!
Your post has been marked as solved!
Requested by ibotmealot#0
It was purpur's fault, they have a strippables section in their config and since I'm using a config from 1.21.3 my main server didn't have the pale oak logs in this section
how did you find this out?
genuinely curious what made you check the purpur config
didnt even know purpur had this as a configurable thing
I changed all my server config files (bukkit.yml, purpur.yml, paper configs, etc) and the issue occured on the test server again. Then deleted the plugins to make sure it wasn't that and narrowed it down to server configs. Then I just went thru and tried with a brand new spigot.yml and purpur.yml file (and not my configured ones), and it worked. So then just searched in the purpur discord and other people have had that issue.
im glad you found the issue and was able to fix it