www.iziservers.com

Some maps would really get easier to vote/play, if the losing team could forfeit the match then the game gets too lopsided.
Maybe the best example of this is overkill, where after things get lopsided the meta changes and play gets eeeextremelyyyy slow, resulting in endless pain for everyone. Especially when thinking about the morale of the losing team.

This could perhaps be eased by having a forfeit happen when 80-90% of one teams members writes !forfeit. That would make the end a bit snappier, resulting in gg

ofc there needs to be some reset events for the votes, so it doesn't trigger by accident after some time has passed and everyone has forgot about it.. too many switches, specs, 1min timeout maybe?
No admin veto/forcing, democracy ftw.... err lose!

this could work, i will look into this asap. it needs some reprogging of custom votes, im on it asap x

maybe i should consider also a score treshold , like a min score diff should be 6 or 7 or smth ?

or forfait should be votable if eg 1 team hits 7 ?

Is score diff of 6 enough of a constraint?
That would leave 0-6 and 1-7 so forth on the table.

Super hard to say how ppl behave before testing and It's mostly about the team anyway, if the forfeit needs a lot of votes from the team.

And big thanks for looking into this )

issues found. there is no command or gamehook in qlive/minqlx to end a game or alter the teamscore.

we have 3 options :

1. lets say score 6-0, losing team call forfait. we set roundlimit temp to 7 and finsih the round to end the game.

2. we put all players iin spec for instant forfait and game end. imo not so fair for the few ppl who didnt want the forfait.

3. we do an instant map_restart but that way the game isnt ended, no gamereg on qlstats , no elochange.

For sure dropping the roundlimit sounds the least hackish way here.
That would actually result in the normal game ending with result counted (hopefully) in qlstats etc.

altering the roundlimit would do the trick but never gives the feeling of an instant forfait imo. espec if there are a few campers that just sitting out the round.

map_restart would punish the winning team because no stats are sent so also no option.

putting all to spec could do an instant forfait, but it looks real ugly

lemme think on it . its like running into a real simpel limitation of ql

I forgot to mention : ql has also a built in mercylimit cvar.
its possible to define a scoredifference and once the diff hits it will end the game instantly.

example: if mercylimit is 7 then the game will end at 7-0, 8-1 or 9-2 (im not sure if elo is counted but i think it accepts Arank with 7 rounds)

when game is ended it will say : mercylimit hit.

It does sound actually better than roundlimit!
Then test activating the mercylimit on vote?

However, having constant mercylimit at 7 sounds a bit dull, not that plz. Sometimes ppl want to keep playing a -7 game.. Comebacks are SWEET!!