Troubleshooting
Common problems and solutions.
Conflicting Imports
By default, Kite auto-imports majority of Bukkit, Paper and Adventure APIs. This can ocassionaly cause type conflics, e.g. when function expects org.bukkit.Sound and net.kyori.adventure.sound.Sound was chosen by the compiler. You can fix it in a number of different ways but easiest one is to add an explicit import:
import net.kyori.adventure.sound.Sound
val sound = Sound.sound(Key.key("minecraft:entity.shulker.shoot"), Sound.Source.BLOCK, 1.0F, 1.0F)Other way around is to use a fully qualified import.
val sound = net.kyori.adventure.sound.Sound.Sound.sound(Key.key("minecraft:entity.shulker.shoot"), net.kyori.adventure.sound.Sound.Sound.Source.BLOCK, 1.0F, 1.0F)Also don’t be afraid to use Kotlin’s as and typealias keywords.
import net.kyori.adventure.sound.Sound as AdventureSound
typealias SoundSource = net.kyori.adventure.sound.Sound.Source
val sound = AdventureSound.sound("minecraft:entity.shulker.shoot", SoundSource.BLOCK, 1.0F, 1.0F)External Libraries
Dynamic library resolver - either via @file:Repository and @file:Dependency annotations or libraries.json configuration file - will be added in a future Kite release.
Unresolved References
Certain forks introduce breaking changes to class loading and/or runtime isolation. This usually cause all scripts to fail compilation due to unresolved reference errors. We provide an experimental workaround for this problem but it is not guaranteed to work in all cases.
This issue is not present in Paper itself or in any popular fork such as Folia, Purpur or Pufferfish.
By adding following flag to JVM arguments, Kite will try to explicitly add server .jar to the compilation classpath.
-Dkite.compat.dynamic-server-jar=trueLocation of the file is determined by looking up some known class and checking it’s source.
In case you’re still experiencing issues, don’t hesitate to let us know.
https://github.com/EchoNineLabs/Kite/issues/new