Big problem with the system
[DUEL] I just realised that if you lets say kill someone 2-3 times within like 1 minute and they basically get a shit start. They can just leave the match and they NEVER lose any points cause they abandon too early or something. This is really annoying, please change it so that if you leave within any fucking time you lose the match and should lose points. People abuse this way to hard. PLEASE fix it.
Thx!
Im gonna show you plenty of links later to show you what i mean.
Players are quitting within in that 50% while loosing to avoid a loss completely.
To keep on the subject of abuse, players while quitting ahead on score will end up with a win.
This has made people adopt a style of running for as long as possible while in the lead, till they reach that 5min mark and quit.
It's match must be >= 9:55 OR forfeit.
QL does not provide any means to distinguish between a player quitting or being kicked.
As soon as I add the "quitter/kicked_guy loses" rule, you'll probably see an increase in kicks. Gain an early lead, kick the other player ... win.
But I agree that this is less common than rage quitting, so I'll go for that.
Sure if its like 10 seconds. but the fact that a player can living within like a minute or two and not get loss in duel is beyond fucked up, i hope you realise that.
What I also said is that the data provided by QL does not make it possible to distiguish if a player left the game on his free will or if some mean server admin kicked him.
So, by making this change, I will fix one (large) problem, but will introduce a new (smaller) problem: You get a free win when you kick the other player.
Still the right thing to do, but I just wanted to point out that nothing is as simple as (almost) everyone always assumes.
This is meant for FFA, CA, FT so that players with < 500 dmg or a taken/given ratio > 10 are ignored. Unfortunately this was also applied to duels, so quitting before dealing 500 dmg caused the player to be ignored.
That problem was found some time ago, but the fix didn't work as expected.
I'll be releasing another fix today.