35388 registered members (251 online, 6 using SGLAC), 7149 registered teams
A Game Frontier company
New to TheSGL.COM?
We are a gaming community running leagues, ladders and cups with big prizes. Register an account now, or if you've already signed up please login.
Head sponsor
Poll
SteelSeries : King of the Hill #3 - Who do you want to see taking on Dignitas in the next match?
Sisters of Mercy
Flattering to Deceive
cZar
Immolate
Locked
Octane
toobad
sexytime
catalyst
Four Kings
vitalsigns
kkpal
Flavour
Europe Chinese Group
Highfive
Shoutbox
You must be logged in to post a shout.
warren_9
KENJINN
shey /
fOzbOp
redrUM.Rules
DEFAULT RULE SET FOR CONDITION ZERO
This is the default rule set for CounterStrike condition Zero matches played here at theSGL.com. Individual events may supercede these rules so please do check each event and it's rules page to ensure you are aware of the rules. If you are unsure - consult an admin. Ignorance of the rules is not an acceptable excuse for breaking them.
1.00 Information :
1.01 About theSGL.
theSGL.com draws from two main areas in our quest to bring you the finest gaming environment possible - the CALeague of North America which has set the standard for competitive online gaming and the football league and cup tournaments of the world. We strive to listen to what the participants want from their games and do our best to offer just that. We denounce abuse, racism and have successfully run friendly yet competitive online and LAN leagues, cups and other tournaments since 2004
theSGL.com draws from two main areas in our quest to bring you the finest gaming environment possible - the CALeague of North America which has set the standard for competitive online gaming and the football league and cup tournaments of the world. We strive to listen to what the participants want from their games and do our best to offer just that. We denounce abuse, racism and have successfully run friendly yet competitive online and LAN leagues, cups and other tournaments since 2004
1.02 About these rules.
Teams, managers and participants must be aware of these rules and abide by them to ensure their continued place within theSGL. Failure to comply and respect the rules here within may lead to suspension, loss of points or even permanent removal from the league. Ignorance of the rules is no defence for transgressions against them and it is a players responsibility to ensure they are familiar with the rules and further to that it is a clan leaders or managers job to ensure that the players within their team are aware of the rules. If you are unsure about any of these rules or feel you need clarification on any aspect of them, then it is your responsibility to seek such clarification from an admin.
Teams, managers and participants must be aware of these rules and abide by them to ensure their continued place within theSGL. Failure to comply and respect the rules here within may lead to suspension, loss of points or even permanent removal from the league. Ignorance of the rules is no defence for transgressions against them and it is a players responsibility to ensure they are familiar with the rules and further to that it is a clan leaders or managers job to ensure that the players within their team are aware of the rules. If you are unsure about any of these rules or feel you need clarification on any aspect of them, then it is your responsibility to seek such clarification from an admin.
2.01 Player registration.
A player must be registered on the website www.theSGL.com and have a profile that includes at least the minimum details required (a registration will not be possible without meeting this requirement).
2.02 Player accounts.
A player profile registered using an alias, avatar or logo that is considered offensive by an admin will be amended and a message sent to that user explaining why. Should the name then be replaced by another offensive (or the same) alias then that player is likely to be banned immediately without further consultation.
2.03 Player game types.
A player can only be registered for any one team for any one game type. For example a player may not be registered for two different teams that play counter strike 1.6. This applies to all teams in all game types. It makes no difference if the teams compete in different divisions or even in different league seasons, if they play the same game then you may not be registered for multiple clans. A player may freely register for teams who play different game types however.
2.04 Player account security.
A player is responsible for their own unique id account. This is to say using counter strike 1.6 as an example, if your steam id account is subject to an upheld accusation of cheating that we do not care who was using that account at that time it will be the person holding that registered account and the account itself that will be banned. It is up to the holder of the account to ensure it’s security. No debate or discussion will be entered into on this subject. If you make public or allow details of your account to be shared by a third party then you leave yourself open to this possibility and it is your duty to either keep the account personal to yourself or deal with the repercussions of failing to do so.
A players theSGL account is also subject to the same process outlined above. It is highly recommended that a player has a different log in password to their unique id account. If your theSGL account details become known by a third party then you should immediately change the password on the said account. Where you are unable to do so then contact and admin who will attempt to secure the account on your behalf and inform you of the new log in details. A site member is considered to be responsible for all content posted by that account and also for any screenshots that may be captured from that account log in on the SGLac system. Neither theSGL nor its admins are responsible for your account security nor will we ever ask for your unique account log in details or your theSGL account log in details.
2.05 Player waiting time.
After registration to a team the player in question will not be eligible to take part in any theSGL official match for that team for a period of seventy hours.
2.06 Right to registration.
TheSGL reserves the right to deny registration or remove any player from theSGL at any time with or without given reason.
3.00 Team eligibility :A player must be registered on the website www.theSGL.com and have a profile that includes at least the minimum details required (a registration will not be possible without meeting this requirement).
2.02 Player accounts.
A player profile registered using an alias, avatar or logo that is considered offensive by an admin will be amended and a message sent to that user explaining why. Should the name then be replaced by another offensive (or the same) alias then that player is likely to be banned immediately without further consultation.
2.03 Player game types.
A player can only be registered for any one team for any one game type. For example a player may not be registered for two different teams that play counter strike 1.6. This applies to all teams in all game types. It makes no difference if the teams compete in different divisions or even in different league seasons, if they play the same game then you may not be registered for multiple clans. A player may freely register for teams who play different game types however.
2.04 Player account security.
A player is responsible for their own unique id account. This is to say using counter strike 1.6 as an example, if your steam id account is subject to an upheld accusation of cheating that we do not care who was using that account at that time it will be the person holding that registered account and the account itself that will be banned. It is up to the holder of the account to ensure it’s security. No debate or discussion will be entered into on this subject. If you make public or allow details of your account to be shared by a third party then you leave yourself open to this possibility and it is your duty to either keep the account personal to yourself or deal with the repercussions of failing to do so.
A players theSGL account is also subject to the same process outlined above. It is highly recommended that a player has a different log in password to their unique id account. If your theSGL account details become known by a third party then you should immediately change the password on the said account. Where you are unable to do so then contact and admin who will attempt to secure the account on your behalf and inform you of the new log in details. A site member is considered to be responsible for all content posted by that account and also for any screenshots that may be captured from that account log in on the SGLac system. Neither theSGL nor its admins are responsible for your account security nor will we ever ask for your unique account log in details or your theSGL account log in details.
2.05 Player waiting time.
After registration to a team the player in question will not be eligible to take part in any theSGL official match for that team for a period of seventy hours.
2.06 Right to registration.
TheSGL reserves the right to deny registration or remove any player from theSGL at any time with or without given reason.
3.01 Team registration.
A team must be registered on the website www.theSGL.com and have a profile that includes at least the minimum details required (a registration will not be possible without meeting this requirement).
3.02 Team accounts.
A team profile registered using an alias or clan logo that is considered offensive by an admin will be amended and a message sent to the registrant explaining why. Should the name then be replaced by another offensive (or the same) alias then that team is likely to be banned immediately without further consultation along with any and all members of that team deemed to be responsible and of “leader” status.
3.03 Team account security.
The team account is administered and controlled by the person orginally registering that team. That user may elect to promote fellow clan member to leader status at that point they no longer have full contol of that team and leave themselves open to a team takeover which would be handled as decribed in rule 7.03
3.04 Right to registration.
theSGL reserves the right to deny registration or remove any team from theSGL at any time with or without given reason.
3.05 Banned players.
Players that are subject to suspension or ban from theSGL who attempt to take part under another identity or account will be removed from theSGL permanently. Further to this a team who allow such a player to take part in their theSGL competitive play may be deemed complicit and in some cases removed also - with suspensions and or bans being attached to the accounts of the playing members of the said team. Another possible outcome of the use of such a player may well be a points deduction against the team involved.
3.06 Disciplinary measures.
Disciplinary measures may be levelled against teams or players who are in breach of the rules laid out here which may include but will not be limited to a suspension of an arbitrary length, a total ban from all theSGL competition forever or the removal of points a team has gained in a theSGL event.
4.00 General in game rules :A team must be registered on the website www.theSGL.com and have a profile that includes at least the minimum details required (a registration will not be possible without meeting this requirement).
3.02 Team accounts.
A team profile registered using an alias or clan logo that is considered offensive by an admin will be amended and a message sent to the registrant explaining why. Should the name then be replaced by another offensive (or the same) alias then that team is likely to be banned immediately without further consultation along with any and all members of that team deemed to be responsible and of “leader” status.
3.03 Team account security.
The team account is administered and controlled by the person orginally registering that team. That user may elect to promote fellow clan member to leader status at that point they no longer have full contol of that team and leave themselves open to a team takeover which would be handled as decribed in rule 7.03
3.04 Right to registration.
theSGL reserves the right to deny registration or remove any team from theSGL at any time with or without given reason.
3.05 Banned players.
Players that are subject to suspension or ban from theSGL who attempt to take part under another identity or account will be removed from theSGL permanently. Further to this a team who allow such a player to take part in their theSGL competitive play may be deemed complicit and in some cases removed also - with suspensions and or bans being attached to the accounts of the playing members of the said team. Another possible outcome of the use of such a player may well be a points deduction against the team involved.
3.06 Disciplinary measures.
Disciplinary measures may be levelled against teams or players who are in breach of the rules laid out here which may include but will not be limited to a suspension of an arbitrary length, a total ban from all theSGL competition forever or the removal of points a team has gained in a theSGL event.
4.01 Custom content.
Custom models and skins are not permitted in any theSGL match where the use of such skin or model gives advantage (however slight) to the participant using them. Models such as the high-fps versions will be allowed however brightly coloured or otherwise misshapen models will not. For games such as counter strike where there is often problems between the CZ and 1.6 models being installed then either model set will be acceptable.
4.02 Client variables.
A lists of unacceptable cvars is available here for your relevant game type. These are the most up to date listing we have but are not exclusive to other command not contained therein which you may be requested to change at any time by an appointed league admin.
4.03 Player unique ID.
A player must meet the requirements laid out in section 2.00
4.04 Sportsmanship
Players will at all times refrain from abuse toward opposing teams or appointed admins. There is a strict ban on racism in particular though we do not wish to see any abuse of any shape or form either on a match server or in an IRC channel (or private message chat)
4.05 Abusive use of crouch command.
Otherwise known as "Russian walking". This technique must not be used whether as the result of a script or by manually causing it. Some may define it as a skill, we however define it as exploiting the game and not playing as the game was intended. This technique is banned. Players caught using the crouch command in an unsportsmanlike manner will cause their team to default a round.
5.00 The league :Custom models and skins are not permitted in any theSGL match where the use of such skin or model gives advantage (however slight) to the participant using them. Models such as the high-fps versions will be allowed however brightly coloured or otherwise misshapen models will not. For games such as counter strike where there is often problems between the CZ and 1.6 models being installed then either model set will be acceptable.
4.02 Client variables.
A lists of unacceptable cvars is available here for your relevant game type. These are the most up to date listing we have but are not exclusive to other command not contained therein which you may be requested to change at any time by an appointed league admin.
4.03 Player unique ID.
A player must meet the requirements laid out in section 2.00
4.04 Sportsmanship
Players will at all times refrain from abuse toward opposing teams or appointed admins. There is a strict ban on racism in particular though we do not wish to see any abuse of any shape or form either on a match server or in an IRC channel (or private message chat)
4.05 Abusive use of crouch command.
Otherwise known as "Russian walking". This technique must not be used whether as the result of a script or by manually causing it. Some may define it as a skill, we however define it as exploiting the game and not playing as the game was intended. This technique is banned. Players caught using the crouch command in an unsportsmanlike manner will cause their team to default a round.
5.01 League title.
The league shall be knows as the “ theSGL.com” a sponsors name may be appended to this title and should be used in full when posting about or reporting on the league.
5.02 Divisional format.
A standard league division will consist of ten teams each of whom will play the other teams once with one match each week on a map decided by the prevailing map rotation for that week. We reserve the right to change the map that any match may be played on at any point if good reasons should present itself.
5.03 Points distribution.
Teams will gain three points for a win, one point for a tied match and no points for losing a match. Winning a match by default will be rewarded with the full three points, the defaulting team will receive no points and neither team will receive any rounds scored for and against them.
5.04 Promotion and relegation.
In an invitational league promotion and relegation are not valid factors. For all league divisions which are not invitational then the minimum of the top two teams will be promoted and the bottom two teams relegated. In some cases where felt to be appropriate there may be more relegations and promotions than this
5.05 Tied teams.
Teams who are tied on points at the end of a season will be separated n the basis of which team came out as winner when the two teams met during the league season. Where one team came in to the event late and did not meet the opposition then the result which stood from the team they replaced will be considered the result of that match. Should teams have drawn in that match then the placing will be decided by the total number of rounds for (highest wins). In the event that the teams remain tied at this point then a playoff may be organised by a league admin.
6.00 Match rules :The league shall be knows as the “ theSGL.com” a sponsors name may be appended to this title and should be used in full when posting about or reporting on the league.
5.02 Divisional format.
A standard league division will consist of ten teams each of whom will play the other teams once with one match each week on a map decided by the prevailing map rotation for that week. We reserve the right to change the map that any match may be played on at any point if good reasons should present itself.
5.03 Points distribution.
Teams will gain three points for a win, one point for a tied match and no points for losing a match. Winning a match by default will be rewarded with the full three points, the defaulting team will receive no points and neither team will receive any rounds scored for and against them.
5.04 Promotion and relegation.
In an invitational league promotion and relegation are not valid factors. For all league divisions which are not invitational then the minimum of the top two teams will be promoted and the bottom two teams relegated. In some cases where felt to be appropriate there may be more relegations and promotions than this
5.05 Tied teams.
Teams who are tied on points at the end of a season will be separated n the basis of which team came out as winner when the two teams met during the league season. Where one team came in to the event late and did not meet the opposition then the result which stood from the team they replaced will be considered the result of that match. Should teams have drawn in that match then the placing will be decided by the total number of rounds for (highest wins). In the event that the teams remain tied at this point then a playoff may be organised by a league admin.
6.01 Match format
A match will consist of one map played in a best of thirty rounds format. The first team to reach sixteen rounds will be declared the winner. One round will be one minute forty five seconds in duration.
6.02 Joining the server.
Unless agreed to the contrary players should join the server on time for their match. A maximum of ten minutes will be given after this time until the match begins. Teams should obtain the server details (theSGL match details page or SGLo matches please contact your opponent) and ensure that their SGLac is running properly in advance of the match.
6.03 Designating the server.
In a theSGL league match the server ip will assigned to the match and displayed on the match details page prior to the game.
6.04 Players.
Each team should field five players from their roster on this website. The players must all have their steam id entered on the roster and be eligible to play (no waiting time on their roster e.g. eligible to play in 36 hours). If a player is not eligible to play due to having not entered their steam id more than 72 hours in advance of the tie then that player may take part at the oppositions discretion however if they decline to allow it then that player must not take part in the match. Likewise where a player who does not feature on the roster at all is attempting to play then the opposing team may grant that player permission to play (in this instance the player must be added to the roster before the match begins) or they may exercise their right to deny the player permission to take part. A team may play with less than five players but no less than four. Should the opposing team wish to drop players themselves to even up the teams then they may do so - but they do not have to. For SGLo matches, the check on the steam must be performed prior to the match as complaints or conflictions after the match has taken place will not be upheld (unless a player joins the server mid match in which case a screenshot of their steam id should be taken).
6.05 Substitutions.
A team may substitute as many players as they wish during the course of a game though at no point must they have more than five players connected to the server. A player joining the match must move from spectator to the relevant team immediately on connection to the server. Players remaining in spectator mode for any length of time will result in rounds being declared forfeit and the player will be kicked from the server.
6.06 Voice communications.
Third party voice communication software may be used. Should a team experience difficulties with such a program then this will not be cause for pausing or halting the match, it is a teams own responsibility to ensure the operation of any such voice communication software.
6.07 Half time.
Teams must allow for a maximum five minute break at the end of the first round though it is preferable to play through without a break. For SGLo matches, should the teams agree to a longer break then this is entirely at their own discretion. A screenshot should also be taken at this point to verify the first half score.
6.08 Tied games.
Matches which end with a score of 15-15 will be considered a draw and overtime to decide a winner is not required. One point will be awarded to each team.
6.09 Finishing the match.
As soon as one team has acheived a 16 round total the match is considered finished with the score at that being the final result. We do not object to all the rounds being played, but the final score will be 16-xx or in the event of a draw 15-15. The teams may leave the server at this point and no rounds will be forfeit. If a team leaves the server before a victory or draw has been achieved then all remaining rounds up to a total of sixteen will be awarded to the team remaining on the server.
6.10 Reporting the result.
The match admin will report and enter the score onto theSGL website. In anSGLo match the score must be reported by both teams. Only the leader or co leader of a team can report the result which should be sent my private message (until the self entering page has been added to the site) to the admin for your division (who is listed on the league tables page).
6.11 Specific in game rules.
Team choice will be handled by the age old practice of the slice and dice. The winning team may choose whether to start as ct or t on the map. If a player is injured by gunfire/grenade coming from the opposition his team may claim the knife round by default immediately. However , flashbangs and smoke are permitted.
In the event that one or more players from each team are alive at the end of the knife round , the teams should "stay" and begin the match. If a team deliberately avoids the opponents in the knife round so that the round times out, the choice of teams may be given to the opponents at the match admin's discretion.
Grenades or flashes may be thrown over any roof or wall. IE - top of the alley into bomb site on de_inferno , or over wall into bomb site b on de_dust2. However , the use of known bugs ( such as flashing between the boxes in site b on dust2 , to gain an unfair advantage by "illegally" flashing opponents who are inside the house/tunnels ) will be regarded as an exploit. A team may forfeit the round in question should a complaint be upheld by the admin. a simple comment typed in to alert the admin to the violation , will allow the admin to review the round later on hltv. the admin may award the round against the offenders at his discretion.
To avoid the flashbug issue entirely we recommend the use of the Drax fixed maps pack which is available from our download section. The server requires them to be installed however players do not need to install any files to make them work.
Shields are not to be used in any match. Should a player use a shield wether or not they bought it themself, they will be asked to discard the item. Should they fail to immediatly so then that players team shall forfeit that round.
All rates and server settings are enforced by theSGL configuration files and must not be changed. This ensures everyone plays under the same set of rules for each match.
The duck walk exploit is specifically banned and will be cause for a round default where detected.
6.12 Defaults.
Where a fixure is in default by one of the teams the oppposition will recieve a win and be awarded three points. No rounds for or against will be entered into the league table.
6.13 Wildcards.
Each team has one wildcard per season and therefore can put off any one fixture at any time before the day of the fixture. For eg a fixture on a Wednesday can be wildcarded at any time up until midnight on the Tuesday. This must be done by personally contacting a senior admin in IRC and recieving a reply. Messages left on a BNC will not be considered to be valid notice - ensure you recieve a reply.
6.14 Rescheduling a match.
Where both teams agree to reschedule a match no wildcard will be used up for either team. The scheduling of the match will be subject to approval from a senior theSGL admin except in matches within the SGLo which must be reported as being subject to reschedule to your divisional admin. A comment from a amember fromeach team on the match details page is required to ensure that both teams have agreed to this.
6.15 Recording demos.
All participants are requested to record a personal point of view demo and must make available the said demo if and when they are requested to do so by a league admin. Failure to present such a demo when requested may result in suspension, removal or loss of team points. POV demos do not need to be uploaded to the website but should be retained for a period of four weeks and made available to a league admin if requested.
HLTV demos of matches will be made available on the match details page as and when they become available to us. In SGLo matches we request that the HLTV demo is uploaded by the home team to the match results page. Failure to do so may lead to a loss of points or forfeit for that team.
7.00 Team rules :A match will consist of one map played in a best of thirty rounds format. The first team to reach sixteen rounds will be declared the winner. One round will be one minute forty five seconds in duration.
6.02 Joining the server.
Unless agreed to the contrary players should join the server on time for their match. A maximum of ten minutes will be given after this time until the match begins. Teams should obtain the server details (theSGL match details page or SGLo matches please contact your opponent) and ensure that their SGLac is running properly in advance of the match.
6.03 Designating the server.
In a theSGL league match the server ip will assigned to the match and displayed on the match details page prior to the game.
6.04 Players.
Each team should field five players from their roster on this website. The players must all have their steam id entered on the roster and be eligible to play (no waiting time on their roster e.g. eligible to play in 36 hours). If a player is not eligible to play due to having not entered their steam id more than 72 hours in advance of the tie then that player may take part at the oppositions discretion however if they decline to allow it then that player must not take part in the match. Likewise where a player who does not feature on the roster at all is attempting to play then the opposing team may grant that player permission to play (in this instance the player must be added to the roster before the match begins) or they may exercise their right to deny the player permission to take part. A team may play with less than five players but no less than four. Should the opposing team wish to drop players themselves to even up the teams then they may do so - but they do not have to. For SGLo matches, the check on the steam must be performed prior to the match as complaints or conflictions after the match has taken place will not be upheld (unless a player joins the server mid match in which case a screenshot of their steam id should be taken).
6.05 Substitutions.
A team may substitute as many players as they wish during the course of a game though at no point must they have more than five players connected to the server. A player joining the match must move from spectator to the relevant team immediately on connection to the server. Players remaining in spectator mode for any length of time will result in rounds being declared forfeit and the player will be kicked from the server.
6.06 Voice communications.
Third party voice communication software may be used. Should a team experience difficulties with such a program then this will not be cause for pausing or halting the match, it is a teams own responsibility to ensure the operation of any such voice communication software.
6.07 Half time.
Teams must allow for a maximum five minute break at the end of the first round though it is preferable to play through without a break. For SGLo matches, should the teams agree to a longer break then this is entirely at their own discretion. A screenshot should also be taken at this point to verify the first half score.
6.08 Tied games.
Matches which end with a score of 15-15 will be considered a draw and overtime to decide a winner is not required. One point will be awarded to each team.
6.09 Finishing the match.
As soon as one team has acheived a 16 round total the match is considered finished with the score at that being the final result. We do not object to all the rounds being played, but the final score will be 16-xx or in the event of a draw 15-15. The teams may leave the server at this point and no rounds will be forfeit. If a team leaves the server before a victory or draw has been achieved then all remaining rounds up to a total of sixteen will be awarded to the team remaining on the server.
6.10 Reporting the result.
The match admin will report and enter the score onto theSGL website. In anSGLo match the score must be reported by both teams. Only the leader or co leader of a team can report the result which should be sent my private message (until the self entering page has been added to the site) to the admin for your division (who is listed on the league tables page).
6.11 Specific in game rules.
Team choice will be handled by the age old practice of the slice and dice. The winning team may choose whether to start as ct or t on the map. If a player is injured by gunfire/grenade coming from the opposition his team may claim the knife round by default immediately. However , flashbangs and smoke are permitted.
In the event that one or more players from each team are alive at the end of the knife round , the teams should "stay" and begin the match. If a team deliberately avoids the opponents in the knife round so that the round times out, the choice of teams may be given to the opponents at the match admin's discretion.
Grenades or flashes may be thrown over any roof or wall. IE - top of the alley into bomb site on de_inferno , or over wall into bomb site b on de_dust2. However , the use of known bugs ( such as flashing between the boxes in site b on dust2 , to gain an unfair advantage by "illegally" flashing opponents who are inside the house/tunnels ) will be regarded as an exploit. A team may forfeit the round in question should a complaint be upheld by the admin. a simple comment typed in to alert the admin to the violation , will allow the admin to review the round later on hltv. the admin may award the round against the offenders at his discretion.
To avoid the flashbug issue entirely we recommend the use of the Drax fixed maps pack which is available from our download section. The server requires them to be installed however players do not need to install any files to make them work.
Shields are not to be used in any match. Should a player use a shield wether or not they bought it themself, they will be asked to discard the item. Should they fail to immediatly so then that players team shall forfeit that round.
All rates and server settings are enforced by theSGL configuration files and must not be changed. This ensures everyone plays under the same set of rules for each match.
The duck walk exploit is specifically banned and will be cause for a round default where detected.
6.12 Defaults.
Where a fixure is in default by one of the teams the oppposition will recieve a win and be awarded three points. No rounds for or against will be entered into the league table.
6.13 Wildcards.
Each team has one wildcard per season and therefore can put off any one fixture at any time before the day of the fixture. For eg a fixture on a Wednesday can be wildcarded at any time up until midnight on the Tuesday. This must be done by personally contacting a senior admin in IRC and recieving a reply. Messages left on a BNC will not be considered to be valid notice - ensure you recieve a reply.
6.14 Rescheduling a match.
Where both teams agree to reschedule a match no wildcard will be used up for either team. The scheduling of the match will be subject to approval from a senior theSGL admin except in matches within the SGLo which must be reported as being subject to reschedule to your divisional admin. A comment from a amember fromeach team on the match details page is required to ensure that both teams have agreed to this.
6.15 Recording demos.
All participants are requested to record a personal point of view demo and must make available the said demo if and when they are requested to do so by a league admin. Failure to present such a demo when requested may result in suspension, removal or loss of team points. POV demos do not need to be uploaded to the website but should be retained for a period of four weeks and made available to a league admin if requested.
HLTV demos of matches will be made available on the match details page as and when they become available to us. In SGLo matches we request that the HLTV demo is uploaded by the home team to the match results page. Failure to do so may lead to a loss of points or forfeit for that team.
7.01 Rosters
A team manager or leader is responsible for knowing who is playing for that team. A roster must contain enough eligible players for the teams next match at all times. Failure to maintain such a roster may result in your team being replaced. Should you drop to less than this amount of players then you should inform a league admin as soon as the problem is manifested and inform them of your subsequent intention or explain with good reason why this has occurred. Obviously your team will require a roster of five eligible players to play in a counterstrike match.
7.02 Takeovers
A team accepted into theSGL is accepted on the understanding that they are the team who then subsequently compete in the event. A place awarded to a team is not the property of a team manager or owner and they therefore have no right to hand over the place awarded to another clan. At all times a clan must retain 60% of their original roster . Should a team have less than this amount then at an admins discretion they be replaced by another team.
7.03 Mercenaries
At no time must a team field a player who is not shown on their roster. Should it be proven that a player other than the registered account holder has participated in a match then that players account may be suspended or banned, further to this the team in question may have points removed and/or be suspended or banned for being complicit in the breaking of this rule.
7.04 Team names.
Any change made to the name of team competing in an theSGL event should be notified to a league admin as soon as possible. Team names found to be offensive or otherwise inappropriate may be requested to amend their name by a league admin, failure to comply with such a request may lead to the removal or replacement of the said team.
7.05 Team ownership.
The player who registers a team shall be considered the leader of that team. They may choose to elect co-leaders or full leaders equal in rank to themselves but they shall remain the nominated owner of that team. Should a team require removal of their owner then they should contact a league admin. We will require at least 60% of the said team to agree with the decision to oust the owner for this to go ahead.
8.00 Servers :A team manager or leader is responsible for knowing who is playing for that team. A roster must contain enough eligible players for the teams next match at all times. Failure to maintain such a roster may result in your team being replaced. Should you drop to less than this amount of players then you should inform a league admin as soon as the problem is manifested and inform them of your subsequent intention or explain with good reason why this has occurred. Obviously your team will require a roster of five eligible players to play in a counterstrike match.
7.02 Takeovers
A team accepted into theSGL is accepted on the understanding that they are the team who then subsequently compete in the event. A place awarded to a team is not the property of a team manager or owner and they therefore have no right to hand over the place awarded to another clan. At all times a clan must retain 60% of their original roster . Should a team have less than this amount then at an admins discretion they be replaced by another team.
7.03 Mercenaries
At no time must a team field a player who is not shown on their roster. Should it be proven that a player other than the registered account holder has participated in a match then that players account may be suspended or banned, further to this the team in question may have points removed and/or be suspended or banned for being complicit in the breaking of this rule.
7.04 Team names.
Any change made to the name of team competing in an theSGL event should be notified to a league admin as soon as possible. Team names found to be offensive or otherwise inappropriate may be requested to amend their name by a league admin, failure to comply with such a request may lead to the removal or replacement of the said team.
7.05 Team ownership.
The player who registers a team shall be considered the leader of that team. They may choose to elect co-leaders or full leaders equal in rank to themselves but they shall remain the nominated owner of that team. Should a team require removal of their owner then they should contact a league admin. We will require at least 60% of the said team to agree with the decision to oust the owner for this to go ahead.
8.01 Server assignment.
In a theSGL league match the server ip will assigned to the match and displayed on the match details page prior to the game.
8.02 Server configuration.
The match must be run using the official configuration files supplied by theSGL. you can download the files on this link. Included in this archive are an sglmr15.cfg which must be run prior to the match to load official match settings, an sgllo3.cfg to make the match live and two "wait.cfgs" which stop the settings being issued to the server too quickly and ensures all settings are in fact loaded.
8.03 Server crashes.
Should a match server crash during a match then these guidelines should be followed. If less than three full rounds have been played in a half then the half will be restarted from the beginning. For matches where the server crashes after three whole rounds have been played the match will be restarted at the score the match was at prior to the server crash but mp_startmoney will be set to 5000. This is regardless of the money situation at the time of the crash.
In a match which is not on an server provided by theSGL and the team not hosting the match request it, server logs proving that the server crash was not triggered by a command sent to it by the home team will be required. This is to say that if you are off to a bad start and decide to restart the server to give yourselves another chance you will default the match entirely and will face other disciplined the senior admin team see fit.
8.04 HLTV proxies.
All matches must be played with a recording HLTV proxy on the server. The details required to view the match in progress must be available to both teams. Where the proxy is only for recording purposes and has no spectator slots then the details should still be made available to both competing teams to allow this fact to be verified. The HLTV demo must be made available to both teams and retained in the event of an admin requesting it.
8.05 Scorebot
A scorebot relaying a description of the match in progress may be used but must be agreed to by both teams involved in the match, The scorebot should only report kills/rounds and other relevant details. Text typed by players on the server both in team only say and server say modes must not be relayed by scorebot.
8.06 Connection problems.
A participant is responsible for his own connection at all times. Should the player suffer from connection problems including high pings, intermittent connection loss or similar problems then a pause of no more than five minutes should be made to allow a reboot and reconnect to the server. A team may have no more than two such pauses in any one match unless the opposition specifically indicates that they will allow it. This is at the discretion of the teams involved but under no circumstances will a team have less than two pauses of up to a five minute duration allowed. This does not allow a team the total or ten minutes of pause time, it allows two pauses of up to five minutes each.
9.00 SGLac :In a theSGL league match the server ip will assigned to the match and displayed on the match details page prior to the game.
8.02 Server configuration.
The match must be run using the official configuration files supplied by theSGL. you can download the files on this link. Included in this archive are an sglmr15.cfg which must be run prior to the match to load official match settings, an sgllo3.cfg to make the match live and two "wait.cfgs" which stop the settings being issued to the server too quickly and ensures all settings are in fact loaded.
8.03 Server crashes.
Should a match server crash during a match then these guidelines should be followed. If less than three full rounds have been played in a half then the half will be restarted from the beginning. For matches where the server crashes after three whole rounds have been played the match will be restarted at the score the match was at prior to the server crash but mp_startmoney will be set to 5000. This is regardless of the money situation at the time of the crash.
In a match which is not on an server provided by theSGL and the team not hosting the match request it, server logs proving that the server crash was not triggered by a command sent to it by the home team will be required. This is to say that if you are off to a bad start and decide to restart the server to give yourselves another chance you will default the match entirely and will face other disciplined the senior admin team see fit.
8.04 HLTV proxies.
All matches must be played with a recording HLTV proxy on the server. The details required to view the match in progress must be available to both teams. Where the proxy is only for recording purposes and has no spectator slots then the details should still be made available to both competing teams to allow this fact to be verified. The HLTV demo must be made available to both teams and retained in the event of an admin requesting it.
8.05 Scorebot
A scorebot relaying a description of the match in progress may be used but must be agreed to by both teams involved in the match, The scorebot should only report kills/rounds and other relevant details. Text typed by players on the server both in team only say and server say modes must not be relayed by scorebot.
8.06 Connection problems.
A participant is responsible for his own connection at all times. Should the player suffer from connection problems including high pings, intermittent connection loss or similar problems then a pause of no more than five minutes should be made to allow a reboot and reconnect to the server. A team may have no more than two such pauses in any one match unless the opposition specifically indicates that they will allow it. This is at the discretion of the teams involved but under no circumstances will a team have less than two pauses of up to a five minute duration allowed. This does not allow a team the total or ten minutes of pause time, it allows two pauses of up to five minutes each.
9.01 Abour SGLac. (SGLac can be downloaded here)
SGLac is a client side program that achieves several things. Firstly it will capture a random number of screenshots from a player taken at random intervals during use. Secondly it will perform a scan of the user machine local memory and compare processes found against a list of known cheat programs. SGLac will also upload a copy of the users cfg for public view. All users will be subject to a graphics bit detection and clients running less than 32bit will be diconnected from the SGLac enforced servers.
9.02 Screenshot upload.
Screen capture will commence when you enter the game. A random number of screenshots will be captured at random intervals and stored locally on your machine until you exit the game. At this point SGLac will then upload the shots to our website where they will be viewable on your player profile page. Whilst every effort is made to avoid out of game screenshots being taken it must be noted that a very small number of out of game (desktops for e.g.) screenshots are captured accidentally. Whilst a user should take every care to remove from view any personal or security compromising items from view we will do our best to remove individual screenshots that you may bring to our attention. Due to the secure nature of the image storage we have in place this is not an instant process though we will make effort to remove the item at the earliest opportunity. Ine view of the possibility outlined above we recommend rcon commands are entered through HLSW or similar program and not via the in game console which is subject to screen capture.
9.03 Configuration file upload.
Certain game types (currently the steam based games only) will have their player cfg files checked and placed on public display in the same manner as the screenshots Whilst a user should take every care to remove any personal or security compromising items from the player cfg file we will do our best to remove individual cfg’s that you may bring to our attention. Due to the secure nature of the image storage we have in place this is not an instant process though we will make effort to remove the item at the earliest opportunity.
9.04 Active cheat detection.
SGLac will scan your local memory processes and compare them to a list of known cheat programs. SGLac will not scan or check any area of your local storage or any of the files contained therein neither will it make the results of the local memory process check public to anyone including theSGL admin team unless a positive match is made or cheat detected at which time this information will be made known to only the senior admins.
9.05 SGLac required servers.
On an SGLac compulsory server a player will be kicked if that player is not running the SGLac client program. You can request your server to be SGLac enabled from this page (A small fee is payable as described on the page, however all Dustworld customers may request SGLac as a free service.
Players may also take advantage of a one time fee which will enable them to use SGLac on any server they wish whever they wish.
10.00 Intellectual property :SGLac is a client side program that achieves several things. Firstly it will capture a random number of screenshots from a player taken at random intervals during use. Secondly it will perform a scan of the user machine local memory and compare processes found against a list of known cheat programs. SGLac will also upload a copy of the users cfg for public view. All users will be subject to a graphics bit detection and clients running less than 32bit will be diconnected from the SGLac enforced servers.
9.02 Screenshot upload.
Screen capture will commence when you enter the game. A random number of screenshots will be captured at random intervals and stored locally on your machine until you exit the game. At this point SGLac will then upload the shots to our website where they will be viewable on your player profile page. Whilst every effort is made to avoid out of game screenshots being taken it must be noted that a very small number of out of game (desktops for e.g.) screenshots are captured accidentally. Whilst a user should take every care to remove from view any personal or security compromising items from view we will do our best to remove individual screenshots that you may bring to our attention. Due to the secure nature of the image storage we have in place this is not an instant process though we will make effort to remove the item at the earliest opportunity. Ine view of the possibility outlined above we recommend rcon commands are entered through HLSW or similar program and not via the in game console which is subject to screen capture.
9.03 Configuration file upload.
Certain game types (currently the steam based games only) will have their player cfg files checked and placed on public display in the same manner as the screenshots Whilst a user should take every care to remove any personal or security compromising items from the player cfg file we will do our best to remove individual cfg’s that you may bring to our attention. Due to the secure nature of the image storage we have in place this is not an instant process though we will make effort to remove the item at the earliest opportunity.
9.04 Active cheat detection.
SGLac will scan your local memory processes and compare them to a list of known cheat programs. SGLac will not scan or check any area of your local storage or any of the files contained therein neither will it make the results of the local memory process check public to anyone including theSGL admin team unless a positive match is made or cheat detected at which time this information will be made known to only the senior admins.
9.05 SGLac required servers.
On an SGLac compulsory server a player will be kicked if that player is not running the SGLac client program. You can request your server to be SGLac enabled from this page (A small fee is payable as described on the page, however all Dustworld customers may request SGLac as a free service.
Players may also take advantage of a one time fee which will enable them to use SGLac on any server they wish whever they wish.
10.01 Casting matches
All theSGL sanctioned matches are the property of theSGL.com and we reserve the right to broadcast, report and promote the fixtures and content of these matches however we see fit. Any team wishing to broadcast in any way the content of a theSGL sanctioned match must first seek and obtain permission from a head admin of theSGL.com. You will not copy, download, reproduce, republish, frame, broadcast, transmit in any manner whatsoever, any material or player created content from theSGL.com except as is strictly necessary for your own personal non-commercial home use.
All copyright, trade marks and all other intellectual property rights in all material or content supplied as part of theSGL.com shall remain at all times vested in Us or Our licensors. You are permitted to use this material or content only as expressly authorised in writing by Us or Our licensors. You will not, and You will not assist or facilitate any third party to, copy, reproduce, transmit, distribute, frame, commercially exploit or create derivative works of such material or content.
Current approved broadcasters of theSGL content are limited to wwwQuadV.com . Unauthorised broadcast of matches by other parties will lead to matches being declared void.
11.00 Disputes :All theSGL sanctioned matches are the property of theSGL.com and we reserve the right to broadcast, report and promote the fixtures and content of these matches however we see fit. Any team wishing to broadcast in any way the content of a theSGL sanctioned match must first seek and obtain permission from a head admin of theSGL.com. You will not copy, download, reproduce, republish, frame, broadcast, transmit in any manner whatsoever, any material or player created content from theSGL.com except as is strictly necessary for your own personal non-commercial home use.
All copyright, trade marks and all other intellectual property rights in all material or content supplied as part of theSGL.com shall remain at all times vested in Us or Our licensors. You are permitted to use this material or content only as expressly authorised in writing by Us or Our licensors. You will not, and You will not assist or facilitate any third party to, copy, reproduce, transmit, distribute, frame, commercially exploit or create derivative works of such material or content.
Current approved broadcasters of theSGL content are limited to wwwQuadV.com . Unauthorised broadcast of matches by other parties will lead to matches being declared void.
11.01 General dispute information.
Disputes are not a public matter and should only be handled by an Admin. Teams found posting disputes on public forums will be punished. A formal dispute must be filed within 72 hours of the match
If POV demos are requested by an admin and are not available due to corruption (unless server crash in which case it is expected that you immediately record a NEW demo on reconnection to the server) or if rounds are missing expect a suspension or ban. Team points may also be forfeit in certain cases
You may only dispute one player at a time on a player by player basis. If you suspect multiple players of cheating, individual disputes should be made with evidence.
Before you can submit a legitimate dispute you must have watched the HLTV demo of the match, watching the player in. Make a list of the rounds and moments in question e.g. “Round 1 – Looks at player through wall and pops out when player X takes a flash out. Round 5 – Reacts to flash before he can see it.” The more examples you give, the more seriously your dispute will be taken. Once a dispute has been filed, the dispute review team will request the player in question’s POV demo (if not already requested by the match admin) and analyse the demo.
The dispute review panel decision shall be final in all instances.
11.02 Suspensions, bans and points deduction.
Players who are accused of cheating outside theSGL and are brought to our attention will be investigated and may be suspended or banned from theSGL competition. The evidence required for such a censure will be equal and exact to the evidence required by www.steambans.com and even then will be subject to considered opinion by our admin team.
Persons bringing to our attention false accusations may be subject to disciplinary measures themselves. We do not take lightly a person who deliberately sets out to discredit another player intentionally.
Players caught cheating within a theSGL competitive match will be banned forever from all theSGL events (be they online or indeed at LAN). Such a player or team incorporating that player found to be subsequently taking part in theSGL events will be subject to the penalties as described in 3.05 Banned players.
For certain infringements and at the admins discretion where rules have been broken or repeatedly ignored a points deduction may be awarded against an offending team
12.00 Convention : Disputes are not a public matter and should only be handled by an Admin. Teams found posting disputes on public forums will be punished. A formal dispute must be filed within 72 hours of the match
If POV demos are requested by an admin and are not available due to corruption (unless server crash in which case it is expected that you immediately record a NEW demo on reconnection to the server) or if rounds are missing expect a suspension or ban. Team points may also be forfeit in certain cases
You may only dispute one player at a time on a player by player basis. If you suspect multiple players of cheating, individual disputes should be made with evidence.
Before you can submit a legitimate dispute you must have watched the HLTV demo of the match, watching the player in. Make a list of the rounds and moments in question e.g. “Round 1 – Looks at player through wall and pops out when player X takes a flash out. Round 5 – Reacts to flash before he can see it.” The more examples you give, the more seriously your dispute will be taken. Once a dispute has been filed, the dispute review team will request the player in question’s POV demo (if not already requested by the match admin) and analyse the demo.
The dispute review panel decision shall be final in all instances.
11.02 Suspensions, bans and points deduction.
Players who are accused of cheating outside theSGL and are brought to our attention will be investigated and may be suspended or banned from theSGL competition. The evidence required for such a censure will be equal and exact to the evidence required by www.steambans.com and even then will be subject to considered opinion by our admin team.
Persons bringing to our attention false accusations may be subject to disciplinary measures themselves. We do not take lightly a person who deliberately sets out to discredit another player intentionally.
Players caught cheating within a theSGL competitive match will be banned forever from all theSGL events (be they online or indeed at LAN). Such a player or team incorporating that player found to be subsequently taking part in theSGL events will be subject to the penalties as described in 3.05 Banned players.
For certain infringements and at the admins discretion where rules have been broken or repeatedly ignored a points deduction may be awarded against an offending team
12.01 theSGL.com
The league shall be known as “The Suicide Gaming League” which we abbreviate to “theSGL”
12.02 Definition of admin.-
An admin will be deemed as being a person appointed by theSGL to officiate in matters relating to theSGL
12.03 Rule update.
We reserve the right to change any or all of these rules at any time. You should keep checking the rules to ensure you don’t breach them. If you see anything you believe to be incorrect or missing please inform a league admin.
The league shall be known as “The Suicide Gaming League” which we abbreviate to “theSGL”
12.02 Definition of admin.-
An admin will be deemed as being a person appointed by theSGL to officiate in matters relating to theSGL
12.03 Rule update.
We reserve the right to change any or all of these rules at any time. You should keep checking the rules to ensure you don’t breach them. If you see anything you believe to be incorrect or missing please inform a league admin.
Steelseries
Main sponsors
Coverage by
News partners
Supported by
