yetanotherusername
commented
11 years ago This change in code created a problem that was not there before. The script does not create the folders in the /dev/shm folder for the worlds and instead overwrites the previous world and generates a new one. What a surprise when changing to ramdisk for world and logging back into a newly generated world, thank goodness for backups! Removing the changes restores the normal functionality, otherwise you would have to manually create the folders for world in /dev/shm before changing flag for ramdisk. Once the folder is first created manually, it seems to work okay. If the server OS is rebooted though, these folders in /dev/shm (being volatile since it is RAMdisk) do not exist on reboot, but minecraft starts on reboot so in this scenario, on reboot, you lose your world (again) and it gets overwritten with a newly generated one, and as it does that, the script complains that the world cannot be found and needs to be moved to the worldstorage folder.
Ahtenus
My plugin create world and destroy them after a certain time, this modification is needed to clean the MCPATH from this obsolet worlds.
I added a checkLink in the "world backup" routine, cause for the same reason, some worlds are created while the server is running, I dont add this change in this pull, cause I assume its an personnal adjustment :D, but you could add too cause some plugins use creation on the fly too (multiverse-like).