Uploaded image for project: 'Spigot'
  1. Spigot
  2. SPIGOT-4882

EntityExplodeEvent appears to fire every tick because of the enderdragon...

XMLWordPrintable

    • 06.05 14:05:25 [Server] Server thread/INFO This server is running CraftBukkit version git-Spigot-1eece4f-fe1199c (MC: 1.14) (Implementing API version 1.14-R0.1-SNAPSHOT)
    • Yes

       

      While working on plugin development I was attempting to listen to EntityExplodeEvent and After putting in some debug code my console was spammed constantly with the following message.

       

      (my debug message) ->

      [code]06.05 14:05:17 [Server] Server thread/INFO Exp event list: 0 type: ENDER_DRAGON 06.05 14:05:17 [Server] Server thread/INFO Exp event list: 0 type: ENDER_DRAGON 06.05 14:05:17 [Server] Server thread/INFO Exp event list: 0 type: ENDER_DRAGON 06.05 14:05:17 [Server] Server thread/INFO Exp event list: 0 type: ENDER_DRAGON 06.05 14:05:17 [Server] Server thread/INFO Exp event list: 0 type: ENDER_DRAGON 06.05 14:05:17 [Server] Server thread/INFO Exp event list: 0 type: ENDER_DRAGON 06.05 14:05:17 [Server] Server thread/INFO Exp event list: 0 type: ENDER_DRAGON 06.05 14:05:17 [Server] Server thread/INFO Exp event list: 0 type: ENDER_DRAGON 06.05 14:05:17 [Server] Server thread/INFO Exp event list: 0 type: ENDER_DRAGON[/code]

      this will output as long as the plugin is enabled, I can exclude if the entity is of type ender_dragon but it seems like the event shouldn't be firing with the dragon just flying around doing nothing.

       

      It also fires constantly with no players in that world.

       

      code to reproduce error:

      [code]

      @EventHandler
      public void onEntityExplode(EntityExplodeEvent e)

      { System.out.println("Exp event list: " + e.blockList().size() + " type: " + e.getEntity().getType().name()); }

      [/code]

       

            Unassigned Unassigned
            whoolieshop Shane Martin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: