Posted - 2007.06.30 14:33:00 - [31]

 

Edited by: Manic Smile on 30/06/2007 14:32:08
Yes we do. We want a lag free, or at least reduced game and we want to be able to go afk for however long we want, short of DT. Seems pretty simple in concept to me. The rest is CCPs business to figure out.

Posted - 2007.06.30 16:49:00 - [33]

 

So i've herd a good reason or 2 for having logg out timer, but no good one for not having one. Well other then just it would be a bad??? Bad for what really?? Don’t really under stand why if you’re not playing then why are you on line??

The only thing I think people are worried about is that they can’t sit cloaked AFK all day in some one else’s space. If the timer is 30 minutes or an hour long then AFK travelers and normal fleet lag issues won’t be an issue at all. Either your playing the game or not, if your not then bye.

No one cares if the ebil cloaked ship in local is keeping us from farming if that player is really playing the game instead of just sitting there AFK for days and weeks on end.

So if you chose to use that tactic then you will actually have to be there to facilitate it not just logg on and then go farm your self on a 2nd account. If you can’t handel that because it’s boring then perhaps you should not do it, its self critiquing

Posted - 2007.06.30 18:03:00 - [35]

 

They already have this implemented, it just isn't turned on. Except for select systems, there is little reason to turn it on.

Posted - 2007.06.30 18:23:00 - [37]

 

Edited by: Keira Fordring on 30/06/2007 18:24:29

Originally by: Tivookz

---

Edited by: Tivookz on 30/06/2007 11:15:45

Originally by: turnschuh

---

lol

you realise that if someone is AFK he doesnt create load at all?

worse idea ever.

---

Quoted for lies.

For each new person in Jita the server has to send and update the local chat for each and everyone anyway, no matter if you're afk or not.

And if you're afk in space you're still sending positional data to the server, so yes, afker's create load.

Tiv

---

In the case of chat updates, wouldn't it be better to let us close the stupid chat windows? When I'm in high-sec, I could care less what goes on in Local and 99% of the time I don't give a damn what's being said in n00b corp chat either.

Rather than having to update 1000+ chat windows with data nobody reads, it would reduce server load considerably if it only had to send the info to people with the window open.

As to being AFK in space, you send very little data to the server while idle. The only time the server needs to update your client is if your camera changes position, you issue a command or an event happens within visibility range (ie: a ship passing by, an explosion, etc.)

Also, the server load would most likely increase due to all the people that were auto-logged trying to log back in. Sure the authentication server is separate from the game server but as soon as you authenticate, the game server has to load your entire environment. A flood of people relogging would be more detrimental.

Auto-logging people who are AFK will only open the client up for more bugs.

Posted - 2007.07.01 01:15:00 - [39]

 

Originally by: Keira Fordring

---

Edited by: Keira Fordring on 30/06/2007 18:24:29

Originally by: Tivookz

---

Edited by: Tivookz on 30/06/2007 11:15:45

Originally by: turnschuh

---

lol

you realise that if someone is AFK he doesnt create load at all?

worse idea ever.

---

Quoted for lies.

For each new person in Jita the server has to send and update the local chat for each and everyone anyway, no matter if you're afk or not.

---

In the case of chat updates, wouldn't it be better to let us close the stupid chat windows? When I'm in high-sec, I could care less what goes on in Local and 99% of the time I don't give a damn what's being said in n00b corp chat either.

Rather than having to update 1000+ chat windows with data nobody reads, it would reduce server load considerably if it only had to send the info to people with the window open.

---

Chat is multicast traffic. Multicast stuff doesn't increase node CPU use, it just increases network load on the edge server, and CCP have said several times that network load isn't the problem. The guts of it is that the node doesn't have to think about sending the chat to each individual player, as far as the node is concerned there is only 1 message and the edge server deals with farming it out to all the connected clients.

Where life gets laggy is when the node has to think about stuff, like the bazillion market transactions going on in Jita every day, or the AI of all the NPC's in motsu, or all of the collision detection, weapons fire and gang bonuses in fleet battle.

Posted - 2007.07.01 13:21:00 - [41]

 

The only remotely legitimate argument against "AFKers" was that they "eat up" system resources.
It was shown that they do that, indeed, but the amount they use is minuscule, so there's no real incentive to "boot" them "for the good of the game".

The true and actual reason people whine so violently against people that stay AFK is that of (usually 0.0) inhabitants that see the face of an AFK cloaker all day long in local, and never really know if that one's really around, or there. So, instead of making abstraction of that cloaker KNOWN to be AFK (and, well, risk losing ships that go out unescorted), they keep on complaining AFKers should be auto-kicked.
How's this for a rebuttal: cloaked people should VANISH from local.
Let me see now how you handle it. From a chicken's point of view, every system now has an AFK cloaker in them.

I call this attempt at kicking AFK people what it is : pathetic.
There's really nothing else at work here but the needs and wants of those that were ever (or fear of ever being) in contact with an AFK cloaker.

Posted - 2007.07.01 15:32:00 - [43]

 

Originally by: Akita T

---

Bad for traders that just want to ckeck some of their orders.
Bad for gang-boosting alt chars sitting in a safespot doing nothing else but that.
Bad for people training several lower half-hour/hour-and-a-half skills.
Bad for CEOs that want to have logs of their corpchats.
Bad for POS-shield-repairing alt chars.
Bad for alt chars in freighters setting up POSes.

Want more counter-arguments ?

---

#1 reason it will NOT get implemented.

CCP is fairly proud of their players online statistic, its counterproductive to them to kick off 5000 afk people who are docked in a station not using up much bandwidth or resources.

Posted - 2007.07.01 17:07:00 - [45]

 

Quote:

---

Bad for traders that just want to ckeck some of their orders.
Bad for gang-boosting alt chars sitting in a safespot doing nothing else but that.
Bad for people training several lower half-hour/hour-and-a-half skills.
Bad for CEOs that want to have logs of their corpchats.
Bad for POS-shield-repairing alt chars.
Bad for alt chars in freighters setting up POSes.

---

To add to those comments...

Bad for noob mining with industrial ships.
Bad for Pos bashing
Bad for Miner guard
Bad for scouting
Bad for AUTOPILOT
that means.. bad for traders, bad for haulers

Least but not last. The docked pilot adds a very small amount of load to the server, since he is not involved in combat or anything. On the other hand not being afk adds to the problem.

Posted - 2007.07.01 17:31:00 - [47]

 

Originally by: Red Crown

---

AFKers present problems for Lowsec/0.0 in the way that they can pin down an entire system using only a velator and a cloak.

---

An unrecognised name in local = "pinned down an entire system" now? I'm sorry, but that is up there with the most absurd statements I've ever read. Whether you have a cloaking Velator in your system or not, you stay alert and you stay alive. Your Dominix friend made the mistake of assuming someone was AFK and paid for it.

On topic, no. How about a gang camping a gate in 0.0? They could quite easily not need to interact with the client at all (beyond reading the overview), so would appear AFK to this timer system.

Posted - 2007.07.01 17:39:00 - [49]

 

No. This isn't WoW.

Posted - 2007.07.01 17:50:00 - [51]

 

Manditory log out? No.

Make it optional, and the default setting, which you can change in a second? Absolutely.

Allow the player to customize the time before disconnect? Even better.