All the curent Alliance Teams
The League Tables
All the league fixtures
Visit the Alliance Forum
The full Alliance league rules
Contact the Alliance Administrators

Link to the LSN web site

Welcome to the LSN Alliance League.

 
1. Team Membership and Team Playing Order

Each Alliance team may have up to 7 members, but must have a minimum of 3 members. All members of each team must be registered LSN players.

A player may play for only one Alliance team in any given month. A player who plays for more than one team in a season will be known as an 'Alliance Tart' - yes we're all looking at you Lego Pirate ;)

2. Matches
2.1 Make up of a Match

An Alliance league match is the term for a set of games played between the members of two clans.

Fixtures will be produced by the Alliance team and published on the Alliance website.

Each match will consist of the teams players playing their opposite number. So the player at position 1 from team A, will play the player at position 1 from team B and so on through all players. The scores from each individual match are then added together and the clan with the higher score wins. In the event that both clans have the same point totals, the game will be considered a draw.

An Alliance league match will consist of no more than five individual games.

If one team does not field five players then the game with the missing player will be declared void providing the player has been declared as missing before the start of the month.

A team must field at least 3 players in a match. Failure to do so will result in the team losing the match 50-0

Alliance League matches always begin on the first of the month.

2.2 Home and Away

On the Alliance league fixture list a team can be designated as either a home or an away team. The major significance of this is to indicate which team should issue the game challenge. In all cases the home team should issue the challenge to the appropriate player as specified on the fixtures list.

2.3 Team Order

A teams playing order may be found on the teams page, along with the date this team order was updated. A thread will also be opened for each team in the team ordering forum. Whenever a team changes its playing order, the new team order must be posted here.

A teams order may be changed at anytime, but the changes will only take effect from the next month. So if a captain submits a new lineup on the 1st of the month this will not be used until the following month. No team order changes may be made on the last day of a month. This is to allow the Alliance league coordinators time to update the team sheet.

No team reordering may take place on the last day of the month. This is to allow league admins time to produce accurate fixture lists.

When teams are issuing challenges for a months games they must check both the teams page and the relevant teams thread in the team ordering forum. If the team order in the forum is newer than that on the teams page then the team order from the thread should be used unless it was posted after the start of the current month.

Teams cannot leave gaps in their team order. If they only have four players, then these players must fill positions 1 to 4.

2.4 Starting Games

When playing the individual games that make up a teams match, all players must conform to the following rules:

The map the game is to be played on will be published on the fixture list.

Before issuing their challenges players (or their captains) are advised to check the Player Availability forum to see if a substitute has been used. If the challenger challenges the substituted player in error and the start date passes without the substitute having been challenged then the match will be voided.

The challenge should be issued with the following settings:

  • Force Points: 20
  • Turns: 30
  • Time Limit: 30 Days
  • All games should be friendlies unless both players agree otherwise.
  • Any faction may be deployed and there are no unit restrictions.

No games should be played using a Beta version of the LSN client unless both players agree otherwise.

2.5 Time Scales

Challenges should not be sent before the 1st of the month.

Game challenges must be issued before midnight GMT on the7th of the Month. If a challenge is not issued in this time then the challenging player will suffer a default loss. If the challenged player does not respond to the challenge by midnight GMT on the 7th of the Month then they will be liable for the default loss. If a challenge is sent at the end of the start period then the challenged player will always have 2 days to respond. This may take the start of the game beyond the first seven days of the month.

Once a challenge has been responded to the challenging player must deploy within the later of either the first seven days of the month or within two days of the the challenged players deployment. Failure to do so will result in a default.

Players who are waiting for a challenge or waiting for a deployment are advised to post on the 'Games Waiting' forum as in the case of any dispute having done so will strengthen their position.

2.6 Problems with Challenges

Players and their captains are responsible for enforcing the above conditions themselves. If a challenge is received that is incorrect they must post on the Alliance forums to advise the challenging player to re-challenge. If an incorrect challenge is responded to then the challenged player is deemed to have accepted the 'incorrect' challenge and has to play the game. For example if a 30 point challenge is sent and responded too then the game must played to completion under those conditions.

2.7 Games played outside of time scales in the rules

If a challenge is issued or accepted after the deadlines outlined above then the player who is not at fault must claim their default at that point. If they respond to either a challenge or a deployment after the relevant start dates then they lose the opportunity to claim a default. If a game is started or runs significantly outside of the normal time scale for the Alliance match then the Alliance coordinators will void the match.

2.8 Player Unavailability - BEFORE the start of the month

As the league is designed to run over several months, it is logical that during some months players may be unavailable to play in their assigned league fixture(s).

If a player is likely to be unavailable for all or part of a month in which they have an assigned game or games, then the team should post a new lineup in their team ordering thread. If the player is then available the next month then the team should remember to post a new team lineup including that player.

2.9 Player Unavailability - AFTER the start of the month

If it becomes apparent that a player is unavailable during the first week of the month then the game will not be voided. If a substitute is available they can be used to cover for the missing player. If no substitue is available then the missing player will incur a default loss.

If a substitute is used in this manner then it is the responsibility of the captain using the substitute to make sure that the challenging player and / or their captain knows that a substitue has been used. They are required to post the use of a substitute in their team order thread as well as emailing the Alliance coordinator responsible for that division (and if possible the opposing team captain). If they do this and no game gets underway then the match will be voided and no defaults or blame allocated to either team or player. If they do not do this or take other reasonable action then they will still incur the default loss.

2.10 Completing Games

When a game is completed the result should be posted on the Alliance results forum.

If a game is conceded then the winning player is awarded a 20 - x win, where x is the score of the conceding player.

If Spawn are involved in a game then the winning players score may need to be adjusted to be higher than the losers. If this is the case the winners score will be the losers score + 1.

Games are considered finished either when a normal result is achieved, or one player times out. If a player times out then the winning player gains a bonus.

  • In seasons 1-8 this bonus was a 20 - x win, where x is the score of the player who times out.
  • From season 9 the bonus is 10 points, up to a maximum of 20. Note that in the case where one player was a long way ahead this may mean the player who did not time out still loses. e.g. 5-17 would become 15-17. If a player feels that the timeout rules have been abused, for example if they were just about to finish off their opponent and score more than ten points then they may send the admins a wholegame. The admins may at their discretion award a larger points bonus in this case.

2.11 Defaults

Where a player defaults (before a game has started) then the team that the defaulting player belongs to will be deducted a single point from their league points total. The match will be scored as follows:

  • In seasons 1-7 recorded as a 0-0 draw
  • In season 8 recorded as a 1-0 win so it was easier to see who the default was awarded to, although the match score was not used when determining the match winner
  • From season 9 recorded as a 10-0 win (as per timeouts) and will be used when determining the match winner.

3. The League Scoring System

Clans will score points as follows:

  • 5 points for a win
  • 2 points for a draw
  • 0 points for a loss
  • a single point will be deducted from a teams league score each time one of their players defaults on a match.

As well as the match points gained through wining and drawing matches, a record will be kept of the number of game points amassed by each team, in each match. This will be used to calculate the teams score points difference.


A teams score points difference will be calculated using the following formula. ( (Total points scored by the team in a match) - (Total points scored against the team in a match))


The points difference for each team is recorded and adjusted after each match.

4. End Of Season

On completion of the season the top 3 teams from division 2 will be promoted to division 1. The bottom 3 teams from division 1 will be relegated to division 2.

 

Alliance league information
Past seasons results
Stats on Alliance players
Other Alliance competitions for clans
The inside line on the Alliance
Credit where credit's due