Ok, going to try to keep this civil. It is a real pain in the a$$ when I am waiting for the df to get into a dungeon and then as soon as the dungeon loads the tank, yes it is always the tank, disconnects. They are avoiding the penalty by unplugging their computer/system. Then those of us who are stuck in there have three options. 1) One person can take the fall and get penalized for doing nothing wrong, 2) we can wait 15 minutes to vote abandon, 3) we can hope that another tank comes along who will not suddenly and mysteriously disconnect as soon as the dungeon loads (that is never going to happen).
My solution: well the server, or whatever it is they use to keep track of who is in which dungeon, will know who just logged in and who just left, either by being "disconnected" or leaving the right way.So, there should be a timer that if a person suddenly became disconnected during the opening cut scene or within 2 minutes (or slightly less) of it, should get a very large penalty on using the duty finder or any dungeon for that matter. Just to make it a real pain for them to get back in and do it again. Even prevent them from logging back in for like 30 minutes on top of it. If they legitimately got disconnected in that very small time frame of watching the cut scene to two minutes into the dungeon that will just be tough luck. I have been disconnected, legitimately, early on in getting into a dungeon, but never during the cut scene or within a minute or two of the dungeon loading. The thing is I try to get back in as quick as I can so we can finish the dungeon and usually I can get back in pretty quick.
You could even go as far as keep track if they are trying to log back in again within a time span. The server has to know where you were since it puts you back in the same dungeon with the same players if you do log back in after legitimately being disconnected. If they are trying to log back in then don't put the ban on them.
I know this kind of stuff is possible, I am about to graduate with my BS CS degree and I have even taken classes on game programming specifically. The "object" representing that character can be kept in a container (first thing I am thinking of is a queue but that might not be the best, depends on what constitutes a "character") when first joining a dungeon that checks: 1) are they disconnected or in the process of disconnecting, 2) at what point did this happen (ie what else was loading)?, 3) if they are gone, hold them in the queue (or other container) until it either times out, at which point they get a ban the next time they log in, or they start the process of logging back in, which will get them back into the same dungeon, and the don't need the penalty. If they are logging back in with a different character then I would penalize the account (ie all the characters on it). I know the code around that is probably complex and there are a lot of things to keep track of.
Still, you guys at Square have some pretty talented programmers. I mean to pull off a complete rewrite in a year is epic, and that is lost on a lot of players in this game. There has to be a better way to handle this stuff than just using a "band-aid" that fixes more false positives than it does the real problems.