Closed HydrolienF closed 5 months ago
Hello @HydrolienF,
Thank you for reaching out! This indeed seems like an issue where I am trying to access the state of an entity, that is not on the same region thread!
I will take a look at this somewhere this week, and hopefully push out an update soon! If the console errors are bothering you, or if the feature is currently not working whatsoever, you could set ignore-wolves-enabled
to false
to prevent it from trying to execute the filter checks that result in the console errors.
Kind regards, Bram
Hi @HydrolienF ,
I wanted to inform you that I've just implemented a fix that addresses the issue you have been experiencing. Could you please take a moment to download the latest snapshot from the link below and let me know if it resolves the problem on your end as well? Based on your feedback, I will proceed with creating a new release later this week. Thank you for your help!
You can access the latest snapshot here: AntiHealthIndicator v1.1.3-SNAPSHOT
Looking forward to hearing from you soon!
Kind regards,
Bram
It fixed it ! Thanks
By the way, having gradle isn't needed to "Compiling Jar From Source".
You can run ./gradlew build
instead of gradle build
and the Gradle wrapper will download gradle if needed. (./gradlew build
for Linux, MacOS and Powershell. And .\gradlew build
for default Windows terminal)
By the way, having gradle isn't needed to "Compiling Jar From Source". You can run
./gradlew build
instead ofgradle build
and the Gradle wrapper will download gradle if needed.
Hey, thanks for letting me know! I'll give this a shot later today, and otherwise remove Gradle from the requirements!
Thanks you for resolving it that quickly !
Hi, I'm using this plugin on a Folia server and I get an exception. I don't know if it happend only with wolf or not. It might be because isTamed try to access to a player even if player is not in the same region.