Prove-It!
Quake III
Quake III
Q3 eFreeze 5v5
Ladder for all Euro InstafreezerZ
Season Dates: 03-21-2010 - 09-21-2010
This ladder is Point based
Invite someone to Join this Ladder
Unable to post or accept challenges on this ladder. See detail below.
Detail:
Not Logged In![ Login ][ Register ]
Sit down results | Next season decisions
Topic: Q3 eFreeze 5v5
Posted By: 333ben
Good evening guys and gals,
The meeting effectively took place this sunday, and I would like to thank all who could attend it.
Several issues have been adressed and the good news is, only one of them was a hung vote. An integral version of the discussion can be found by following this link: http://linusky.free.fr/Private/eFreeze meeting log.txt. No need for further ado so there come the votes' results:
- Should Koko ban be lifted? (YES: 8, NO: 0)
- Should the cl_timenudge range be changed: (HUNG)
1. Keep the current cl_timenudge range (3 votes)
2. New range [-20,20] (2 votes)
3. New range [-10,10] (2 votes)
- Should the GUIDs be forced next season? (YES: 10, NO: 0)
- Should admins/refs be given the right to ask a player to reconnect during a match if there is a lag complain on that player and they agree? (YES: 4, NO: 5)
- Reduce a season's length to 6 months? (YES: 7, NO: 0)
- Should we go back to the old challenging system? (YES: 2, NO: 4)
- Should we force teams not to refuse more than 3 challenges in a row (otherwise, they must go inactive for at least 2 weeks)? (YES: 6, NO: 1)
- Should we forbid a team to make a similar challenge within 1 week once it has been declined? (YES: 7, NO: 0)
- Keep q3lynx as a referee? (YES: 5, NO: 1)
- Keep Ring as a referee? (YES: 4, NO: 3)
- Keep Whitey as a referee? (YES: 6, NO: 1)
- Keep Adam as an admin? (YES: 7, NO: 0)
- Keep 333ben as an admin? (YES: 6, NO: 0)
- Keep doomy as an admin? (YES: 7, NO: 0)
- Keep Svarog as an admin? (YES: 0, NO: 5)
- Should loxotron made an admin? (YES: 7, NO: 0)
There is a vote available for the one hung issue (cl_timenudge range): http://www.fraggednation.com/forum/topic/Should-cltimenudge-constraint-range-be-changed-9558.
The season will start on Monday 21 September 2009 and will end on Sunday 21 March 2010 although the challenging will be open as soon as Sunday afternoon.
The official eFreeze ladders for this season will be:
- eFreeze 5V5
- eFreeze 2V2
- eFreeze 1V1
The administrators/referees team will be composed of:
- Adam,
- Al1en_NQT,
- 333Ben,
- Code,
- Doomy,
- HtK,
- Loxotron,
- Q3Lynx,
- Ring, and,
- Whitey.
Thanks for your time and consideration!
edit: a few mistakes.
[read more]
| Ladder Season: | 03-21-2010 - 09-21-2010 |
| Cash Payout? | No |
| Time Zone: | GMT |
| Challenging Disabled? | No |
| Signups Closed? | No |
| Allowed Declines Per Week: The number of challenges a participant may decline/ignore in a 7 day period without being penalized. Please see the general rules for specifics on Challenge Declines | 3 |
| Ranking Type: | Point Based |
| Challenge Map Selection: | Randomly Generated |
| Challenge Point/Rung Restriction: The number of Rungs, or Points, that a participant must be within to challenge another participant. | 0 |
| Rounds Per Challenge: | 3 |
| Reporting Type: The type of data collected when reporting a Challenge | Score Entry |
| Matches Require a Referee? | Yes |
| Challenge Out Hours: The minimum numbers of hours from the current time to which a challenge date may be specified. | 48 |
| Accept Timeframe Hours: The number of hours allowed to accept a challenge - failure to respond inside this timeframe will result in the system processing it as an 'Ignore'. Please see the general rules for more detail on this. | 24 |
| Same Opponent Grace Period: The number of hours that must pass after reporting a match before the same opponent may be challenged again. | 12 |
| Multiple Challenges at a Time? Specifies whether or not each participant may have more than 1 concurrent challenge pending at any given time. | Yes |
| Team Ladder? Is this a 1v1, or a Team Ladder | Yes, this is a 5v5 Team Ladder |
| Requires GUID? Whether or not this game require a unique ID registered in your profile to play. | Yes |
| Setting Name: | Setting Value: |
|---|---|
| all_forgotten_sec_settings | 1 |
| g_hookspeed | 1400 |
| g_hookspeedpull | 800 |
| fraglimit | 15 |
| capturelimit | 15 |
| g_speed | 400 |
| more coming | soon |
| 1. Behavior | |
|---|---|
| 1.1 | Cheating will not be tolerated. Any player caught cheating will be banned for at least a ladder season, that is, if the player publicly recognizes the act of cheating and publicly apologizes to the community for such wrongful behavior. If the player denies cheating, the ban will be permanent. Note that any team having a cheater in it may see its matches results voided on all matches in which the cheating player played in them. (This will be done at the administrators team discretion) This rule gives additional details to FraggedNation general rule 12.2. |
| 1.2 | Playing under the name of another player will not be tolerated and will result in: o 1st time offense: 2 months ban on all eFreeze public ladders. o 2nd time offense: At least 1 ladder season[1] ban on all eFreeze public ladders. o 3rd time offense: A permanent ban from eFreeze public ladders played on FraggedNation. All matches concerned by the faking and having a "tightness metric" (see below this paragraph for more information) inferior or equal to 4 should be rematched within a time span chosen by the administrators/referees team. If the matches are not replayed within the given time span, all results will be changed so that the team who had the faking player has lost. The "tightness metric" is computed according to the score of each map of the match: For each map (in which Team A had a faking player): * If Map Score is 0/0: o Score = 0 * Else o Score = Team A / MIN(Team B, 1) * If Team A lost, Score = - Score Then all three maps scores are summed to give the match "tightness metric". This rule gives additional details to FraggedNation general rule 10.2. |
| 1.3 | Challenging the decision of a referee or an administrator can be expressed publicly on the ladder's forum but not in-game. Challenging an in-game call and not following is not tolerated and will result in: o 1st time offense: 3 weeks ban on all eFreeze public ladders. o 2nd time offense: 2 months ban on all eFreeze public ladders. o 3rd time offense: At least 1 ladder season[1] ban on all eFreeze public ladders. An example of a referees/administrators call can be asking a player to leave from a server on which he's not supposed to be because of FraggedNation rules. |
| 1.4 | Any insulting or annoying behavior will not be tolerated whether in-game or on FraggedNation forums & shout boxes and will result in: o 1st time offense: A written warning is issued to the player. The offense count will be reset to none after 3 months of good behavior. o 2nd time offense: 3 weeks ban on all eFreeze public ladders. o 3rd time offense: 2 months ban on all eFreeze public ladders. Examples of insulting or annoying behaviors are: - Allegations of Player Cheating without solid material (cf. FraggedNation general rule 20.2) - Prejudice comments (cf. FraggedNation general rule 20.6) - Repeat threads (cf. FraggedNation general rule 20.7) or "spamming" in-game - Repeated referees/administrators decisions challenges without proper arguing. The administrator team reserves the right to give a 1st or 2nd time offense a 3rd time offense's penalty at their discretion (especially for Prejudice comments). |
| 1.5 | Insulting a referee or an administrator will not be tolerated whether in-game or on FraggedNation forums & shoutboxes and will result in: o 1st time offense: 2 months ban on all eFreeze public ladders. o 2nd time offense: At least 1 ladder season[1] ban on all eFreeze public ladders. o 3rd time offense: A permanent ban from eFreeze public ladders played on FraggedNation. The administrator team reserves the right to give a 1st or 2nd time offense a 3rd time offense's penalty at their discretion (especially for Prejudice comments). |
| 1.6 | [1] At least 6 months ban. So if the ladder in which the offense occurs ends in 2 months: If the next one lasts 3 months, 3 ladder seasons, else, if it lasts 4 months, 2 ladder seasons. |
| 2. Game play | |
| 2.1 | At a 5v5 ladder, if a team shows with less than 5 player, it will still be authorized to play. For instance, if only 4 players show, the teams will either play 4v4 if the other team agrees or 4v5 in the contrary event. Note that the same logic applies to other ladders (e.g. 2v2) but with different numbers. FraggedNation general rule 19.5 stated that: "You may NOT under ANY CIRCUMSTANCES substitute a non-roster player for play in a ladder match. Should your team not have enough people showing at the match, you will be forced to take a forfeit loss.". It should now be considered as: "You may NOT under ANY CIRCUMSTANCES substitute a non-roster player for play in a ladder match.". |
| 2.2 | If a player is on 2 rosters, he naturally is allowed to take part in a match of any of the rosters. The only exception to that is if he already joined another clan AND took part in an official match for them (in their roster). In that transition process, the FraggedNation general rule 19.4 applies (a clan can take in exactly one player that was not on the official roster at the time of the challenge but has been added to the roster). In the rare event in which a player belongs to both rosters of a challenge (old clan & new clan), he MUST play on his new clan's roster. This rule gives additional details to FraggedNation general rule 19.4 and 19.8. |
| 2.3 | A team cannot deny more than 3 challenges in a row. If a team does refuse 3 challenges in a row without accepting a challenge or challenging another team, it will be put inactive by admins for a minimum 2 weeks after the last challenge denying. |
| 2.4 | A team cannot chain challenge another team. If (team A) challenges (team B) and (team B) denies (team A)'s challenge, then (team A) can not challenge (team B) for one week. If (team A) rechallenges (team B) a second time after getting a deny within one week, the challenge will be removed by the admins. If (team A) chain challenges teams on a regular basis (regular is determined by admins), it may suffer a ELO points removal or being put inactive by admins for 2 weeks, or both. |
| 2.5 | Players GUIDs will be enforced during a match. A player whose GUID is not registered on FN can not play a FN match. Players are responsible for checking the other team's GUIDs. Any complain must be done before the match ends (If you can not get a referee to join your match before it ends, make sure to use a messenging system which logs date, e.g. FN PM, MSN) or it will be discarded. |
| 2.6 | Referees and Administrators SHOULD NOT take decisions, or act as Referees/Administrators while their team is playing a FN Match. If need be, an admin/ref may take decisions, or act as a Referee/Administrator but if, and only if, it can be done on a completely legitimate ground. Some examples of illegitimate grounds: |
| 2.7 | A team cannot challenge a team which ELO score is 100 points or more lower to theirs at the time of the challenging and cannot play a team which ELO score is 150 points or more lower to theirs at the time of the playing.
|
| 2.8 | A team cannot decline a challenge from a team which had a lower ELO score when the challenge was made. Their only option is to request a date change. The date change request must match the following criteria: - It must propose 3 dates; - All 3 dates must be within 2 weeks of the former challenge date; - All 3 dates must not be on commonly celebrated holidays; - Among the 3 dates, at least one of them must be on a work-day eve evening(Sunday to Thursday) and at least one of them must be on a week-end day eve evening (Friday or Saturday); - All 3 dates must be proposed at normal times (i.e. between 7PM and 9PM GMT unless the other team accepts another hour). The admins' team reserves the right to change the dates if they feel the purpose is to dodge the challenge with bogus dates proposals. This rule gives additionnal details to FraggedNation general rules 15.1 and 15.4. |
| 2.9 | You may substitute 1 ineligible player for play during the match. An ineligible player is someone who was NOT on your roster at the time of challenge, but as of the date of the match has been on the roster for at least 24 hours. Any team may substitute an ineligible player who was not on their roster at the time of the challenge, but has signed on AT LEAST 2 HOURS PRIOR to the time and date of the match. This is contingent on agreement from the opposing team. No exceptions will be made for players NOT on the roster 2 hours prior to the match. |
| 3. Miscellaneous | |
| 3.1 | Use this site to compare your time to gmt: http://wwp.greenwichmeantime.com/. |
| 3.2 | To have your GUID on FN, use this guide: http://www.clan333.com/forum/Forum.asp?forum=2§ion=10&post=16635&page=last. |
| 3.3 | Rules also be found on the ladder forum by following this link: http://www.fraggednation.com/forum/topic/eFreeze-Ladder-Rules-8346. Rules history, violations and discussion may be found on that forum thread. |
| 3.4 | Whenever rules are changed, you should be warned by e-mail on the address you entered to join FraggedNation. |
| 3.5 | The penalties applied to a player can be reduced by half if he publicly recognizes his wrongful behavior and apologizes on the ladder specific forum in which the rule violation occurred (unless specified otherwise). The administrators team reserves the right to refuse an apology for reasons they will describe. |
| 3.6 | The penalties lengths, points values, and any numeric value displayed on the rules are not to be considered as ultimate admins' decisions. In fact, it will be used as a guide for the admins' team when delivering penalties after an offense. It is important to note that the admins' team will try to consider aggravating and mitigating factors as much as possible. |
| 3.7 | Appeals to these rules violations' resulting penalties should be made according to FraggedNation general rule 11.1. |
| 3.8 | The rules are not retroactive. |
- Fri Sep 3 at 5:00 PM GMT[view]ALLIANCEChickens Have Revenge!!!
- Thu Sep 9 at 6:00 PM GMT[view]Saint Quake EliteALLIANCE
- Sun Sep 5 at 7:00 PM GMTPending Accept*]WeeD[*ALLIANCE
- Tue Sep 7 at 7:00 PM GMTPending AcceptDevils&EvilsALLIANCE
- Wed Sep 8 at 6:00 PM GMTPending AcceptChickens Have Revenge!!!KoE
- Sun Sep 12 at 7:00 PM GMTPending AcceptSaint Quake Elite[Killers & Demons]
- Thu Sep 2[view]Russian Warriors WDevils&Evils L
- Thu Sep 2[view]Devils&Evils WChickens Have Revenge!!! L
- Wed Sep 1[view]Chickens Have Revenge!!! WRussian Warriors L
- Tue Aug 31[view]NQT W*]WeeD[* L
- Tue Aug 31[view]Chickens Have Revenge!!! W!MakeLove*NotWar! L
- Mon Aug 30[view]Devils&Evils W*]WeeD[* L
- Mon Aug 30[view]*]WeeD[* W!MakeLove*NotWar! L
- Mon Aug 23[view]Saint Quake Elite W*]WeeD[* L
- Mon Aug 23[view]Devils&Evils WChickens Have Revenge!!! L
- Tue Aug 17[view]*]WeeD[* WNo Mercy L
- Mon Aug 9[view]Devils&Evils W*]WeeD[* L
- Sun Aug 1[view]*]WeeD[* WRussian Warriors L
- Tue Jul 27[view]Devils&Evils W*]WeeD[* L
- Sun Jul 18[view]*]WeeD[* W!MakeLove*NotWar! L
- Thu Jul 15[view]!MakeLove*NotWar! WDevils&Evils L
- Thu Jul 15[view]Russian Warriors W!MakeLove*NotWar! L
- Mon Jul 12[view]Saint Quake Elite WRussian Warriors L
- Sun Jul 4[view]No Mercy W*]WeeD[* L
- Sun Jul 4[view]Saint Quake Elite W*]WeeD[* L
- Wed Jun 30[view]Devils&Evils WKoE L
- Mon Jun 28[view]Saint Quake Elite WKoE L
- Sun Jun 27[view]NQT W*]WeeD[* L
- Sun Jun 27[view]No Mercy W!MakeLove*NotWar! L
- Thu Jun 24[view]Devils&Evils W!MakeLove*NotWar! L
- Wed Jun 23[view]Devils&Evils WNo Mercy L
- Tue Jun 22[view]Russian Warriors W*]WeeD[* L
- Mon Jun 21[view]KoE WDeaths Riders Clan L
- Sun Jun 20[view][Killers & Demons] W*]WeeD[* L
- Sun Jun 20[view]Saint Quake Elite WNQT L
- Thu Jun 17[view]Russian Warriors WDevils&Evils L
Quake III Game Director(s)
Q3 eFreeze 5v5 Head Admin(s)
Q3 eFreeze 5v5Time for changes!atrey
Quake IIIhiii.XeNoN
Q3 eFreeze 5v5Goodbye to you my friendst0kz
Q3 eFreeze 5v5Help to Paywhitey°
Quake IIIQ3 efreeze CTF 5v5HtK
Q3 eFreeze 5v5Useless and hated maps PollAlvaro°
Quake IIIANNOUNCEMENT: Please Welcome our New Q3 ...Sgt_SalsaMan
- Q3 eFreeze 5v5New maps efreeze 5v5 PollXeNoN
Quake IIIPlease Welcome our New Q3 Game Directorseason
Q3 eFreeze 5v5Fraggednation serversal1en_nqt
Q3 eFreeze 5v5NoGhost - A Quake III AlternativeVo!tag3°
Q3 eFreeze 5v5What's next?^sQe^kawa
Q3 eFreeze 5v5Random MapsInVerSe°
Q3 eFreeze 5v5efreeze tournament?!?Moldovanin- Q3 eFreeze 5v5Small summary!^sQe^kawa
Q3 eFreeze 5v5Quake Live Freeze Tag petition[DIE16]Lil_John_Pi°
Awarded By: 333ben
Season 3
Most Active Team: [Killers & Demons]
-- Close Contenders: Russian Warriors, Saint Quake Elite
This ladder is not configured for any prize payouts. Please click this link to search the list of ladders that have been configured for prize payouts.
Ladder Membership Status
:: Loading Shoutbox :: Ladder Servers
- efreeze 5v5
94.75.230.236:27960
