End Gateway will not be created upon Dragon Death

[nebula-a]

What behaviour is expected:

That a new gateway would be created each time the dragon dies - there are currently 4 in my world so there's plenty of room.

What behaviour is observed:

No new gateway appeared when the dragon was defeated.

Steps/models to reproduce:

• Defeat the dragon once
• Defeat it at most 3 more times after re-spawning it.
• Observe the number of end gateways each time.

Plugin list:

Plugins (13): CoreProtect, DiscordSRV, EntityChecker, EzFilter*, LuckPerms, LuckPermsChat, NoCreeperGrief, OpenInv, PlugMan, spark, StaffChat, SuperbVote, Votifier
Note: StaffChat is developed by me for my server and is chat-related only.

Paper build number:

24

Anything else:

Not that I can think of - possibly how the dragon fight is coded but that's all I can say as you develop this.

[nebula-a]

Note: The plugin EntityChecker is also coded by me and only adds a small entity-counting command. NoCreeper grief is too and empties the block list of an explosion.

[kickash32]

Did you upgrade this world from 1.15.2 or older?

[nebula-a]

Did you upgrade this world from 1.15.2 or older?

yes, but all the chunks are upgraded

[DerekWearmouth]

Also having this issue with my 1.15.2 migrated world.

[nebula-a]

Any solutions if this isn't a bug..?

[DerekWearmouth]

Any solutions if this isn't a bug..?

We ended up fully resetting the end file to fix this issue..

I have a similar issue, but the ender dragon is not spawned, and the perch for the dragon which has a portal is also not spawned. It's basically an empty end... I tried many recent builds, none of which helped with this.

[legacy2355]

I am also having this issue. 1.15.2 migrated to 1.16.1. The level.dat changed, is it somehow due to this?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because it has not had activity in a long time. If the issue still applies to the most recent supported version, please open a new issue referencing this original issue.