This is related to SoR check in, but with login acting in place of a literal check-in.
If a player hasn’t logged in between 32hrs and 8hrs (24 hr window) before SoR, they are deleted so the family can find a replacement.
Vote for this feature to raise its priority and get it done faster!
I agree with the principle… but not sure of the mechanic. Would it be possible for leaders to override this, if, for example, I’ve been online with the team for prior to this, but for some reason couldn’t make it online for a day?
Imho both is needed.
if you don’t meet checkin, than leader can remove you.
@Belg, yeah we’d need a way to allow for exceptions. A new family tag could work.
@The_LiGhTgUnS that would be effective, but also very heavy-handed and could cause other problems. It reminds me of leaders who have asked if we can delete players who don’t respond to their messages.
We don’t want to create communication requirements to be able to play at all. SS is a valid choice.
If you check-in than leader can’t remove you.
That’s requiring players to jump through hoops. Logging in is sufficient.
The feature posted here won’t include a check-in. I’ve re-opened the other thread if you want to make a case for a distinction there.
Will the votes of my original idea be inherited to here 
Nope, it’s a distinct idea and code change. 
This is an interesting situation though, I think some of your votes there may be from people who might be satisfied with this alternative, and just wanted something to get rid of those inactives.
I could be wrong, but I’ve added an explanation just in case.
Honestly, I don’t like the automatic deletion. Not unusual to join and then not bother to log back in until SOR, especially during the days of outgame family forums and IRC.
HC camaar can join at round opening, fb rc on hp, built expos and the next time I need him is tick 7 when expos land and he needs to aid to built.
Seriously, one log-in 31 hours before SoR is enough not be removed for inactivity?
That doesn’t work for me… You’ll still be stuck with an inactive that just joined 31 hours before SoR, and never logs in again.
I’d like a check-in act to be done by the player, and the leader to be able to tag players who didnt check in for deletion.
Wouldn’t the same problem exist once they log in and check in 31 hours before SoR, and then never come back?
I’d prefer that empire deletion for inactivity remain within control of the family, and not be an automatic coded feature. There could be a multitude of reasons for this, with one such example being a player joins but is traveling and unable to log in again until right before or after the SOR. The decision to leave the person in the game or not, should ultimately rest with the family and its leader to make.
That’s reasonable.
Would it suffice to add an additional check here that the player must also be marked inactive? That would also solve the problem @Belg mentioned.
This would make it semi-automated based on time, but also within the family’s control to bypass.
Yea true, but it is another step. I guess what I’m also having trouble with is 32 hours is a LONG time before SoR…
But I guess it’s a good start, let’s try it out and we can fine-tune it based on the results 
Would it suffice to add an additional check here that the player must also be marked inactive? That would also solve the problem @Belg mentioned.
This would make it semi-automated based on time, but also within the family’s control to bypass.
That would be workable.