. Information
1.1. The Epic Gaming League is an international Warcraft 3: The Frozen Throne League. The main language is english.

2. Definitions
2.1. Clan: Participating teams will be referred to as "Clan". Each clan must consist of at least 5 players.
2.2. Team Manager: A Team Manager is responsible for a Clan and is the entity that will receive the prize if its clan wins.
2.3. Player: Players are the people who win the points in clan wars, by Knocking-out all of the opposing teams players in a "King of the hill" format (NGL).
2.4. Sub-cards: Each clan recieves 2 sub-cards for qualifiers, and 3 for the regular season. A sub-card can be used to replace a place in the LU with a player not in the LU.
2.5 Sub-cards May also be used to replace the starter with a player already set in the lineup.
2.6. Joker-card: Each clan recieves 2 Joker-cards for qualifiers, and 4 for the regular season. A joker-card can be used to "revive" a player who has been KO, by replacing another player in the LU.

3. Competing System
3.1. Qualifiers
3.2. Regular Season
3.3. Playdowns
3.4. Playoffs
3.5. Clan war
3.5.1. Each team will have 4 players in their Line-up, the "starting" player must be stated when submitting the line-up (4.1.). The starting players will then play eachother, and the winner will then advance to face the next opponent from the opposing clan. Once all of the players of a clan have been KO, they have lost the clan war.
3.5.2. All series are best of 1
3.5.3. Team is awarded 1 point per match won.
3.5.4. If teams are even on points at the end of the regular season, win/loss record will determine who advances to the play-offs, If this is also equal, then it will go down to the head-to-head record between the 2 teams.
3.5.5. If there are more than 2 teams equal on points and equal win/lose record, then there will be tie-breaker clan wars.
3.5.6. Teams are allowed a maximum of 10 minutes in between each series, more than that will result in a default win for the waiting team for that series.
3.6. Maps
3.6.1. Map Veto System
3.6.1.1. There will be a "Starting map" given at the start of every Clan war, this map can be used again.
3.6.1.2. The team who have just lost a point choose the next map. The same map can not be played twice, apart from the starting map.
3.6.1.3. The map pool is shared.

3.6.2. Map Pool:

Twisted Meadows
Turtle Rock
Terenas Stand
Echo Isles
Secret Valley
Ancient Isle
Melting Valley
SnowDrop 1.3

3.7. Races
3.7.1. Players have to use their races that they sent in their lineup for the first game
3.7.2. After that, players are allowed to change race.
3.7.3. Players that have random as their race have to choose random.

4. Lineups
4.1. The line-ups are to be submitted by the team manager via email (lineups@epic-league.net) at least 30 minutes before the match scheduled time.
4.1.1. Line-ups must have the starting player indicated and the race each player is using for their first match. Failure to have either of these will result in 0.5PP (1PP if neither are indicated)
4.2 Line-ups will be posted 15 minutes before the scheduled time.
4.3 Line-ups cannot be changed after 30 minutes before the match is meant to be played (unless a sub card is used)
4.4 Line-ups will not be accepted beyond the match schedule time, and the match will result in a forfeit win in favor of the team that submitted their line up.
4.5 No barred players can be on the line-up, regardless on whether or not the opponent has allowed them.

5. Scheduling
5.1. Team's managers are responsible for scheduling a clan war.
5.1.1. Team should have at least 1 manager.
5.1.2. At least one manager on each team must have an MSN account.
5.2. The clan war has to be scheduled by Thursday 11:59pm EST (5:59 CET Friday)
5.2.1. Failure to schedule by 5.2. will result in 0.5 PP to the team responsible for not scheduling.
5.2.2. Once scheduled you must inform an admin of the time/date either by the scheduling board or another way
5.3. Scheduling problems
5.3.1. If matches can't be scheduled without conflict, admins will take control of the situation and set a time. Check the staff list to contact an admin, or send an email to Rift@Epic-League.net
5.3.2. If the above situation occurs, it is up to the managers to inform the admins early.
5.3.3. If one team is unreachable, the other team gets to choose the time and date.
5.4. All games have to be played by 11:59 EST Sunday (5.59 CET Monday)
5.4.1. If for some reason teams can't play their games in time, the managers have to inform the admins straight away.
5.5. If a player fails to show 20 minutes after the clan war time, the team manager must either subcard or forfeit that match.
5.6. No matches will be delayed unless the admins postpone it for a very serious reason.


6. Roster
6.1. Added players are not eligible for 7 days after they have been added
6.2. Players can only play on one team roster.
6.2.1 Players who play on another team tag simultaneously for any prized competition are considered "Double Tagging" and may be banned from the competition.
6.3. Managers that are listed on the team profile are eligible to play in that teams clan war.
6.4. If a team merges, they must notify the admins immediately.
6.4.1. If both teams that merge are in the league, all of the players will be eligible for any wars, but if they are merging with an outside team, than the standard 48 hour eligibility rule will take place for any new players.

7. Replays
7.1. It is up to both teams to save all replays.
7.2. Replays have to be uploaded in the EPGL replay database by the team manager as soon as possible.
7.3. Failure to upload a replay within 48 hours of when the series were played, will result in 0.5 penalty points against the team committing the infraction.
7.4. The password for the EPGL database is 12345

8. Hosting and Lagging
8.1 Hosting
8.1.1. Both players have to agree on the host.
8.1.2. If a host can't be agreed on, the admin in charge will set a host to be used.
8.1.3. If the game is laggy, it should be saved and rehosted. Leaving a game without saving and notifying will constitute a forefit to the player who left the match.
8.1.4. If a player scouts or there is interactions between the 2 players the 8.1.3 rule no longer applies, unless the players make an agreement to save and rehost.
8.1.5. The game must be hosted under these parameters:
Game must be set on fastest.
Observers must be set to “Full observers.”
Team lock must be on
Random Heroes must be off.
Random Races must be off.
Fog of War must be on.
“Full” unit sharing must be off.
8.2. Observers
8.2.1. Only lineups, managers and admins are allowed to obs the game.
8.2.2. A player have the right to call 'no obs'. Then only admins and managers are allowed to obs the game.
8.2.3. The admin-in-charge have to be in the game, unless a specific order is given to start the game without the admin
8.3 Disconnection
8.3.1 If a player disconnects before the 2 minute mark, a regame will be called.
8.3.2 If a player scouts or there is interactions between the 2 players the 8.1. rule no longer applies.
8.3.3. If a player disconnects after the 2 minute mark, the present admin will decide if it's a re-game or a win unless both player agree to re-game.

9. Penalty
9.1. Penalty Point system
9.1.1. Penalty Points are assigned to a clan and are cumulative over the season.
9.1.2. Penalty points may only be assigned by a EPGL admin.
9.1.3. Three penalty points will result in the loss of one (1) point from the team’s standings.
9.1.3.1 Five (5) penalty points accumulated during qualifier will result in disqualification from a EPGL qualifier.
9.1.3.2 Seven (7) penalty points accumulated during regular season will result in disqualification from the EPGL regular season.
9.1.4. One penalty point will be issued for each forfeit in any clan war.
9.1.5. Penalty points may be assigned for (but not limited to):
9.1.5.1. Poor player conduct (including “bad manner” behavior).
9.1.5.2. Any activity judged to impede the progress of the clan match.
9.1.5.3. Team Leaders not sufficiently performing their duties.
9.1.5.4. Any other misconduct as judged by an admin.
9.1.6. Multiple penalty points may be assigned for one activity.
9.2. Severe Misconduct
9.2.1. Some activities are beyond the scope of the Penalty Point system. They include (but are not limited to):
9.2.1.1. Use of third-party programs (“map-hacking”).
9.2.1.2. Roster abuse (“double-tagging”)
9.2.1.3. Misleading the admins.
9.2.1.4. Other misconducts as judged by the senior admin staff.
9.2.2. These misconducts may result in the ban of a player or even a team from the league from a season or even forever.