Plugin attempted to register task while disabled

Discussion in 'Plugin Development' started by Chinwe, May 3, 2013.

Thread Status:
Not open for further replies.
  1. Offline

    Chinwe

    I updated bukkit and craftbukkit on my test server for my minigame, when suddenly every scheduler started throwing this IllegalPluginAccessException. I downgraded back to the original version but it still persists :c

    It occurs on every scheduler that worked before, and I haven't (consciously) disabled the plugin before this or anything.

    Code:
    2013-05-03 19:43:51 [SEVERE] org.bukkit.plugin.IllegalPluginAccessException: Plugin attempted to register task while disabled
    2013-05-03 19:43:51 [SEVERE]    at org.bukkit.craftbukkit.v1_5_R3.scheduler.CraftScheduler.validate(CraftScheduler.java:394)
    2013-05-03 19:43:51 [SEVERE]    at org.bukkit.craftbukkit.v1_5_R3.scheduler.CraftScheduler.runTaskTimer(CraftScheduler.java:120)
    2013-05-03 19:43:51 [SEVERE]    at org.bukkit.craftbukkit.v1_5_R3.scheduler.CraftScheduler.scheduleSyncRepeatingTask(CraftScheduler.java:116)
    2013-05-03 19:43:51 [SEVERE]    at net.chunk64.ctc.utils.GameUtils.startGameCountdown(GameUtils.java:68)
    2013-05-03 19:43:51 [SEVERE]    at net.chunk64.ctc.CaptureTheChicken.onCommand(CaptureTheChicken.java:285)
    2013-05-03 19:43:51 [SEVERE]    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:44)
    2013-05-03 19:43:51 [SEVERE]    at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:189)
    2013-05-03 19:43:51 [SEVERE]    at org.bukkit.craftbukkit.v1_5_R3.CraftServer.dispatchCommand(CraftServer.java:523)
    2013-05-03 19:43:51 [SEVERE]    at net.minecraft.server.v1_5_R3.PlayerConnection.handleCommand(PlayerConnection.java:965)
    2013-05-03 19:43:51 [SEVERE]    at net.minecraft.server.v1_5_R3.PlayerConnection.chat(PlayerConnection.java:883)
    2013-05-03 19:43:51 [SEVERE]    at net.minecraft.server.v1_5_R3.PlayerConnection.a(PlayerConnection.java:840)
    2013-05-03 19:43:51 [SEVERE]    at net.minecraft.server.v1_5_R3.Packet3Chat.handle(Packet3Chat.java:44)
    2013-05-03 19:43:51 [SEVERE]    at net.minecraft.server.v1_5_R3.NetworkManager.b(NetworkManager.java:292)
    2013-05-03 19:43:51 [SEVERE]    at net.minecraft.server.v1_5_R3.PlayerConnection.d(PlayerConnection.java:109)
    2013-05-03 19:43:51 [SEVERE]    at net.minecraft.server.v1_5_R3.ServerConnection.b(SourceFile:35)
    2013-05-03 19:43:51 [SEVERE]    at net.minecraft.server.v1_5_R3.DedicatedServerConnection.b(SourceFile:30)
    2013-05-03 19:43:51 [SEVERE]    at net.minecraft.server.v1_5_R3.MinecraftServer.r(MinecraftServer.java:581)
    2013-05-03 19:43:51 [SEVERE]    at net.minecraft.server.v1_5_R3.DedicatedServer.r(DedicatedServer.java:226)
    2013-05-03 19:43:51 [SEVERE]    at net.minecraft.server.v1_5_R3.MinecraftServer.q(MinecraftServer.java:477)
    2013-05-03 19:43:51 [SEVERE]    at net.minecraft.server.v1_5_R3.MinecraftServer.run(MinecraftServer.java:410)
    2013-05-03 19:43:51 [SEVERE]    at net.minecraft.server.v1_5_R3.ThreadServerApplication.run(SourceFile:573)

    The line in question (68) is a standard scheduler:

    Code:
            final int startCountdown = Bukkit.getScheduler().scheduleSyncRepeatingTask(new CaptureTheChicken(), new Runnable()
            {
                int countdownLength = 3;
                Location chickenSpawn = CaptureTheChicken.spawnLocationsRedBluChicken[2];
     
                public void run()
                {
                    BukkitUtils.messageAllPlayers(ChatColor.GRAY + "Game starting in " + ChatColor.GREEN + countdownLength + ChatColor.GRAY + " seconds!");
                    chickenSpawn.getWorld().playSound(chickenSpawn, Sound.ORB_PICKUP, 5, 0.3F);
                    countdownLength--;
                }
            }, 0, 20L);
     
  2. Offline

    chasechocolate

    Are you ever disabling the plugin anywhere in your code? Does it throw an errors besides the one you posted?
     
  3. Offline

    Chinwe

    Nope, I'm not disabling it at all. And no, this is the only error it is throwing, and it happens with all schedulers.
     
Thread Status:
Not open for further replies.

Share This Page