Todays login-blackout came at a particularly inopportune time for me. A very close friend and I were just in the process of getting closer.. And exploring a level of intimacy that we hadn't yet reached.. when a poseball pair failed to load the poses correctly. Eh, it happens.. SL is buggy, fine. The solution.. pop off and back on... works almost every time. So, we said our mutual "brb's" and hit the [X]. 60 seconds later we were smacking our foreheads. We'd seen the blue-box announcement about 20 minutes earlier, saying that logins had been disabled due to a grid issue.. And it was our own stupid fault for logging off.
But this is the first time that those login-disabled things have caught me off gaurd, and left me standing at the gate going.. "well how stupid! What was I thinking?" and for the breifest of moments.. I thought.. "why didn't they warn me?"
Now.. it was at this moment that I understood the cognitive disconnect that is going on for many. Often times, we do get those blue box warnings.. and they don't register fully. Frankly we get so many blueboxes during the day.. it's hard to take any of them too seriously.
But what's missing.. in this whole thing.. seems to be a "are you sure you want to quit? logins have been disabled so you won't be able to get back in until this is remedied" Some kind of a checkback that queries the state of logins... so that when the user hits the [X] button to basically give us a little bit of a failsafe, in the event that logins are limited at that moment.
I think it would go a LONG WAY towards solving most of the "why no inworld warnings" complaints, and would result in far fewer people banging their head against the wall in frustration.. After all.. you can be mad at the software when it allows you to quit without saving.. but you can only be mad at yourself when you TELL it not to save on exit.