Forum

– This is the place to give the admins feedback regarding the two new rules.
– The thread will be closely moderated and punishments given out relatively easily. Keep it civil.

Config update
– sv_restrict_aspect_ratio_fov 0 has been added.
– Comments have been added to various parts of the config, to clarify the purpose of commands where we feel it necessary.

Rules to improve fairplay
There have been cases of extreme unsportsmanship in the last 6v6 and highlander season where, for example, a team did not allow the same number of pauses they have been granted or did not allow their opponent a merc aöthough they have been allowed to use one. To prevent this we extended the merc- and pause rule.
– If your opponent allows a merc, you are expected to extend the same courtesy to them.
– If your opponent allows a pause longer than 5 minutes or more than one pause you are expected to extend the same courtesy to them.

Screenshot rule revision
The screenshot rules have been revised. We never had a clear policy how to deal with missing screenshots and even some admins have been confused about that. From now on, admins will verify a result one week after it has been submitted if the opponent did not do it yet. Only in this case missing scoreboard screenshots will be punished with a minor warning for each team.
Also, it has been requested that the matches a player played in should be shown on his ETF2L profile page. In order for this feature to work properly, it is required that you upload a correct status screenshot for every match. To achieve this we will enforce a much stricter rule on missing status screenshots.
– Please note that a scoreboard screenshot is not sufficient for all attack/defense maps as it does not show the winner – the screenshot explicitly declaring one team to be the winner is required instead.
– If one or more score screenshots are still missing after one week, and the result has not been verified by the teams, both teams will receive a minor warning.
– Missing status screenshots will be awarded with a minor warning no matter if the result has been verified by the teams. The second violation of this rule will be punished with a major warning and one point deduction.

VAC ban policy
Players with an orange box VAC ban will be banned for one year. This rule is active from March 15 2012. We will not change steam IDs of VAC banned players anymore but instead ban them for a year. We do not care if it was your brother, your mother or your dog who cheated on your account – you are responsible for it!
Players caught avoiding a ban by creating a double account receive a 2-year-ban. When the ban runs out, they may request a change of the steam ID.
– As of March 15, 2012, any player with a VAC ban on the Source engine will be banned for 1 year. Players with VAC bans that do not apply to Team Fortress 2 will not be affected. Players receiving VAC bans before March 15, 2012 will not be affected.

Admin section in the rules
We added some rules to explain the use of the IRC bot and the roles and responsibilities of the admins.
Since we had a problem being bound to the rules many times in cases where one team exploited the rules in their favour, we added some kind of “safe guarding clause” that allows the admin staff to make decisions that are not covered by the rules. Please note that all cases where this rule applies are revised by the whole staff and not by one single admin to prevent admin abuse.
– To request help from an admin or to file a match complaint, please join our IRC channel #etf2l on quakenet, type !admin and wait for the next free admin to respond. Please do not add admins on Steam to ask questions or directly query them on IRC.
If you do not have an IRC client installed on your pc you may use our webchat plugin.
– All active admins are shown at the staff page. When requesting help from an admin on IRC you may specify for which competition you need an admin, e.g. !admin highlander or !admin 6v6
– The ETF2L rules are enforced at the discretion of the admin team. Any complaints will be judged on a case-by-case basis and different punishments may be handed out in each case.

Quoted from Dr-GimpfeN

please allow tftrue and add the tftrue settings to the config

Quoted from CanFo

Config update
– sv_restrict_aspect_ratio_fov 0 has been added.

COME HERE YOU BIG SEXY LUMMOX

Hello,

I know, that there are merc rules if your roster cannot be completed by your own members. But was it ever considered, to add a substitute for every team, that is ingame and can join his/her team, if a player has a timeout?

We all see it on every matchday, that someone is timed out, and one team has to play with a lower amount of players for a certain amount of time.

Wouldn’t it be useful, if you never have to worry about such a problem?

PS: I’m aware, that there have to be several restrictions and thoughts on this, to avoid exploitations (i.e. someone died and has to wait 15sec to join, but instead the substitute can spawn instantley, and so on..)

CHEERS!

I mean: Having x+1 players ingame

If a player drops you can request a pause and your opponent has to pause within the next 15 seconds. In the meantime, your sub can start connecting and can join a team when you unpause. This way, you should not play 5v6 for longer than about 20 seconds.
We will not allow a player to sit in spectator mode for the reasons mentioned (the possibility of ghosting). Spectators (e.g. casters) can, however, be allowed by the league, if both teams agree.