Kick cooldown given even when impossible to kick (objective observation, not just a complaint)

One of the problems with the new kick cooldown is that the 3 hour timer is started even when it is impossible to kick.

Here are the steps to reproduce:
1. Have someone collect a collection, but ask others not to make a choice in the group loot
2. Initiate a kick.
3. You will be told that you cannot kick because there is pending group loot.
4. You will still be given the cooldown timer.

Some may say that you just need to watch to see if there is pending group loot. However, this happens even if you yourself have made a selection-- it just takes one of the group to not have voted.

this is indeed a problem

And to think this never would have happened if people didn't kick Spytle.

This is because you INITIATED THE KICK and in the patch notes it DOES STATE if you initiate or vote to kick IF THE KICK FAILS IT WILL STILL START THE TIMER ). The timer DOESN'T START if you vote no.

Hope this helps.

Yes I did indeed read the patch notes before making my post. But I posted because I do not agree that this is how it should work. I suggest that the cooldown should not start if it is impossible to kick the person.
My group encountered this situation when we went to kick a person who was disconnected and it appears that person had not voted on the group loot. This is definitely a way for someone to grief an instance.

It was needed, though. Especially after update 47. People were kicking the low CR people out of low tier content more than ever.

Then really you should have waited for the group loot timer to run out before the kicking. If the person DCed and there is loot that dropped, what happens if the person came back and was kicked and missed out on loot? even if it is a collection, you wait til the group loot timer runs out and if the person isnt back then you can kick. Kicking someone in group loot just isnt nice or fair.

oooh wheres this video lmao

3 hours is way too much. 1 hour would be fair.

Yes, I agree that would be unfair. The reason we wanted to kick that disconnected player was not to cheat him out of group loot. He was done with the instance. Instead of excusing himself he must have closed the game. We wanted to fill his spot.

As previously mentioned in the thread, it is impossible to kick someone if there is pending group loot. The game does not allow it. This was probably made this way for exactly the reason you said. I never asked that this be changed. Rather, I am asking that a kick initiated while there is pending group loot NOT to start the kick cooldown.

If I have already answered the need/greed/pass, I do not see any feedback to indicate that is in progress, just scrolling back through the chat window.

I didn't see this thread until after I posted this
https://forums.daybreakgames.com/dcuo/index.php?threads/votekick-problem.253293/
It can be a loophole to teleport away right when a boss starts since, like how you can't kick during Group loot, you cannot kick during combat.

editops.. someone beat me to it
Apparently this issue exists if someone tries to initiate a kick while still in combat. Because kicking while in combat is impossible, the kick cooldown should also not be started in this case either.
https://forums.station.sony.com/dcuo/index.php?threads/votekick-problem.253293/

I think this does illustrate some edge cases that probably weren't fully thought through.

If a vote is successfully initiated and it passes or fails, the timer should start. If the vote itself is failed to initiate because of group loot or being in combat, the timer shouldn't start. The timer should only start if the attempt to initiate a vote actually leads to a vote. This is not a recommendation to alter the circumstances upon which a vote fails to initiate. Those circumstances are still reasonable.

Regardless of the patch notes, what I describe above is how I recommend the system should be altered to behave from how it is behaving today.

this happened to us last night in HOH. the person we were trying to kick was DC'd (shocker, right?) and we had to wait for them to be removed from the group automatically before we could reopen the instance. Meanwhile, others left the group because they didn't want to wait. Needless to say, the group fell apart and we never finished the raid. This needs to be addressed.

who would vote, 'no', in the case of a disconnect? Throw in the group loot, which the dc'd player cant roll on, but is still counted as someone to roll, and everyone in the group has voted, 'yes' to kick, the group loot prevents the removal of the dc'd player and now it is impossible to kick the dc'd player and you have to wait for them to automatically be removed by the game. --needs a fix.

woah. thats waaaaay to long. why not 30-1h. 25. lol

No it wasn't. 3 hours is a ridiculous amount of time. A certain someone got kicked and now we all have to deal with this crap.

There was evidence of kick abuse in the past, in fact, there were lots of support tickets filed because of it. They took kicking out for a weekend and saw a 2% increase in completed instances, but also found some griefing in the experiment, which showed that kicking was a necessary evil. The 3 hr. cool down is a fair compromise. if you're worried about wasting your kick, because of something like Group Loot, it's a great idea to check your message box to see who got the loot before initiating a vote to kick.

Not really though because you can wait for the loot to be dropped as there is a time limit to vote on loot. If also a vote is started before the loot is given out you can always vote no that way you can still open a vote after the loot is given out. So the intended use is still more functional then before.

This really is a problem granted its rare but this is a problem.What about people who just start farming mid instance ignoring what the group is doing.This happens a fair amount in intergang and rarely in closed instances.Combined with a three hour wait and a failed start up attempt to kick (after asking people several times to pick up collections after we cleared a mob or two) and you can see it really does need to be looked at.