Guild Wars 2

Dear Anet,

Earlier today, during a Tequatl raid, I went through all night, trying to help Sanctum of Rall down the beast. When time reached 8-9 AM locally (some five hours earlier from now), I accidentally fell asleep. Yet, even though I wasn’t active for about four straight hours, I didn’t get disconnected! Thankfully, it was way past America’s bedtime, so I wasn’t clogging that much space on a extremely high server demand, but still, I find it highly problematic these days, due to guesting and map-space requirements.

I know I ruined somebody’s day somewhere by making them stuck on overflow, while I was sleeping and my character clogged up the map, standing uselessly, getting killed a lot and wasting precious manpower on good folks trying to get me up again (for which, I apologize to my gaming mates).

There was no pet or child present on my table to keep me “false active”, my mouse or keyboard weren’t touched for that time, yet I miraculously didn’t get disconnected after four hours of standing around, not moving, not writing, not doing anything. That needs fixed ASAP.

If you are frequently tired enough that you fell asleep at the keyboard or went afk and fell asleep in a different room then you should have logged out yourself since you would know it would happen.

I personally hate the afk timer in the game, especially when I tab out to read the wiki or something. If I need to go make dinner or something then I like to sit in LA and read the map or guild chat when I get back but I always get booted after 10-15 minutes, whatever the timer is but it is a pain.

I would like to see an option where you could set an afk timer, that would be perfect for people who are susceptible to falling asleep at their keyboards. I would definitely turn it off or extend it to 1-2 hours so I could come back when ready. What is the point of warping somewhere safe or to LA when I get kicked in a few minutes of not moving. I will log out if I am not going to be playing for over an hour.

Yeah, if I knew I was going to sleep, I would have logged out, trust me, I’m not that much of an idiot. My computer doesn’t handle running this high powered app well, either. Human body, at least mine, doesn’t exactly have a screen or monitor that would precisely tell you “sleep imminent and unavoidable in 10 minutes, close all apps and prepare to assume a horizontal position.”

And sorry, but being still in-game after FOUR kitten HOURS is either a bug, or a really bad idea. Or both. Because if you leave for that long, you have no right to clogg the map for someone else. Hell, even an hour is too long. 30 minutes are max in my opinion. When the game counts participating in map chat as inactivity and threatens to boot you when you just write in guild chat and not moving, then this shouldn’t happen at all.

Being attacked or downed and revived etc reset the afk timer.

I went afk (cant add ‘ed’ onto afk, stupid filter) near the old giant farm on steps of arah, came back 4 hours later not logged out, but naked. I thought I was in a safe spot, heh :p

@Have No Faith In Me (Is it bad that I do, for your informed answer?): Thank you. Good to know, I will warn people from it on raids. Not rezzing AFKs.

Still, the timer is ridiculously long on the Tequatl event – when Sanctum of Rall downed him, he caught us with our pants down, spawning after 45 minutes instead of 1h30 he usually takes. Lot of people were AFK, standing on a safe spot, not getting killed for those 45 minutes. That’s way too long, especially on high-server demand events.

Well – for dungeons (solo runs), fractals, personal story, and SAB the ability to idle is important. There were a few times in personal story and SAB where I would have to do something else for around 30 mins to upwards of 2 hours and didn’t want to lose my progress. This is especially true for SAB trib mode, or even SAB achievements, where if you get booted or log off you lose progress (trib mode takes me around 2-3 hours in the first go to do, I rather not have to spend that time doing the level again).

I’m not saying that open world should be subject to instanced rules, I’m saying idling should be allowed for instances but not for open world. At least in open world everything is persistent – you won’t lose progress on something except for the dynamic events.