Provisional Divisions, Schedule, Rules Changes and Feedback

Date January 16, 2012

Provisional Divisions

Voilà. A link to the feedback thread can be found below.

S11 Map Schedule

  • Week 1 – cp_badlands and cp_snakewater
  • Week 2 – cp_snakewater and cp_gullywash_final1
  • Week 3 – cp_gullywash_final1 and cp_freight_final1
  • Week 4 – cp_freight_final1 and cp_granary
  • Week 5 – cp_granary and cp_badlands
  • Week 6 – cp_badlands and cp_gravelpit
  • Week 7 – cp_gravelpit and cp_gullywash_final1

Playoffs

Playoffs will be held between March 18th and March 31st. Write it down, cancel all other engagements, consider yourselves notified.

Premier Division Playoffs

  • 4th vs 3rd: March 18th – March 24th
  • Winner vs 2nd: March 25th – March 31st or sooner
  • Winner vs 1st: April 1st – April 7th or sooner

Changes to the Rules

In preparation for Season 11 we have updated the etf2l config and had a look over the rules. Some rules are still being discussed, any further changes we make will be announced at a later date.

Config changes

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.

You can download the config here. The config is always available on the rules page.

Rules changes – League rules:

  • Updated to Season 11 Rules – Title, map pool, map schedule.
  • Banned the Bombinomicon

General Rules:

  • Edited: 1.4, 3.2, 3.8
  • 1.4 Use the match comments to record agreements on mercs, servers and other cases

    We encourage using the match comments to keep in touch with an opponent. Any agreement between two teams regarding the use of mercs or servers must be recorded on the relevant match page. If anything requires verification it MUST be documented either by a screenshot of the original conversation or by leaders from both teams providing confirmation in the match comments.

    If your opponent allows a merc, you are expected to extend the same courtesy to them.

    3.2 Status & Scoreboard screenshots required

    One member of each team has to take a status screenshot before a match is starting and after every player switch. A screenshot of the final score has to be taken at the end of every map/round. 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. When submitting the result, a team leader has to upload all relevant screenshots.
    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.

    3.8 Teams may request a pause if problems occur

    Teams may request a pause at any time during a match. Reasons for pausing can include:

    – Player drop

    – Server problems

    – The match is unplayable due to network issues

    If you need to pause, you must clearly request a pause and give a reason for it (for example: “Pause please, player drop”). The other team is then required to pause at the first appropriate time (e.g. not in the middle of a push). Teams must pause within 15 seconds of being asked. Not responding to a pause request will lead to penalties like a minor warning accompanied with the forfeit of the round in question, or, in extreme cases, a major warning and forfeit of the map.

    You may not resume the game under any circumstances without giving proper warning to the other team.

    Each team has the right to one pause per map.

    A pause may not last longer than 5 minutes.

    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.

  • Added: 6.5, all of 7.
  • 6.5 VAC Bans

    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.

    7. Admins

    7.1 Requesting admin help

    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.

    7.2 Admins on the staff page

    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

    7.3 Admin discretion

    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.

Feedback

As always we appreciate any feedback you can give us. Post your thoughts on the rules, unlocks, provisional divisions and the poll system in the appropriate thread.

17 Comments

  1. Koeitje: AUTOBOTS said:

    Looking forward to 20 minute rounds.

  2. Permzilla: (Legend) - (☞゚ヮ゚)☞ - WiK? said:

    “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.”

    inb4 everyone who used AnAkIn’s plugin gets VAC’d :D

  3. Dr-GimpfeN: 9g1c said:

    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.

    wtf????

  4. Faraday: Foust - UBD said:

    was whitelist updated?

  5. Califax: dyn. said:

    On behave of the Eyefinity users i’de like to thank ETF2L for their wisdom.

  6. Tenshi: 50829 said:

    Why ban the Bombinomicon?

  7. Dr.KriPtz: |LP| - A4 said:

    this is gonna be good!! :)

  8. r7an: -9w- said:

    nice merc rule, but how will this be enforced? people can still deny a merc and make you play with 5 and escape punishment?

  9. Paul: CotC said:

    Yeah pretty much what r7an said : /

    never forget …
    http://etf2l.org/matches/26908/

  10. Buffalo Bill: TDR » - T⑨ said:

    We try and prevent people from lacking sportsmanship as much as possible, but not everything can be fully covered by rules. Because of that we also added the “admin discretion” rule (rule 7.3). No matter how much we like to we can’t prevent it 100%, unfortunately, but that rule allows us to deal with it as best as we can.

  11. CanFo: (Legend) - [HA] - #T4F said:

    If your opponent denys you a merc although you allowed them to use one you could, for example, ask an admin for clearing it up. A possible solution would then be that the admins either revoke the approval for the merc of the other team, allow a presented merc or just give a warning to the team being a d*ck but every case needs to be discussed seperately. I hope it never comes down to this, of course.

  12. SiriusA: [ˈχʊχːiˌχæʃtli] said:

    All the Fakkelbridge links are broken. That means etf2l config and the Config pack too. I hope you will fix it soon.

  13. CanFo: (Legend) - [HA] - #T4F said:

    SiriusA: Links are working for me.

  14. SiriusA: [ˈχʊχːiˌχæʃtli] said:

    CanFo: Ok they’re back now. Looks like chris managed to fix his page :)

  15. skeej: (ETF2L Donator) - UbeR | - Fe | said:

    @ Califax: And on behalf of the windowed-widescreen users i’d like to thank ETF2L for their wisdom too. Problem is that every non-etf2l server is still set to “1” though… oh well…

  16. Retsh0ck: 32erz - 2strong said:

    please get rid of freight, please, I beg you

  17. Gas13: niveous. said:

    Div 5B is funny o/