Buscript failed to load!
S4IVin opened this issue · 7 comments
Information
-
Server version: This server is running Yatopia version git-Yatopia-"aaeb472" (MC: 1.16.4) (Implementing API version 1.16.4-R0.1-SNAPSHOT)
-
Full output of
/mv version -p: https://paste.gg/p/anonymous/58a6f2164733478e95d1317d40fc7aa6 -
Server log:
Description
Simply when I start the server I get this warn: [12:12:35 WARN]: [Multiverse-Core] Buscript failed to load! The script command will be disabled!
Steps to reproduce
- Start the server
It isn't an error OR a warning OR even Informational if Buscript isn't on the server so can't you just mute the warning unless Buscript exists????
Also when I start the server I also noticed another warn:
[12:12:33 WARN]: [Multiverse-Core]" Multiverse-Core v4.2.2-b812 "has registered a listener for org.bukkit.event.entity.EntityCreatePortalEvent on method" public void com.onarandombox.MultiverseCore. listeners.MVPortalListener.entityPortalCreate (org.bukkit.event.entity.EntityCreatePortalEvent) ", but the event is Deprecated. "Server performance will be affected"; please notify the authors [dumptruckman, Rigby, fernferret, lithium3141, main -].
Either due to using java 15 or a plugin conflict. Things you can try is with only mv plugins installed and also use paper instead of Yatopia. But honestly, if you don't use Buscript which most ppl don't, you can just ignore.
Same thing for your second issue. You can ignore it. #2000
Either due to using java 15 or a plugin conflict. Things you can try is with only mv plugins installed and also use paper instead of Yatopia. But honestly, if you don't use Buscript which most ppl don't, you can just ignore.
Same thing for your second issue. You can ignore it. #2000
Ok!
I don't use buscript either, but I thought I'd confirm this too. The warning still appears on Java 16 (I'm migrating to it, in preparation for MC 1.17), latest version everything, Paper.
If it just a log line without a stack trace of long error it’s fine. Buscript doesn’t work on java 16 so we just gracefully disable it for now.
