Flo

Watten could be fixed and be added to server. Pretty funny map! Also I added Wurttemberg on server today.

Qu'est ce qui se passe ? explique moi un peu tout ça.

Looks like Watten map is bugged, so I removed it for now. If you have another pk3 file or a link for download it I can try again.

Hello, thanks for suggestions, much appreciated. What we have to keep in mind for our servers is that when we want to add a new map, we need to also add omnibot files (paths, goals, scripts), so they need to be available. Hopefully I could find them for these 5 maps. I added UJE Watten and Etdo2 radar laboratory for now on main server. Will see the other ones later on.

These small range changes are easily catchable also. anyway, any other idea to keep cheaters away is welcome !

Hello, we had to put some protections against VPN users to try to protect servers from cheaters. False positive on your end. You got whitelisted, you won't have any trouble anymore.

Hi, we don't have silent server, but we have a nitmod one with dual SMG setup, and the server config cvar for that is: set g_dualSMG "2"

The issue has been fixed and you should now be able to play!

Hello! let us investigate this situation and come back to you soon

There is a clash between you and Knux since several weeks, and spamming !news is one of the reasons of this clash, among others.

Can we all calm down here and be friendly together please. @knuX please respect our members and overall all players. No need to go mad with language, doesn't bring anything. @Txrki for bad language, you can use mute command first. Also, spamming !news command can be irritating from players point of view, best is not to spam that every map. Thanks.

Hello, it's ok now, we have whitelisted your account. You are free to connect.

Thanks for your feedbacks. This has thus been disabled.

Hi, so we have upgraded our ETL servers from version 2.82.1 to version 2.83.2. They added a fine tracking of damages dealt, including assist mechanism. Along that, a feature to allow complaints upon teambleeding. This complaint makes an XP loss for the victim, and is by default triggered if at least 50% of your HP has been impacted by this teammate. This can trigger many popup, and is a bit redundant with the fact that server already tracks teambleeders, and acts (warn/kick) by itself against these. We would like your opinion on the poll attached on whether we should disable this feature serverside or not. (cvar has been tested and is working) Thanks

Yes indeed I could confirm the bug. It doesn't allow callvote when there are less than 30sec left. I discussed with developers and this is not intended, and hard coded. So I can't do anything on that, there's no cvar or link with any other mechanism. So until they fix this, you either have to shuffle with wolfadmin commands, or callvote before 30sec remaining (current warmup time is 40sec on server).