Attachment to Defeat Idle Logout, How the Heck Does it Work?

But there are occasions when it might be useful to remain in-world even while you're away from the keyboard. For instance, one day I was at a discussion group that was scheduled to run for a couple of hours, and I was called away before it was over. In this case, it was less than half an hour before the end time, so I just walked away and let the idle-timer logout happen -- but suppose I had been called away earlier? I might well have used an idle-logout defeater to stay in-world for the entire discussion, and then go back later and read it in my history.

It makes sense though. LL use the same basic trick for a few other things. For example, the "Editing appearance" thing doesn't actually appear when you go into edit mode... it appears *when you play the edit mode animation*.

Wow...lots more drama over this then I thought there would be....

I for one call it a godsend.

Beyond its obvious use for camping chairs, this item is wonderful for me. I do a lot of scripting in outside programs because the linux client can be flaky at timed (no copy/paste..eek!) and sometimes those coding binges can get quite long. If I idle out...I'd have to log back in to SL and make sure that everything was still setup correctly, get my script inworld and then probably go back to my notepad and start again....possibly to be logged off again. Thanks to this little gem...thats not a worry anymore

Call the toll-free number press 4 and ask Lee...

Beyond the questionable ethical considerations (more on that in a minute), I also have the same issue. I spend time in here, the Wiki, an editor, et cetera while I have the SL client open. Inactivity disconnects are annoying, but thankfully the client doesn't freeze everything and leave your tuckus hanging in the breeze with that one big script you were working on and forgot to save before being disconnected. You at least can go into the edit window and copy/paste the data into an editor, then reload SL and paste it back into the file, and then either continue coding or save it. I would prefer it if somehow SL could check my "activity" via OS call (much the way screen savers work), and not time me out if I am simply switched away, but still active on the computer.

One thing I didn't realize for quite a while is that, even with compile errors, the save still goes through. I thought until just recently that it had to compile, otherwise it wouldn't save. Perhaps if they made sure to issue the "Save complete." message even when the compiler barfs, it would be a little more intuitive.

About the idle timeout avoidance issue... I have to believe that if they bothered to implement an idle timeout, there were valid reasons for doing so. I don't think "chair-camping" is a valid reason to avoid it. I think it is an unintended artifact of the dwell system, and I would expect that LL takes a dim view of it, especially since you aren't really "dwelling" in SL while you are at work with your computer logged in at home. It's more like public loitering than anything. That said, I don't agree with the counter to the argument concerning additional lag. Players have a right ("right" as in per the ToS agreement, not as in a statute "right", so don't go there, please) to be logged in, and have a right to wear avatars or use items that wouldn't otherwise break the ToS, whether they are afk or not. As such, I don't think that argument has merit, except as far as land owners go, and even then, land owners have ways of dealing with it (no foreign scripts, capiche? ). Everyone also has the ability to adjust their own client's rendering parameters to control rendering performance, so that's not really an issue in my mind, either.

As a scripter, I try to be VERY conscious of what I make, both in the design, and implementation phases. Some of the first subroutine tools I made were debugging and profiling tools. I also do things like set particle budgets for all my effects; something very few scripters seem to worry about, given the amount of particle starvation I have seen in some areas. Anyway, the upshot is that, yes, we do have an obligation to keep our creations from degrading the experience of all playing the game as much as possible, while keeping in mind our needs to do the things we want to do.

Do note that if you use outside tools for scripting, etc. you can minimise SL and the taskbar icon will flash (assuming your OS supports it) whenever you get:
An IM
A dialog
And you know what happens withing a few minute of being logged out? A "You are about to be logged out" dialog message. This has come in handy on a few occations, notably when someone (either in SL or out of) points me towards a video and it's longer than the idle-timeout of SL. And SL needs to be minimized for me to watch it because otherwise the video flickers.
(This post not meant to offed, just inform.)

I think a lot of good points were brought up here, and most of the topic has been covered so I'm going to step out now. My main concern was the same concern that customers were IMing me with, asking if this was a TOS violation. I'm interpreting the Linden response that was linked here as saying this is not a direct TOS violation if you use it under normal circumstances, which alleviates my number one issue. I definitely agree though that the ability to create things in SL brings with it a responsibility to improve the system rather than destroy it, and discover and point out flaws, weaknesses, and unintended consequences.

Well, if camping gets killed entirely, then your kill-idle-timeout device will not be a TOS violation and probably doesn't need to be broken by LL fixing the loophole it exploits. It's a usefull tool and if there isn't anything to abuse by using it, don't fix the problem.

Besides, there are other ways to camp and not get logged out.

This only works on a "supported OS" ie Windows (Winblows for those of us in the know). I for one, am not under Bill Gates' thumb...so this feature does nothing for me. If I am running a multidesktop Unix based environment...trust me, even if there is a taskbar icon...it doesn't flash. And you can't say I can depend on audio cues...because I have so SL sound under linux (Hint hint!).

I'd be more then happy if there was some method of informing me quite simply "Oh nos...I'm gonna log you out in 5 minutes" that I could see without having to look at second life to not use an anti-idler and take resources...but as of right now...there isn't without me taking the initiative to do some scripting to monitor the terminal that SL runs in (even if I could...hmmm).

So for now...MC Seattle...thank you so much for such a valuable tool to add to my arsenal

I don't think you can consider Torley authoritative in this situation.

Like I said, if the OS supports it.
And yes Windows doesn't just blow, it sucks too (although I must say that I have had very few problems with WinXP). One of these days I'll actually try and get Mandrake working (or I should say, it works now, but it's missing stuff I need). Oddly enough, it works despite the fact that I partitioned over it and tried to install Gentoo three times....Still trying to work that one out (along with how Gentoo could fail to install because "not enough disk space" on a ~65 GB partition).

Wow. I don't get logged out while scripting simply because I can't script outside of SL. How are you doing your scripting outside SL?! (Sorry, THIS is offtopic, but I HAVE to know!) So far not only can I not copy/paste within SL itself, but I can't interact with my Window Manager's clipboard either, so I have to manually type EVERY SINGLE CHARACTER! How, how, how? I've been considering writing a program to send key events to SL just so I can paste scripts, in fact! HELP!

Select the text with Ctrl A, copy with Ctrl C, paste with Ctrl V.

If that doesn't work for you, consider re-installing Windows?

Perhaps you missed that the two of us are on Linux. Sorry about that.

And LL has been slacking on fixing the cut/paste deficiency... Even though it's been bug tracked a number of times.


- d.

It's actually a complicated thing to do for disabling your idle. The orb of anti-idle does not work anymore so I will talk to the Lindens and I think they have a solution for disabling the idler. Until then, I'm Austin Zon saying "Peace Out!"

alt+ctrl+d , client - character - character tests , remove AKF , thank you

no more idle never logout

Is that persistant, or do you have to check remove AFK ever time you log back in like the remove camera constraints option?

that is persistant and will stay for as long as u don't uninstall the game