Windows 10,

java -d64 -Xms3072M -Xmx3072M -DIReallyKnowWhatIAmDoingISwear -jar spigot-1.15.1.jar
PAUSE

Additionally, a linux cloud machine with 5GB.

Made a PR for this: https://hub.spigotmc.org/stash/projects/SPIGOT/repos/craftbukkit/pull-requests/844/overview

Are you sure that doesn't just generate chunks to create the spawn point?

And what if we add flag to the RegionFileCache, during the spawn point finding, if this Flag is present new chunks are saved to a temporary folder. When trying to load a chunk it will first try to find a present chunk in the normal region folder, if no chunk is present it will search in the temporary folder. After the spawn point is found, it will set the flag back to normal and will deleted the chunks in the temporary folder. This way the Spawn point is present and no chunks are permanently generated before WorldInitEvent. The down sites of this method is that the spawn chunks are generated twice and if a Bonus chest is present, it needs also to be re placed.

But if this solutions is suitable, I can implement it.

As a temporary fix for Leonard, you can set a "dummy" spawn point via ChunkGenerator#getFixedSpawnLocation(World, Random), this way no spawn chunks should get generated (in theory, I only looked in the code not tested it). And in the WorldInitEvent (or other place) you generated the spawn point your self.

But what solution did this thread agree on? Are we adding a new event or are we changing worldinitevent?

The source is managed on Stash, see README.md

Are we supposed to open a pull request on github or....?

Is there any update on whether or not this issue will be solved?

This really depends on the usage of this event if it's used in the terms of world generation modification it's crucial this gets done correctly otherwise I can't think of a proper usage for it however another thing to consider is the fact how the event is described in the documentation. This event should be called prior to any chunk loading and it's not doing that breaking that promise I think we need to either go with not having a spawn or making a other event that will call prior to chunk loading but doing so will make the naming scheme look bad so I'd personally go for option 1 with the knowledge stuff is gonna break

As part of the world init process, the world spawn position needs to be found.
Finding the world spawn position requires loading chunks so that the hypothetical spawn position can be tested to see whether it is suitable or not.

Yes, the WorldInitEvent could be moved before this, but then the world will not have a spawn (or populators or border) when the event is called

Can reproduce and confirm

PASTEBIN: https://pastebin.com/iQ1df3WT

EDIT: To make sure nothing was editing the results i created a fully new server instance and it still happend here is the log output https://pastebin.com/2W0pCapp

Yes. Though if it matters, I did disable nether and end.

Are you generating a fresh world?

Tried a server with no plugins, but the worldiniteventtester plugin. Same result.

What kind of stack traces do I call on? Do I call one inside ChunkLoad and WorldInitEvent?

https://pastebin.com/MaUTdjit

Changed the plugin a bit and got a stack trace.

New plugin has been attached

Cannot reproduce on my clean server.
I suggest you add more debug to your plugin such as world name and stack traces. I also suggest you remove other plugins from your server.

It is definitely present on the latest version of 1.15.2

And it can be so so bad: https://pastebin.com/rfYs7cL3

The new version I'm using is "CraftBukkit version git-Spigot-c574e08-708be69 (MC: 1.15.2) (Implementing API version 1.15.2-R0.1-SNAPSHOT)".

Cannot reproduce on latest version of 1.15.2, and reviewing the code shows the event is called before any chunks are loaded