@bislo1 It takes as long as it takes.

I thought I would be able to at least test tonight, but Im currently stairing at a screen thats converting player names from lowercase to the correct uppercase letters, the conversion to 1.8 isnt just moving to a new server file, its much more.

• GriefPrevention Needs to convert all the data from lowercase to uppercase, for instance my data is stored as godsdead, this needs to be changed to GodsDead, so then it can look up the proper UUID which happens next, so close to 20,000 players need to be checked for upper/lower case first, and then again to convert those to UUIDS.
• Essentials data needs to do the same.
• Then the world itself needs to do a conversion from 1.7.10 to 1.8, We havent got this far yet as im waiting on griefprevention.

Again, this is only a test, a local test, since this data changes rapidly each and every day, Once I have tested everything and I am happy nothing will be destroyed, I then have to run it on the most uptodate data.

See how this is a very, very, very long process?

I think itll take around about 24 hours to just complete the GriefPrevention data upgrade for the development server, once this finishes I can invite people on to see what happened to the world so we can check for problems with those 2 plugins.

Once I have those plugins sorted, I can move on and test each and every plugin individually by itself, again a very very long process, Ironing out any problems along the way.

Then once I have all this tested, I will need to re-do the entire thing again, on the live server.

I predict that all signs will break in this inital test, If they do we have 2 options.

Get every shop owner to empty their shop before the switch, I will give fair warning of a week once im sure there is no way to convert the world saving the data.

The other option which I hope will work is a flag that can be set in the startup shell script to convert old sign data to new, now this is out of my control and lies in the hosts hands, It can only be done once, and needs to be removed, if something goes wrong or they screw it up, then I will have to revert to a world backup.

Seeing that Im not in control I have to work alongside the host to do this, since I cant do it locally and upload the world as my internet is so poor, the world is 3.6GB in size.

Another obstical is that we can only convert GriefPrevention data once the servers already on 1.8, so I would have to wait the 24 hours conversion time to see if the host managed to set the flag correctly and nothing goes wrong.

Unlesss I block all changes to GriefPrevention (somehow?) on the live server so I can convert locally, and upload that live? Its a big catch 22 the whole thing.

Im testing locally, and seeing what happens first.