I ( a warrior, with proper gear) just finished Balder's and requeued, and miraculously had an invite 10m later from a group in progress. I immediately got kicked from their guild group for some unknown reason. After being kicked, I had an hour cooldown on the dungeon. Why does the kicking CD even exist, and why isn't there some system in place to discourage guilds from doing this? Who the hell thought this was a good idea, and for what reason, anyway?

yes this happened to me to, from a semi full guild except one slot and guess what?

They had cleared everything but last boss and decided it would be fun to get people in and kick them out over and over.

I had my instant CD on top of waiting for another 2 hours for Instance matching once it was over........

That needs to be fixed

Quote: LOLtex on 06/04/2012, 12:41 AM - view
I doubt they thought. That's the problem here. The programmer is only as good as what he is asked to program. If they did not consider the case where people are inviting you to kick you, it won't be accounted for.

I've had similar happen to me as well, being kicked before even getting to type out a greeting. Part of the problem (though not the source of every instance of this) is that parties have gotten smart to the bonuses of LFD and want those, but without dealing with the randoms. So they make a 4/5 party with a 5th person already planned. The 4/5 go into matching as a party at the same time as their single 5th. The party then kicks anyone who hits that open slot until their pre-selected 5th gets in, since both going into matcher at same time doesn't guarantee they'll be paired first time.

There needs to be a way to discourage this practice or look at lessening the effect of the cool down timer if kicked, based on how long you even got to be in the zone. There are times when kicks are needed realistically, but someone who didn't even get to do anything in the zone shouldn't be punished with cool down and be allowed to re-queue immediately.

Quote: Ahmon on 06/04/2012, 12:52 AM - view

Basically this. As a programmer you don't add more than what's needed. Coding is exactly like building a house of cards. You change one thing, something completely unrelated can be affected. Also it really depends on how the game was built. If the devs had already put an on off switch for CDs, then they can just flick it.

However, if that hasn't been done, something as simple as removing a cooldown for being kicked could take 1 line of code or a 100 lines of code. It's easy from out perspective to demand something. But if you don't know what goes into programming something simple such as tic-tac-toe, then understanding something on a grand scale such as Tera would be daunting to wrap your mind around.

First it has to be an acknowledged problem by the devs. Then it has to be put on a schedule to when the fix needs to be done along with meetings on how and what not. Then the fix has to be done.Then there is also a testing phase to make sure the code does what it suppose to do. Then see how this one fix affects other new fixes being rolled out at the same time. Then it gets released but in turn something else is wrong now that wasnt caught in QA. It's one big mess.

I took a 2 semesters of java programming in college, and I hated it. And we were only doing simple things (looking back they were easy) and had trouble with that. I can only imagine what BHS/EM has to do.

Quote: gex2k1 on 06/04/2012, 01:13 AM - view

If that were the case then we wouldn't have a lfd at all

Quote: Bringer on 06/04/2012, 01:58 AM - view

What he meant was programmers coded what they have been told, not to make some tweaks that they weren't told to do. This is suppose to be the Project manager's responsibility to plan this outcome, which he clearly did not think of this outcome. Nevertheless, changing this shouldn't be quite difficult, if it's written in OOP, if this is not the case then...Good luck to the dev...

I know, i saw the opportunity to make commentary on the game though so i took it.