Flo

Well, I reverted back to original version following the feedbacks. It means it removes: - randomization of player to be balanced - no move feature below 3mn left duration - announcer to encourage self balance due to massive damage difference between teams

Ok let's try this idea. I added a condition to deactivate the autobalance when there is less than 3 minutes remaining on the map. Also takes into consideration the time bonuses. Let's see if it helps and don't hesitate to bring new feedbacks.

I like this idea. However I'm not sure it covers the situation where teams are not unbalanced by numbers (e.g 10vs11) but stacked/unfair, and one good player wants to join other team to try to balance the match. The hard part is to discriminate a player that is willing to balance the match but will be forced to move back to stronger team as soon as autobalance is triggered by -2 number. The ETL version is moving the last player in the table, and table is populated upon et_clientSpawn callback, by order of appearance so you're right laggers come last at beginning of the map. Original version: playerForcePutteam( playersAllied, playersAxis, playersAllied[ numPlayersAllied ], "r", "^1Axis" ) Current modified version on main server: local randIndex = math.random(1, numPlayersAllied) playerForcePutteam( playersAllied, playersAxis, playersAllied[ randIndex ], "r", "^1Axis" )

First of all, thanks for feedbacks and bringing them here so we can discuss and keep track of what is needed in the end. I do confirm the autobalancer script was modified, the 24th of June this year. The logic of the former version of the balancer script was basically to populate tables in order of appeareance of players joining teams. Then it moves the last one in the table when it kicks in. So it was always switching the player that joined the team the last (new player, or already-switched player). We changed to a total random method instead. The culprit that we tried to address was the fact that when strong players/TM members/friends were trying to balance a map, they were very likely to be switched back to the other team as soon as teams are unbalanced in terms of numbers (-2 less in one team). I understand your point tho. It's very hard to always find good balance when tweeking this game. When you try to improve a situation in one side, it alters another one on the other side. I'm all happy to listen or discuss about any idea that could cover these both situations or improve the server on that topic.

Idea is interesting but I fear it could be too intrusive into the map design. Some maps are already protected by invisible roof like on erdenberg or have an invisible glass against heavy weapons only like in beach invasion through mapscript only, want to stick to the public map pk3 so no need to download a custom version of a popular map when joining our server. Also we tend not to overdo that everywhere, not willing to alter maps too much, we prefer to manage things externally with scripts protecting the spawn areas and managing the kicks and bans to control the server.

Hello, I remember your case. You were pissing off all server with your mortar all day long and were pretty proud of this, taunting other players. That's because of players like you that we modified the server. Indeed it's no more possible to stand mortar in protected areas, was too unfair. Also, the rules changed and you'll find rule 18 covering the fact that it is no more allowed to exploit mortar the way you were doing it. I don't know what happened for your kick but I believe the admin who kicked you already had in mind your past behavior with this mortar and your proud intention to piss off all server with this weapon. We don't tolerate such behavior anymore, fun is for everyone, not only for you.

Your nickname in game?

whitelisted

Hi, can you elaborate a bit more? Do you mean having textures directly inside the map? because as of today the sk areas are already integrated to levelshots, i.e command map and limbo menu Thanks

Try to put the cvar in server.cfg instead. Also, I guess the path is case sensitive, gotta take care of the actual name of targeted database, example on our server with standard db name: set n_SQLiteDBPath "/xxx/xxx/xxx/xxx/nitmod/NITMOD_DB.sqlite"

Yep c'est pas faux. Considérant que j'entends beaucoup trop parler de lui tous les jours et qu'il a déjà subi un ban par le passé, on va dire que c'est la goute d'eau qui fait déborder le vase. Je viens de lui remettre 3 mois dans les dents, ça lui laissera une dernière chance ensuite si il veut en bénéficier... ce qui semble loin d'être garanti...

Yes, if you have several etkeys for same IP, you'll have the same issue with etkeys not whitelisted yet.

Hi, you're whitelisted now. Don't change your etkey

Hello, it's OK now you have been whitelisted

Hello, I guess you didn't see fuel dump on our server history because we were using the summer version so far from time to time. Anyways i added original fuel dump version to the map rotation. Thanks for suggestions.