Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken /q reload #554

Closed
ghost opened this issue Jun 5, 2017 · 2 comments
Closed

Broken /q reload #554

ghost opened this issue Jun 5, 2017 · 2 comments
Assignees
Labels
Bug A bug in the code or in a documentation.

Comments

@ghost
Copy link

ghost commented Jun 5, 2017

I was working with my quests when suddenly I wasn't able to reload the plugin anymore. I've purged all the data, removed all the quests I was editing from the plugin folder and the "packages:" option from the config.yml, rebooted twice the server, still nothing: I can't reload anymore, always the same mistake

[16:13:34 WARN]: Unexpected exception while parsing console command "q reload"
org.bukkit.command.CommandException: Unhandled exception executing command 'q' in plugin BetonQuest v1.10-dev
        at org.bukkit.command.PluginCommand.execute(PluginCommand.java:46) ~[server.jar:git-Paper-1101]
        at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:151) ~[server.jar:git-Paper-1101]
        at org.bukkit.craftbukkit.v1_11_R1.CraftServer.dispatchCommand(CraftServer.java:675) ~[server.jar:git-Paper-1101]
        at org.bukkit.craftbukkit.v1_11_R1.CraftServer.dispatchServerCommand(CraftServer.java:638) [server.jar:git-Paper-1101]
        at net.minecraft.server.v1_11_R1.DedicatedServer.aM(DedicatedServer.java:441) [server.jar:git-Paper-1101]
        at net.minecraft.server.v1_11_R1.DedicatedServer.D(DedicatedServer.java:404) [server.jar:git-Paper-1101]
        at net.minecraft.server.v1_11_R1.MinecraftServer.C(MinecraftServer.java:754) [server.jar:git-Paper-1101]
        at net.minecraft.server.v1_11_R1.MinecraftServer.run(MinecraftServer.java:652) [server.jar:git-Paper-1101]
        at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]
Caused by: java.lang.IllegalStateException: Not scheduled yet
        at org.bukkit.scheduler.BukkitRunnable.getTaskId(BukkitRunnable.java:134) ~[server.jar:git-Paper-1101]
        at org.bukkit.scheduler.BukkitRunnable.cancel(BukkitRunnable.java:18) ~[server.jar:git-Paper-1101]
        at pl.betoncraft.betonquest.compatibility.citizens.CitizensParticle.reload(CitizensParticle.java:96) ~[?:?]
        at pl.betoncraft.betonquest.compatibility.Compatibility.reload(Compatibility.java:393) ~[?:?]
        at pl.betoncraft.betonquest.BetonQuest.reload(BetonQuest.java:638) ~[?:?]
        at pl.betoncraft.betonquest.commands.QuestCommand.onCommand(QuestCommand.java:233) ~[?:?]
        at org.bukkit.command.PluginCommand.execute(PluginCommand.java:44) ~[server.jar:git-Paper-1101]
        ... 8 more

That happened when I disabled the particles (worked fine)

effectlib_npc_effect:
  disabled: 'true'
  class: WarpEffect
  iterations: 10
  particle: dragonbreath
  grow: 0.08
  radius: 1
  delay: 2

AND tried to do something like this in an empty custom.yml

effects:
  Zughy:
    class: WarpEffect
    iterations: 10
    particle: dragonbreath
    grow: 0.08
    radius: 1
    delay: 2

and the event was like:
FIRST_PARTICLE: 'particle Zughy condition:!_start'

Then it broke

EDIT: I had a look at your code, tracing the exception. I "solved" it deleting the whole effectlib_npc_effect section

@RiledUpCrow
Copy link
Contributor

Thanks for the report ^^

@RiledUpCrow RiledUpCrow added the Bug A bug in the code or in a documentation. label Jun 5, 2017
@ghost
Copy link
Author

ghost commented Jun 5, 2017

You're welcome
Oh, btw, just kidding: in-game I see weird fire columns made of particles on NPCs

@RiledUpCrow RiledUpCrow added this to Bugs in Next Release Jul 7, 2017
@RiledUpCrow RiledUpCrow self-assigned this Jul 9, 2017
@RiledUpCrow RiledUpCrow moved this from Bugs to Done in Next Release Jul 31, 2017
@RiledUpCrow RiledUpCrow removed this from Done in Next Release Jul 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A bug in the code or in a documentation.
Projects
None yet
Development

No branches or pull requests

1 participant