|
Title: No inactivity on local processes Post by: Crlaozwyn on August 12, 2008, 11:38:31 PM It makes sense (at least to me) for local processes (deletes on your own gateway, password/ip changes, research, and reformats) to not drop due to inactivity. I can elaborate on this if anyone would like me to, but it seems self-explanatory. What do you think, Sir Emi?
Title: Re: No inactivity on local processes Post by: Nagitof on August 13, 2008, 12:40:07 PM I didn't know thats was happening. But deffently does make sence not to be dropped.
Title: Re: No inactivity on local processes Post by: Araeus on August 14, 2008, 06:40:55 PM That would be a big one for research, finish a ton of research and have to wait for AP/HPD to finish them and they start to time out... that would suck...
Title: Re: No inactivity on local processes Post by: Crlaozwyn on August 17, 2008, 02:59:38 AM More thoughts/ideas? I'm looking forward to Sir Emi's ofc.
Title: Re: No inactivity on local processes Post by: Moen Co. on August 17, 2008, 08:10:11 AM I like the idea, except for IP change/password change, although I don't think anyone would let a queued IP/password change time out unless they went on vacation or something.
Title: Re: No inactivity on local processes Post by: Crlaozwyn on August 17, 2008, 10:58:09 AM Exactly - it just stops players from having to play against the mechanics. Those who IP hop and change pass regularly always have one cued up anyways. If this is the sticking point, then don't include those. With or without those, I think it makes the game more realistic and a bit less irritating :)
Title: Re: No inactivity on local processes Post by: virus man on August 17, 2008, 11:40:21 AM That would be a big one for research, finish a ton of research and have to wait for AP/HPD to finish them and they start to time out... that would suck... Tell me about it ;( Lost over 180 levels on my Firewall because of that stupid gateway bug on it. I like the idea, except for IP change/password change, although I don't think anyone would let a queued IP/password change time out unless they went on vacation or something. This is why the inactivity was started. Because of people leaving up IP change and/or Password change to use up CPU/RAM and prevent virii etc from infecting their systems. As for it timing out. I do all the time ;) But that is because I tend to keep both up all the time on my main server. Title: Re: No inactivity on local processes Post by: Moen Co. on August 17, 2008, 02:55:08 PM Quote This is why the inactivity was started. Because of people leaving up IP change and/or Password change to use up CPU/RAM and prevent virii etc from infecting their systems. As for it timing out. I do all the time ;) But that is because I tend to keep both up all the time on my main server. That seems like less of an issue now that the average player's hardware is much higher than the resources taken up by either. Title: Re: No inactivity on local processes Post by: Crlaozwyn on August 20, 2008, 10:05:21 AM Yep, there aren't many reasons to have local processes time out, other than irritating us :)
Title: Re: No inactivity on local processes Post by: Andreas on August 20, 2008, 10:08:17 AM An inactive account with one or more running processes should slow the servers down. Unfortunatly it also concerns the local processes as well.
Title: Re: No inactivity on local processes Post by: Crlaozwyn on August 20, 2008, 12:46:28 PM Why would inactive accounts affect the servers? Since they're inactive, no one will be asking the server for the info.
Title: Re: No inactivity on local processes Post by: Theraze on August 20, 2008, 02:25:12 PM And if this is actually an issue, how about making it so that if the account isn't logged into for 7 days, THEN inactive local processes time out. Takes all of a single extra line in the code, since it's already checking time not-logged for newbie protections...
Title: Re: No inactivity on local processes Post by: Andreas on August 21, 2008, 08:13:36 AM That is a good idea. I agree on this suggestion.
|