March 8, 2010
Pushing the community forward
Our partnership with EsportsHeaven continues with the 128 team Sapphire Challenge with €500 up for grabs.
While that partnership is strong, it is also a growing one, and we still need your support and participation. So, if you’re able to play on the evening of the 15th of March, make sure you sign-up today!
We’re also very excited to tell you about an upcoming Highlander tournament we’ll be hosting in association with Valve and TF2Lobby for new to competitive play teams. Expect details about how this involves you in the coming week!
Also make sure to check out the second episode of The Direct Hit podcast, “Who the hell decided to go valley?”, where the team takes a look at what’s wrong with competitive TF2 and how we can put a positive spin on it.
Rule changes with immediate effect
- In response to the awesome Fraglander frag movie by Sammage, we have been forced to rule that the kind of turning scripts demonstrated in his video will be banned in ETF2L play.
- After a number of issues with pauses in matches recently, in both ETF2L and the ESH cups, we are changing the pause rule to the following
Teams may request a pause at any time during a match. Reasons for pausing include:
– Player drop
– Server problems
– Your game 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, by rule, expected to pause on behalf of their opponents in a sensible and sportsmanlike manner. They must pause at the first appropriate time.
Teams should use their common sense about what an appropriate time to pause is. Try your best not to pause when major engagements are taking place. You should pause within 15 seconds of being asked.
If a complaint is made that a team was either abusing the ability to request pauses to gain an unsportsmanlike advantage, or a team failed to fairly pause or took excessive time to do so after being clearly requested to pause, the admin team will review the supplied SourceTV demo and assess penalties on a case-by-case basis. Penalties include minor warning accompanied with the forfeit of the round in question, or, in extreme cases, major warning and forfeit of the map.
A team is only expected to pause on behalf of the other team once per map. After the first pause has been used, it is up to the other team whether and when to pause or not.
A pause cannot last more than 5 minutes. After 5 minutes have passed, the other team is free to unpause the game without the other team’s agreement, as long as they let the other team know that they are about to unpause. We advise teams to use the 5 minutes wisely: sort out whatever problem you have and arrange a sub from your roster in case the problem cannot be fixed.
You may not unpause the game under any circumstances without giving proper warning to the other team.
- Following the results of the Obscure poll, cp_obscure_rc2 will be used in all future games until further notice.
- Please also note that several teams have fallen foul of the rule regarding the use of mercs. You must have the other team’s permission to use a merc, and all mercs must be registered with ETF2L. It is your responsibility to check this, not the other team’s. There will be no exceptions.We also advise, as always, that you get your opponent to agree to allowing your merc on the relevant match page. It’s also a good idea to screenshot their agreement (if it’s agreed in-game or through Steam chat/IRC) too.
Changes to the admin team
We regret to announce that we’re removing long-time volunteers Amonsilas and Weqo from the admin team due to inactivity. We thank them for their services to the community and wish them good luck with their future plans.
We have also taken the decision to relieve Anakin from his role in the anti-cheat team. An unfortunate conflict of interest has arisen with his position as ESL admin, and it was, in our estimation, effecting his performance in his duties with ETF2L. We are very grateful for his hard work and wish him all the best with regards to future ventures.
Following Anakin’s removal, the anti-cheat team is seriously understaffed. We are in the final stages of approving new members, who we hope will formally join the team within the next few days.
In response to allegations against anti-cheat team
Following an internal review between the head admins, anti-cheat and league staff, we have decided to uphold the anti-cheat team’s decision regarding Quad’s ban, as detailed on February the 8th. They have fully explained their decision and they have the full support of the head admins.
Due to the seriousness of the allegations made against the anti-cheat team, we have taken the decision to make an exception in publishing details of our anti-cheat team’s report.
Ticks 3000-4000: Unusual movement, microadjustments of crosshair.
4400, 5600, 5950, 6700: Kills with unusual crosshair movements and patterns.
5100, 5800: Also potentially suspicious kills
Please keep in mind that we do not release this kind of information for a reason. While these instances may look innocuous to you, it is the judgement of our anti-cheat experts that they constitute evidence of cheating.
Considering Gryzor’s behaviour towards our league and exercising his personal vendettas against certain members of our staff in the name of “improving” our community, it’s difficult to take his word seriously. Nevertheless, be assured that we took the allegations he made against our league very seriously.
For those reasons, however, and his leak of confidential admin information that he obtained through his previous role as ETF2L staff, we have taken the decision to exclude him from our community for a year.
It’s very important to us that our admins, people in positions of trust, do not abuse their role. Any admin, past or present, caught leaking information will be subject to the same penalty.
Gryzor – Leaking confidential admin information – 1 year ban
Hastaloe – Speedhack – 1 year ban