Quote Originally Posted by QT_Melon View Post
Yeah but you're on Balmung which is notoriously overcrowded. I think I feel for players that are on smaller servers and having to get forced out. It's not like their server is the problem.
It's not a single server issue. Players in their personal chamber or private house using one of those tactics ties up a transient (created when you enter and torn down when you leave) instance on the instance server that handles all short term instances for the data center as well as tying up a place on the transfer server that handles transferring you from one instance to the next. That impacts smaller worlds as well as larger ones because the instance servers are shared, while the world servers handle the open world zone instances. On Balmung, you could have a zone that is overpopulated in addition to many hundreds of inactive players in transient instances of some kind, such instances not only inclue private house, apartment, personal chambers, Aesthetician, Inn, solo duties and dungeons/trials, etc... so if a significant amount of the server resources are tied up maintaining solo instances for habitual AFKers, it reduces the resources available for duties, which hurts the Queues and slows performance - for everyone in the data center.

Personally, I feel that SE should work on coding better AFK detection, and institute a 3 strikes system after which you are autologged out and locked out of the server for an increasingly long cool down each time you are auto logged out during any given 7 days. Perhaps people will finally be discouraged from pointlessly tying up server resource in the mistaken belief that they need to to ensure their spot on the server is saved.