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
{{ message }}
This repository has been archived by the owner on Jun 23, 2023. It is now read-only.
Currently from what I've seen the Inactivity scan will flag ships even if the inactive player only owns 1 block in a grid, The majority could be owned by an active player and this is at least for my server causing some problems.
I suggest that the scan check for majority owner, And if a ship is flagged for an inactive player, if they are not the majority owner the ship is not deleted and instead ownership of the blocks they had are transferred to the majority owner.
If the inactive player is the majority owner, the ship should be deleted.
The text was updated successfully, but these errors were encountered:
I like this suggestion. I am not entirely sold on the ownership transfer, though. There could potentially be legitimate reasons to have ownership of different blocks by different people. If I were to also do that part, I'd definitely make it a separately-configurable option.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently from what I've seen the Inactivity scan will flag ships even if the inactive player only owns 1 block in a grid, The majority could be owned by an active player and this is at least for my server causing some problems.
I suggest that the scan check for majority owner, And if a ship is flagged for an inactive player, if they are not the majority owner the ship is not deleted and instead ownership of the blocks they had are transferred to the majority owner.
If the inactive player is the majority owner, the ship should be deleted.
The text was updated successfully, but these errors were encountered: