FOMO

FOMO

Bukkit Plugins
180 Downloads

Plugin not working Paper 1.16.5

shplack opened this issue ยท 2 comments

commented 
10.05 12:03:25 [Server] INFO Enabling FOMO v0.3
10.05 12:03:25 [Server] INFO Connected to WebSocket
10.05 12:03:25 [Server] WARN javax.security.auth.login.LoginException: The provided token is invalid!
10.05 12:03:25 [Server] WARN at net.dv8tion.jda.internal.JDAImpl.verifyToken(JDAImpl.java:361)
10.05 12:03:25 [Server] WARN at net.dv8tion.jda.internal.JDAImpl.login(JDAImpl.java:281)
10.05 12:03:25 [Server] WARN at net.dv8tion.jda.internal.JDAImpl.login(JDAImpl.java:248)
10.05 12:03:25 [Server] WARN at net.dv8tion.jda.api.JDABuilder.build(JDABuilder.java:1931)
10.05 12:03:25 [Server] WARN at com.jamesinaxx.fomo.FOMO.onEnable(FOMO.java:51)
10.05 12:03:25 [Server] WARN at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:263)
10.05 12:03:25 [Server] WARN at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:380)
10.05 12:03:25 [Server] WARN at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:483)
10.05 12:03:25 [Server] WARN at org.bukkit.craftbukkit.v1_16_R3.CraftServer.enablePlugin(CraftServer.java:501)
10.05 12:03:25 [Server] WARN at org.bukkit.craftbukkit.v1_16_R3.CraftServer.enablePlugins(CraftServer.java:415)
10.05 12:03:25 [Server] WARN at net.minecraft.server.v1_16_R3.MinecraftServer.loadWorld(MinecraftServer.java:591)
10.05 12:03:25 [Server] WARN at net.minecraft.server.v1_16_R3.DedicatedServer.init(DedicatedServer.java:281)
10.05 12:03:25 [Server] WARN at net.minecraft.server.v1_16_R3.MinecraftServer.w(MinecraftServer.java:1065)
10.05 12:03:25 [Server] WARN at net.minecraft.server.v1_16_R3.MinecraftServer.lambda$a$0(MinecraftServer.java:289)
10.05 12:03:25 [Server] WARN at java.base/java.lang.Thread.run(Thread.java:834)
10.05 12:03:25 [Server] INFO Successfully initialized FOMO discord bot
10.05 12:03:25 [Server] INFO Successfully initialized FOMO

Running on Apex Minecraft Hosting

Also the config.yml file did not prepopulate the field with token: or channel: so this might be the problem.
I've configured the config.yml file as such:

token: xxxxxxxxxxxxxxx
channel: '1234567890'
commented

This has been fixed in the latest version 0.4

commented

Sorry to hear this. I am aware that there is currently an issue with config.yml, not pre-populating which is annoying because it isn't the most straightforward setup. I believe there should be a template config with comments at the top but assuming there isn't this is the proper way to do it.

bot:
   token: xxxxxxxxx
   channel: 1234567890

I will fix this as soon as I can, Sorry for the inconvenience