on chunk generation?

Hello,
Is there an event that runs upon the finishing of generating a chunk? I know about ChunkPopulate event, but I'm not sure exactly when its ran...

Thanks

 

try this:
@EventHandler
public void chunkGenerationEnd(ChunkLoadEvent e) {
if (e.isNewChunk()) {
//What ever you need to do here
}
}

The documentation for the ChunkLoadEvent is here

 

slam5000 But at that time the chunk isn't populated, so not really finished (trees, ores, ... missing).

@Megalos

Source: http://jd.bukkit.org/doxygen/d6/d62/classorg_1_1bukkit_1_1event_1_1world_1_1ChunkPopulateEvent.html

 

you're right... upon closer inspection of the documentation though, I did notice that the ChunkPopulateEvent is called after the chunk is populated, and a chunk is populated at the end of its generation lifecycle, so if that's what you're looking for Megalos, than you can use ChunkPopulateEvent. Just wondering so I might be of more use, what exactly are you trying to achieve?

 

I wanted to empty all chunks over a certain coordinate, yet I can't use a terrain generator since it would also override the default terrain generator
v10lator, I've seen that, but just to clarify, I meant whether its before or after the chunks are sent, my bad, should have mentioned it. I already found the solution though, thanks.

 

OK, so in trying to stop a chunk from generating, you're going beyond the Bukkit API's capabilities. Currently, there's no real way to just stop a chunk from loading. (besides taking the worldborder strategy, and just stopping players from getting close enough to the chunk for it to load.)

This is due to a weird (not really glitch... but it could be an issue for some coders) mechanic in how the minecraft server loads chunks. If you for example stopped a chunk from generating, bukkit will accept you telling it not to load, but the minecraft server will notice the players's still in range of the of the chunk, and attempt yet again to tell the server to load the chunk. This of course will once again fire the chunk load event... which you will cancel again, creating an infinite loop. If you only want the appearance of there being nothing at that location, you could use player.sendChunkChange() to send a fake empty chunk, but other than that, I don't think you can just stop a chunk from generating.