You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have noticed that after each dragon is killed a new end gateway is created. Could you add into the config, a limiter that would force only one end gateway? I have players that stay in the end and wait for the dragons to respawn (respawn on death: 300) and after about 30 min the end is full of gateways.
The text was updated successfully, but these errors were encountered:
I would not be opposed to trying to limit how many end gateways are created. This is something that I've actually considered in the past. The issue I had was that I was not sure whether there was anything I could do to limit that. I'm going to see if perhaps there's some way I can hook into it, but this is not a guarantee that it will be available.
Even setting a keep alive limit on the portals so that they auto remove at the start of a respawn cycle much like the exit portal would be a big help in my opinion
In the current Bukkit API, this option is not available. However, I am considering making a pull request to Bukkit to allow for this to be controllable and to be able to cancel the generation of end gateways. It will not be available in the next update (as of this comment) but will be available in a future version.
2008Choco
changed the title
Request: Limit end gateway creation
Limit end gateway creation
Mar 14, 2020
I have noticed that after each dragon is killed a new end gateway is created. Could you add into the config, a limiter that would force only one end gateway? I have players that stay in the end and wait for the dragons to respawn (respawn on death: 300) and after about 30 min the end is full of gateways.
The text was updated successfully, but these errors were encountered: