Chunk Save Signed with airSlate SignNow

Chunk save initial

oh my goodness is how uncle oh yeah it's me lunk oh here in charge of programming short number-one let's get into business five weeks ago we implemented chunk loading but chunk loading is only half the story so today we're going to be implementing the other half chunk saving to save chunks we need to follow the same convention that we used to load them in dev log 3 we outline the basic structure of a saved chunk file we store each chunk in a file with name given by the coordinates of that chunk in the file we have a 16 by 16 grid of tile types specifying the type of each tile and lastly for each entity inside the trunk we list out the entities type image and position relative to the top left of the chunk and you might ask local which chunks do we save all of them good question these two categories of chunks required saving number one newly generated chunks and number two changed chunks without further ado let's jump into the code alright so let's quickly make a chunk saver class which we will be using to save chunks for the constructor we're gonna need a list of chunks we need to save the name of the world stored in this game world info class and an image to string map that tells us given images load path let's save these parameters as class variables and now let's move on to the actual save function the save function should also take in a frame data thanks to the buffered rendering we implemented in deadlock 5 so first we'll just make a for loop looping for each chunk in our chunk list to write to a file we're going to be using the built-in class called buffer Grider the syntax to use buffered writer is like so and we'll just make this function throw an i/o exception to avoid tri caches next for each tile in the 16 by 16 tile grid I'm going to have to turn that tile into a tile index from devlog 3 in our tile factory we already have an ID to tile type hash map for chunk reading similarly we're going to need a tile type to ID hash map like the opposite and back to our safe chunks function we'll get this map that we just made once at the beginning and write out each tile type to the file done but we're only halfway we also want to save and 2d data we arbitrarily decided in devlog 3 now we would be saving each entity in the following format type for example like obstacle mob decoration name of the image and the coordinates relative to the number of tiles from the top-left of the chunk again from dev log 3 we have a char to entity type hash map for entity reading so we'll quickly create a reverse map for entity saving moving on to...