You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a player is deleted with "/del_player" any claims that player had will be owned by a UUID with no name. This becomes especially problematic for player ships, as any new player with the deleted player's name will have their ship claimed under the deleted player's UUID.
We need to handle claims when deleting a player, but how should it be implemented? Ship claims can be easily deleted, but planets are a different story. If the old player had claimed important planets, simply un-claiming them could get messy. Maybe we could transfer ownership to a builder (if one exists) or have an optional argument to specify a player that should be given ownership?
The text was updated successfully, but these errors were encountered:
This is really an issue with every plugin that stores data per-player, since only the base data is actually saved on the player object. It might be worth adding some sort of on_delete_player method for plugins to hook into to deal with this.
When a player is deleted with "/del_player" any claims that player had will be owned by a UUID with no name. This becomes especially problematic for player ships, as any new player with the deleted player's name will have their ship claimed under the deleted player's UUID.
We need to handle claims when deleting a player, but how should it be implemented? Ship claims can be easily deleted, but planets are a different story. If the old player had claimed important planets, simply un-claiming them could get messy. Maybe we could transfer ownership to a builder (if one exists) or have an optional argument to specify a player that should be given ownership?
The text was updated successfully, but these errors were encountered: