Issues with players/ships on beta

[Devious]

We are currently experiencing an issue where players lost their ships after we moved the player dat files, it appears some players got duplicated so it would be valued if we can get some light on the changes made in this patch:

 

Crafts that were destroyed through database corruptions can be restored

Players can be moved to other sectors, including ships (just rename the files if the names clash)

 

How can we restore a destroyed craft? It happens often that a player is destroyed while loading into a sector, which obviously shouldn't happen.

 

How can we move a player (and his ships) to another sector? Some sectors seem to be very heavy on the client, which causes them to get stuck on the loading screen into that sector. Teleporting them out works, but sometimes a player his ship is left behind.

 

 

 

 

 

 

[Hammelpilaw]

How can we restore a destroyed craft? It happens often that a player is destroyed while loading into a sector, which obviously shouldn't happen.

 

What I found out yet: If a player is in a crashed sector (server crashes when he logs in) you have to delete the sector to make the player able to login without crashing the server again. Before 0.12 his ship(s) in this sector were deleted, but now all player ships and stations get restored from the player files and spawned into the sector as soon as it gets regenerated.

 

I don't think you could restore a destroyed ship, but im not sure.

[Devious]

We finally have seem to get rid of it by removing the jumpsmeta.dat, every time a player would jump to the corrupted sector (or a sector connected to it by gates) the server would crash on jumping. The sectors that were connected by a gate would let you charge your jumpdrive if you press spacebar after selecting the sector to jump to, the corrupted sector itself didn't even let you do that. Manually restoring the sector after deleting jumpsmeta.dat seemed to have gotten rid of it.

 

it may or may not have been caused by the server not shutting down properly but now that we have taken this step it didn't seem to have come back yet.