Improved Anti-AFK

[HoratioGamer]

Is your feature request related to a problem? Please describe.

In 2b2t, server restarts come at unpredictable times. Whenever Anti-AFK is turned on, and the player walks away from the keyboard (perhaps waiting for a second account or another player to come online), there is the risk there will be a server restart, and, the account will come back online with Anti-AFK still active. When Anti-AFK is active when minecraft enters the server, it will often send the player's character off on a long diagonal walk to who-knows-what location. This is a huge problem because if the point was to keep the location secret, this behaviour, over a period of time will cause a starburst shape of NewChunk trails all leading back to the AFK location, which might be a stash or a base. This prevents one from leaving Anti-AFK on and AutoReconnect on.

Describe the solution you'd like

Solution 1: Automatically disable Anti-AFK when minecraft enters the server. At least then one has an AFK detection time on the server before being booted off. Then one can safely leave an account in Anti-AFK with AutoReconnect on. The KISS, but not as useful solution.

Solution 2: When Anti-AFK is initiated, record the coordinates at which it was initiated. When minecraft enters the server, if Anti-AFK is on, and the coordinates of the last location at which Anti-AFK was activated is say within 200 blocks, then step 1) goto the last initiation location. Restart the Anti-AFK algorithm. The effect of this would be, one could leave Anti-AFK on and not worry about restarts or AutoReconnect -- the Anti-AFK behaviour will properly resume when the account is next online.

A separate side-benefit of this solution means, a player can put their account in Q before going to school or work, and when returning home, have a good chance of finding their account AFKing in 2b2t, essentially having passed the Q while at school or work. This would be especially useful for those who have non-prio alt accounts they use to support activities on 2b2t, then they would merely have to sit the prio Q with their main account to accomplish material transfers or pearling.

Describe alternatives you've considered

AutoLog has a feature for Crystals, that quite irritatingly will cause a player to AutoLog over the mere existence of a historic crystal. This prevents one from leaving the Crystal option on when AFK travelling on a highway in 2b2t -- a historic crystal will cause the account to AutoLog causing a Q wait to resume play, just over someone having left a crystal behind on the highway. At first, I found this feature bothersome and always left it turned off. The current behaviour of the Crystal option of AutoLog allows one to intentionally AutoLog an account in other cases where it might be desireable:

a) The Crystal Pearl. It is used when the player to be pearled is on first, and the person loading their pearl is on at some later time. The person to be pearled can set a crystal pearl at the destination location previously visited. When at a different location, the person to be pearled can enter Anti-AFK to await the other person coming on line. The person coming on line triggers the Crystal Pearl, a variation of a dry pearl, where the pearl landing zone is surrounded by crystals. Immediately after pearling, the client of the traveller detects the crystals and AutoLogs the traveller. The traveller has arrived, even through the player was AFK, perhaps even asleep hours ago. They person loading the pearl and the person being pearled do not need to coordinate. The next time the person travelling logs in, they have arrived at the destination location and can reset the pearl that lands in the area with crystals.

b) The Crystal-Guarded Anti-AFK ring. This is not a very good solution because it will just lead to the player AutoLogging immediately after getting back on-line, sort of defeating the purpose of AutoReconnect. Simply, an Anti-AFK square is surrounded by crystals and AutoLog with the Crystal option is used. If the game restarts while in Anti-AFK, and the account starts to walk away from the Anti-AFK area, it will pass close to a crystal and AutoLog.

In retrospect, the Crystal option should have two options: New Crystals, as in, freshly laid so one can walk by historic crystals on a highway without be autologged, and Historic Crystal the more conservative approach that is also useful for these other purposes when one wants to intentionally AutoLog.

Additional context As one cooperates with other players more, the ability to safely Anti-AFK in the presence of restarts is useful. In my experience, this comes up whenever cooperating with players in very different timezones, or very different availability schedules.