07-06-2014, 09:24 PM
You cannot change the entire world at once, because the server would have to load all the chunks for the world and re-save them with the new biomes. You need to follow a different approach, you've already mentioned that - first change all the chunks around players and then change each chunk as soon as it gets loaded or generated by the server. Note that you can already keep track of the loaded chunks for each world, simply by using the chunk unloading and loading hooks to store the chunk coords in a table.
There will probably never be a proper API function to enumerate all the loaded chunks, because as soon as such a function call would return, the data could be invalid - another thread may unload the chunk or load another chunk. We could use callback-based API so that you can execute code for each chunk loaded, but in this plugin's case it could be too much of a performance hit.
There will probably never be a proper API function to enumerate all the loaded chunks, because as soon as such a function call would return, the data could be invalid - another thread may unload the chunk or load another chunk. We could use callback-based API so that you can execute code for each chunk loaded, but in this plugin's case it could be too much of a performance hit.