Its been a probliem since 1.0, they did it with the chocobo escorts.
Not surpised its still happening. SE said the would sort it in 1.0 & did a OK job at it, so hopefuly they will have something out soon for ARR.
Its been a probliem since 1.0, they did it with the chocobo escorts.
Not surpised its still happening. SE said the would sort it in 1.0 & did a OK job at it, so hopefuly they will have something out soon for ARR.
Too bad the community here is so against being able to kick someone from dungeons eh? Enjoy your leechers I suppose (or enjoy leeching, if you're really that against it).
I'd just say - put in an AFK timer on dungeons with a penalty to it: if you trigger the AFK timer on yourself while in a dungeon, you are lock from dungeons for 2 days. Then make that timer 10 minutes rather than the normal 30. If someone has to leave, they should leave, not AFK. If you've an emergency and can't even get to the logout button: you have bigger concerns than a 2 day timeout.
Also, people who reque after a group breakup with no bosses down, who are NOT the first ones to leave, should get bumped up in the DF queue.
But my ideal solution would be to let groups that queue into a dungeon stay together and reque together, even if some of them leave - I think that should be in there even if none of the other solutions are, and regardless of whether or not the game gets a votekick system. Couple it with the ability to make cross-world friends and group with them for DF purposes... and you'll start seeing these PUGs turn into mini-communities.
Votekick is too abusable. Better to try other methods for accountability first - like cross server shareable blacklists and the ability to set a flag to not be queued with anyone who has been blacklisted a certain amount more than oneself has been.
I would set it as 'DF only random-groups people who have been blacklisted a similar amount - a range of 10.' and only people who have blacklisted others a similar amount - but a range of 50 on that. And how many times someone has been blacklisted, or how many people (but not who) they have blacklisted should both be visible on lodestone. As well, blacklisting should require typing a reason, 50-150 characters - and the reasons people have blacklisted you also visible on lodestone (with a 1-month ban against anyone who types a name into that reason).
My suggestion is pretty complex... but I've very rarely seen votekick used legitimately in any MMO...
I've also very rarely seen AFKers though. Perhaps the simplest solution would just be to remove from the group and dungeon anyone AFK more than 5 minutes (granted I have seen people who tried to speed run and force constant pulls in a group to prevent this trigger, and to prevent WoW's must wait 30 seconds after combat to votekick trigger...).
Last edited by Makeda; 09-25-2013 at 03:01 PM.
Striving for perfection is the path to one's downfall. 'Tis the paradox of the immaculate carrot. | Jah Bless. One God, One Aim, and One Destiny - Marcus Garvey.
Until the philosophy which holds one race superior and another inferior is finally and permanently discredited and abandoned, everywhere is war - Ras Tafari.
You mean like the people abusing the current system by AFKing or griefing runs with no means to get rid of them aside from eating a 15 minute lockout penalty? That kind of abuse?
I'm pretty sure a 3/4 or 7/8 vote-kick mechanic would not be abused as much as AFKers and griefers currently do.
edit: nevermind
To go with that, I also recommend two more changes to patch up a potential loophole that may harm the good players.I'd just say - put in an AFK timer on dungeons with a penalty to it: if you trigger the AFK timer on yourself while in a dungeon, you are lock from dungeons for 2 days. Then make that timer 10 minutes rather than the normal 30. If someone has to leave, they should leave, not AFK. If you've an emergency and can't even get to the logout button: you have bigger concerns than a 2 day timeout.
Scenario: You get an AFKer who uses say mouse hardware macros to avoid the AFK penalty. A tank decides he doesn't want to deal with this and leaves dungeon. Now you're stuck waiting for tanks and as a Tank myself, I know that I never bother to click the "join in-progress", for the simple reason that most of the in-progress parties end up with me and another person, and we get to wait even longer.
1. In-progress parties only "Commence" when slots are full
This desperately needs to be done asap. If you keep throwing people into half-parties and force them to wait inside the dungeon, they will not join in-progress again. I used to always join in-progress as tank and healer, but now I refuse to use it, because I rarely get a proper party. I almost always end up dropping it because we're short a healer or there's only another person in the dungeon.
The join in-progress function is broken. Whoever implemented it like this needs to be denied 1 year's worth of karaage-kun.
2. Together with #1 above, make join in-progress compulsory
Except for first timers.
Everyone who's not a first timer will be funneled towards in-progress dungeons first. The key reason is still healers and tanks. Why on Eorzea should i join in-progress as a tank and risk having to wait inside a dungeon doing absolutely nothing but twiddle my fingers, while me and another DDer wait for a healer? So I don't use it.
Whoever thought it was a good idea to make it an option needs to be denied 1 year's worth of karaage-kun, too.
And please send the total of 2 years of karaage-kun in weekly packages to my home address as recorded in my member details. Thank you very much.
It was designed more as an assurance than to be effective. And indeed, together with the server upgrades, I've not had any 1017s now.
It is funny when I keep seeing FC buddies find out "hey the AFK kick doesn't work if you do xxxx" all the time. :3
“There is nothing noble in being superior to your fellow man; true nobility is being superior to your former self.”
― Ernest Hemingway
that lonely person on that run is an AFK PERSON.
i was in CM today and some1 was afk , we killed 1 boss , the tank said screw that im not going to run this for some1 that is afk....and left , after 1 tank left , every1 started leaving....i was wtf just happened?
so i was there talking in FC chat about it , when some1 joined and saw that we were 2 and left inmediatly...another 1 joined and left .....i decided to quit , but guess that instance with that lonely AFK person was joined by lots of ppl afterwards.
All the more reason to get your FC or run pre-mades. Damn, this sucks. I can't believe it's come to this.
"Swift as the wind, silent as the forest, fierce as fire, immovable as a mountain..." - The Furinkazan
- Kyodai - Hyperion Server -www.clan-kyodai.com
I hate to say it, but why would you ever bother trying the dungeon if someone is afk? I'd just ditch the guy, eat the timer, and go on with my day.
Problem is, the first person to abandon a duty is locked out for 15m.. the rest aren't, but the first is. No one wants to have to lock themselves out for 15m when it's someone else who should be suffering a penalty.. This is especially bad for DD's who already have long queues as it is, they don't need ANOTHER 15m added to their time after already waiting at least that much just getting into the instance to begin with..
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.