New pvp map, and a not-so-small problem
Posted: Thu Jul 18, 2013 3:26 pm
Today the pvp map was reset.
As a few of you have already noticed firsthand, some people are ending up at spawn with empty inventories. What has happened is that every person in the pvp world at the time of the reset, have had their player data unintentionally wiped.
This glitch was entirely human error. For the map resets, I've made a script that does things such as clean the map, backup everything, and teleported people in the pvp world back to where they were in the normal world. Within the past couple of days I've updated it to make sure it works in 1.6, and I've tested it locally. Now, as part of this script, I have to manually enter the UUID of the normal world, so that it knows which world to move people to. This UUID is different on all worlds, meaning that what I had it set to for my tests is not correct for the actual server, this is where the problem lies. In my haste to get the reset over with, I forgot to change the set UUID to that of the server's normal world. Running the script, these players location was set to a non-existent world. Minecraft, thinking that the player data was corrupted, then reset all the player files.
This was entirely human error, and I take full responsibility.
I do still have partial backups from this, and so for those affected, replacement claims are open.
I sincerely apologize for this mistake.
And, on the happy side, the new pvp world is up and running :)
As a few of you have already noticed firsthand, some people are ending up at spawn with empty inventories. What has happened is that every person in the pvp world at the time of the reset, have had their player data unintentionally wiped.
This glitch was entirely human error. For the map resets, I've made a script that does things such as clean the map, backup everything, and teleported people in the pvp world back to where they were in the normal world. Within the past couple of days I've updated it to make sure it works in 1.6, and I've tested it locally. Now, as part of this script, I have to manually enter the UUID of the normal world, so that it knows which world to move people to. This UUID is different on all worlds, meaning that what I had it set to for my tests is not correct for the actual server, this is where the problem lies. In my haste to get the reset over with, I forgot to change the set UUID to that of the server's normal world. Running the script, these players location was set to a non-existent world. Minecraft, thinking that the player data was corrupted, then reset all the player files.
This was entirely human error, and I take full responsibility.
I do still have partial backups from this, and so for those affected, replacement claims are open.
I sincerely apologize for this mistake.
And, on the happy side, the new pvp world is up and running :)