:: Up North Battlefield League ::

	:: information ::

	:: league ::

	:: community ::

	:: other ::

:: userpanel ::

Chapter 1 - General
Chapter 2 - Penalties
Chapter 3 - Administrators
Chapter 4 - Rescheduling
Chapter 5 - Match procedure
Chapter 6 - Server
Chapter 7 - After the match
Chapter 8 - Protests
Chapter 9 - Players
Chapter 10 - Clans
Chapter 11 - Conduct
Chapter 12 - League
Chapter 13 - Cheating
Chapter 14 - The site

§1.1
These rules apply for gaming, use and behaviour related to Up-North's leagues, tournaments and web pages, unless stated otherwise.

Revision 4 2004-08-24

§1.2a
These rules must be followed by all users/players at all times, with the exception of cases handled by §1.2b and §1.2c.

Revision 2 2004-07-20

§1.2b
An administrator can authorize exceptions/additions from the rules if he finds it necessary.

Revision 1 2004-07-20

§1.2c
Clans can decide to disregard a rule if both clans agree provided that the change does not cause harm to a third party such as another clan/player.
Generally, rules that can be disregarded are clearly stated.

Revision 2 2004-08-24

§1.3a
The purpose of these rules are to make the game experience fair and enjoyable for all participants. It is impossible to cover all situations and in case of a situation not covered by the rules an administrator can rule according to §1.2b.
In case a rules' literary meaning is in conflict in the spirit in which the rule was written, an administrator can change the interpretation according to §1.2b.

Revision 1 2004-07-20

§1.3b
If a situation occurs where clans/players cannot agree on the interpretation of the rules, or wish to invoke §1.3a, an administrator should be questioned (see Chapter 3).
If an administrator cannot be found, the match is can be postponed until a ruling is made.

Revision 2 2004-08-24

§1.3c
If a players/clan notices that the opponents are breaking a rule, they should notify them. To start or continue a game without giving the opponents a chance to correct their mistake is unsportsmanlike and administrators can decline protests involving situations where a clan silently accepts breaking of a rule just to be able to complain afterwards if they loose.

Revision 1 2004-07-20

§1.4a
The rules can be changed at any time. These changes are often posted on the front page, but rules apply even if changes are not posted.

Revision 2 2004-08-24

§1.4b
It is every player's responsability to know the rules. Not knowing a rule is not an excuse for breaking it.

Revision 2 2004-08-24

§2.1
If a situation occurs where a clan has gained more by breaking a rule than they loose in penalty, an administrator can increase the penalty according to §1.2b.

Revision 2 2004-08-24

§2.2
Forfeit - Penalty that means that the opponent receives 50% of the tickets on the portion (round/map/match) forfeited. Forfeiting clan receives 0 tickets.

Revision 4 2005-06-19

§2.3
Ticked deduction - Penalty which means that a teams' tickets are reduced on the portion of the game (round/map/match).

Revision 1 2004-07-20

§2.4
Loss of match - The punished clan receives forfeit on all rounds of a match according to §2.2

Revision 2 2004-08-24

§2.5
Replay of match or part of match - The match in question is to be replayed, either fully or partially.

Revision 1 2004-07-22

§2.6a
Clan exclusion - The punished clan is excluded from the current league/tournament. See also Rule 12.3.

Revision 2 2004-08-26

§2.6b
Player exclusion - The punished player is excluded from the current tournament/league.

Revision 1 2004-07-22

§2.7
Ban - The punished player/clan is excluded (see §2.6) and forbidden to participate in later leagues/tournaments for a specific time span, or for life.

Revision 2 2004-08-24

§2.8
Point deduction - One or more points earned in the game are removed. If the clan punished did not score any points in the game, the score may become negative.

Revision 1 2004-09-01

§3.1
Administrators are appointed by Up-North and can be seen at respective division-/season-page.

Revision 4 2004-07-22

§3.2
Contact with an administrator should primarily be made via UN-message or IRC. To send UN-messages is preferred, both to administrators and opponents, as in conflicts they can be used as evidence (since they cannot be altered afterwards which an IRC log can).

Revision 2 2004-08-24

§4.1
Rescheduling can be made when both teams agree on a new date/time.
Use the Reschedule-feature (available to leaders/trustees) found on the match-page.

Revision 2 2005-07-31

§4.2a
Reschedules have to be answered within 24 hours.
A UN-message is sent to all leaders and trustees of the clan recieving the reschedule.
If you are a leader and do not visit the site very often, you can choose to get notifications about UN-messages via email by enabling that in your profile.

Revision 3 2005-07-31

§4.2b
Reschedules not answered in time according to §4.2a can be forced by the opponent.

Revision 3 2005-07-31

§4.3a
A valid reschedule must have both a date and a time.

Revision 1 2004-07-22

§4.3b
In case of invalid rescheduling, the administrator can change the date and/or time.

Revision 2 2004-07-22

§4.4
It is allowed to play a game before the scheduled time provided that Rule 4.5 is followed.

Revision 2 2005-07-31

§4.5
Matches may not be rescheduled outside the given matchweek, in such case the administrator has the right (but not the obligation) to decline to reschedule.
A match may not be played before the previous match, or after the next match.

Revision 1 2004-08-24

§4.6
If one team cant or does not want to reschedule a match, the team that wants to reschedule should use Forced Solving.

The system then asks both teams of all the dates they can play and decides a date after that.
If one team does not respond, they are considered providing 0 dates.

Forced Solving can be applied up until 4 days before the game is suppose to start.

Revision 2 2005-07-31

§5.1
Make contact with your opponents before the game. If you have not got hold of the opponents 10 minutes before start of the game, you must enter the channel #up-north on QuakeNet and ask for them in the channel. If you 15 minutes after the game was supposed to start still not have made contact with them please type it in the channel. That serves as proof in case of a conflict.

Revision 1 2004-08-23

§5.2
All players have to be in the chosen server (se rule 6 for server rules) at least 5 minutes before the game should start.

The team providing the server should give the opponents access to the server at least 15 minutes before the game is supposed to start.

If they get access later, they can not be expected to have all their players ready 5 minutes before start.

The game should always start at the designated time. If some clan does not have all their players present 15 minutes after the starting time, the game can be started anyway. Exceptions can be made according to Rule 1.2c.

Revision 4 2005-07-31

§5.3
The first map to be played is the map listed first at the match page.
Exceptions can be made according to Rule 1.2c.

Revision 2 2004-08-24

§5.4
Home team starts as US on all maps.

Exceptions can be made according to Rule 1.2c.

Revision 2 2005-07-31

§5.5
Each game should be over in 3 hours from the designated starting time. If a game is not finished by that time due to delays, the team not responsible for the delay has the right to demand a postponement or forfeit on the remaining part of the game.
If both teams are responsible for delays, the match can be postponed.
The game can of course continue longer than 3 hours if both teams agree.

Revision 1 2004-08-23

§5.6
Each team has the right to demand one pause per round, with a maximum time of 3 minutes.
More than one pause per round and team is not allowed, regardless if they used their full 3 minutes or not.
A clan can use this pause for anything, and does not have to explain why they want a pause.
A request for pause is made by anyone in the team writing it in the chat.

The team controling the server must then pause the server within 30 seconds after the request has been made. Make sure to take screenshots of the request and when the game was paused.

Failure to pause within this time will be punished by 1 ticket per extra second up to 90 seconds, after which the team requesting the pause has the right to request a restart of the round.

Exceptions can be made according to Rule 1.2c.

Revision 3 2006-02-01

§5.7
Changing players is allowed any time during the match.
Changing players during an ongoing round is allowed, provided that the player that is to be replaced disconnects before the new player connect. Pausing is only allowed according to Rule 5.6.
There is no rule how many players can be changed, as long as they all are approved according to Rule 9.

Revision 1 2004-08-23

§6.1
The home team is responsible for providing an approved server. If they cannot provide an approved server the opponents should be notified as soon as possible so they can try to provide one.
If no server is available an administrator should be contacted and if he cannot find a solution the game can be postponed.

Revision 1 2004-08-23

§6.2
A server should be dedicated, connected in Sweden, Norway, Denmark or Finland and have Punkbuster activated.
Exceptions can be made according to Rule 1.2c. Pay special notice to Rule 1.3c.

Revision 2 2004-08-24

§6.3
A server should be configured as follows:

Required settings:
sv.password "[insert password here]"
sv.internet 1
sv.punkBuster 1
sv.allowFreeCam 0
sv.allowExternalViews 1
sv.allowNoseCam 1
sv.hitIndicator 1
sv.spawnTime 15
sv.ticketRatio 200
sv.roundsPerMap 10
sv.timeLimit 1200
sv.scoreLimit 0
sv.soldierFriendlyFire 100
sv.vehicleFriendlyFire 100
sv.soldierSplashFriendlyFire 100
sv.vehicleSplashFriendlyFire 100
sv.friendlyFireWithMines 1
sv.tkPunishEnabled 0
sv.tkPunishByDefault 0
sv.votingEnabled 0
sv.autoBalanceTeam 0
sv.teamRatioPercent 100
sv.useGlobalRank 0
sv.useGlobalUnlocks 0
sv.maxPlayers 20
sv.startDelay 30
sv.manDownTime 15
sv.endDelay 15
sv.endOfRoundDelay 15
sv.timeBeforeRestartMap 30

Pay special notice to Rule 1.3c.

Revision 11 2006-02-16

§6.4
In the case of a server crash all players should capture a sceenshot so that the tickets and time is remembered.

Revision 3 2005-07-31

Revision 7 2005-07-31

§6.6
Drawing of lots to decide the score.
AN administrator should make the draw.

The administrator will determine the ticket score at the time of the crash based on the screenshots captured according to Rule 6.4.
If a score cannot be determined by the administrator the score is to be determined as 75% of the starting tickets for both teams.
When a score is determined, the administrator will draw lots to decide a winner.
The winning teams lose 10% of their determined tickets and the other team loses 90% of their determined tickets.

Revision 2 2004-08-24

§6.7a
If one team thinks the server is bad, they have the right to demand a change of server. The change can only be made after a completed round.

Revision 1 2004-08-23

§6.7b
If both teams want to change server, the change may be made during the round and the match resumed at the new server according to rule 6.4 or 6.5.

Revision 1 2004-08-23

§6.8
If both teams think the opponents' server is bad, a neutral server should be used. If no neutral server can be found, the remainder of the match is to be played 50% on each server. If three rounds are remaining, two of them are to be played at the complaintants server. If only one round is remaining it is to be played at the complaintants server.

The hometeam may select which map(or round(s)) that is to be played on their server.

Revision 4 2005-05-16

§6.9
Each clan should take screenshots at the end of each round.

Revision 2 2004-08-23

§6.10
The team controling the server decides if demos are to be recorded.

Revision 1 2005-07-31

§6.11
Shoutcasters or spectating admins should always be allowed access to the server.

Servers should have at least 18 slots, to make room for such extra spectators.

Revision 1 2005-11-10

§7.1
The score should be entered as soon as possible after the game is over.
Any team may enter the score.
If no score is entered within 5 hours an administrator has the right to enter a forfeit win for the home team.

Revision 1 2004-08-23

§7.2a
When a score is entered the other team has 3 hours to accept (or change) it. If it is not accepted/changed within 3 hours an administrator can accept the score. Point deduction according to Rule 2.3 can be made on the team that did not accept the score.

Revision 1 2004-08-23

§7.2b
Rule 7.2a only applies to the clan not entering the score first. There is no specific time limit for the team that first entered the score to accept a changed score. The score should however always be accepted as soon as possible. Situations concerning unaccepted scores are treated according to Rule 1.2b.

Revision 3 2006-09-22

§7.3
An MVP should always be chosen in the opposing team if the game was played (in case of forfeit, no MVP should be selected). The choice can be made freely, but the MVP must have played some time during the game.
Penalty for breaking this rule is point deduction according to Rule 2.8.

Revision 4 2004-09-05

§7.4
Home team is responsible for uploading screenshots to the site.

Revision 1 2004-08-23

§7.5
Winning a map gives 1 point to the winning clan.
Drawing a map gives 1 point for each clan, unless the total is a draw.
The total winner gets 1 bonus point.
If the total is a draw, the total result is 1-1.

Examples:
Clan A wins both maps (and, of course, the total): 3-0
Clan A wins first map, Clan B second map, Clan B wins the total: 1-2
First map is a draw, Clan A wins second map (and therefore the total): 3-1
Clan A wins first map, Clan B the second, but the total is a draw: 1-1
Draw both maps: 1-1

The result of a forfeit is 50% of the tickets on all maps (See Rule 2.2)

Revision 2 2005-06-19

§8.1
A protest should be posted in the division news.
A message should also be sent to an administrator to inform him about the protest.
Protest must be posted within 48 hours of the game starting time.
Later protests will not be accepted, unless the circumstances made it impossible to post the protest within 48 hours.

The protest should always be in english, as all other public posts.
The score in the game must be accepted as usual even if a protest is posted.

Revision 5 2006-02-16

§8.2
Protests should contain evidence (server logs, screenshots, IRC logs etc). Speculations and suspicions will be disregarded without evidence.

Revision 2 2004-08-24

§8.3
Protest not posted in accordance with §8.1 are not accepted.

Revision 3 2005-07-31

§8.4
The team protested has the right to reply to the protest before a ruling is made.

Revision 1 2004-08-23

§8.5
An administrator has the right to make a ruling without following Rule 8.4, if the evidence is overwhelming or the situation demands it.

Revision 1 2004-08-23

§9.1
For a player to be approved, he/she must follow Rule 9.2a,b,c,d and e.
The opponents can approve a player according to Rule 1.2c even if he does not follow Rule 9.2a,b,c,d or e.

Revision 1 2004-08-23

§9.2a
A player can only be member of one clan at a time per league/tournament.

Revision 2 2004-12-25

§9.2b
A player must have been registered as member of the clan at least 72 hours.

Revision 2 2004-08-24

§9.2c
A player's nick in game must equal the nick at the page (excluding clan tag). Certain deviance can be accepted, but to avoid confusion everybody should use exactly the nick they are registered with.

Revision 2 2004-08-24

§9.2d
A player must be connected in Sweden, Finland, Denmark, Norway or Iceland.

Revision 1 2004-08-23

§9.2e
A player not following 9.2d is allowed provided that the clan has no more than 3 such players playing at the same time during a match.

Revision 4 2005-07-31

§10.1
A clan can consist of an unlimited number of players.

Revision 1 2004-08-23

§10.2
A clan can only field players approved according to Rule 9.1.
Penalty for breaking this rule is forfeit according to Rule 2.2.

Revision 1 2004-08-23

§10.3
Each clan must have at least one leader.

Revision 2 2004-08-24

§10.4
The clan is responsible for everything its members do.

Revision 1 2004-08-23

§11.1
All players must behave in a sportsmanlike way.

Revision 1 2004-08-23

§11.2
Curses and degrading comments will be punished according to Rule 2. The penalty given is related to the gravity of the situation.

Revision 1 2004-08-23

§12.1
For a clan to be accepted into a league, the administrators must have reasons to believe that the clan can field a full team every game.

Revision 1 2004-08-23

§12.2
If a clan during a season forfeits more than 30% of their rounds, they are expelled from the league according to Rule 2.6.

Revision 1 2004-08-23

§12.3
If a clan is expelled, or disbands, from the league by any reason all their played matches are cancelled.

Revision 1 2004-08-23

§13.1
A player cannot use any form of software (or other resource) during play that alters, adds or subtracts functionality related to the game.
Example of such software:
* cheats
* altered textures, sounds or other resource-files
* software that times, calculates or in other ways help the player during the game with tasks that are normally done manually.

Examples of forbidden things:
* the clearpoints addon
* any kind of spawntimer
* texturepacks
* any form of changed minimap

Revision 2 2004-08-24

§13.2
Programs for voice communication are allowed.

Revision 1 2004-08-23

§13.3
A player that during the game intends to use something not part of a standard, out of the box, Battlefield 2 installation (with the latest patch) must consult an admin before using it.

Revision 2 2005-06-19

§13.4
A bug is considered as a function in the game made by a technical mistake by the developers.

Revision 3 2004-08-24

§13.5
Examples of bugs:

Blocking spawnpoints
Spawning on squadleader outside map

Revision 5 2005-09-11

§13.6
Examples of non-bugs:

Changing squad midgame
Changing squadleader midgame
Pixelshooting

Revision 3 2005-08-23

§13.7
The penalty for exploiting a bug is depending on the severity.
If the exploit was made unintentinally by the force of opponent (for example being shot through a roof by an enemy explosion) no penalty will be given.

Revision 1 2004-08-24

§13.8
A player/clan that wish to use something that could remotely be classified as a bug should contact an administrator in advance to get clearance.

Revision 1 2004-08-24

§14.1
Only one user account is allowed per physical person.
There is NO excuse for creating multiple accounts.
If something is wrong with your account please contact an admin and it will be fixed.

Revision 2 2004-08-24

§14.2
Spam, ads or any other kind of commercial messages are not allowed in our messaging system, comments or forum.
If you wish to send the same message to a large group of people, you must contact an admin to get clearance first.

Revision 2 2004-08-24

§14.3
Using an account that does not belong to you is strictly forbidden.

Revision 1 2004-08-24

§14.4
Impersonating another person is not allowed.

Revision 1 2004-08-24

§14.5
All times and date at the site are in CET during winter (GMT+1), CEST during summer (GMT+2). The time zone used by Sweden, Norway and Denmark.

Finland is one hour ahead.

Revision 4 2005-08-01

§14.6
When posting comments on the site, it is not allowed to:

* use a picture as "signature"
* use pictures excessively
* post line breaks/spaces/tabs/etc excessively

Revision 1 2005-11-30

	:: wazzup ::

	You need to register for this feature to work

	:: poll ::

	New league? 1942 25% 2142 16% Wouldnt play either 59%

:: top betters ::

	Fnatteus	64122
	Maverick	45311
	Tank Abbott	44177
	maggo	41457
	xM	39450

:: upcoming ::

No upcoming matches

:: played ::

CW - SF	0 - 3
[CW2] - Mutt	3 - 0
iD - JDG	3 - 0
more...

	:: advertisement ::