[SPIGOT-4882] EntityExplodeEvent appears to fire every tick because of the enderdragon... Created: 06/May/19  Updated: 06/May/19  Resolved: 06/May/19

Status: Resolved
Project: Spigot
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Shane Martin Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: enderdragon, entityexplodeevent

Version: 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)
Guidelines Read: Yes

 Description   

 

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]

 

 Comments   
Comment by md_5 [ 06/May/19 ]

Happens in 1.13.2.

Please follow the instructions in future.

Comment by md_5 [ 06/May/19 ]

What about 1.13.2 ?

Generated at Sat Dec 13 13:43:15 UTC 2025 using Jira 10.3.13#10030013-sha1:56dd970ae30ebfeda3a697d25be1f6388b68a422.