Generic Rules

1.10 Introduction

The NSPlayer tournament rule set has been based primarily upon the foundations of the Cyberathlete Amateur League, Natural Selection division. It hopes to allow fair and fun games of competitive NS. Specific details about the style, structure and fixtures of the tournament or league can be found on the NSPlayer website regarding that event. All matches will be held using the latest public release of Natural Selection.

1.20 Definitions

· ROUND - One session of continuos play where players remain in the same team for the duration, and only a single victory event occurs.
· MATCH: Full game between 2 teams, will generally include two rounds and a possible third tiebreaker.
· SERVER: Any approved or NSPlayer operated server.
· CAPTAIN: The player listed as the leader on the roster or any player who is officially acting as team captain in the absence of the leader.
· EXPLOIT: A bug in the game engine, physics, or a map that allows players to do things that they were not intended to be able to do.
· IRC: Internet Relay Chat, online text communication tool in a channel format. Most common client is mIRC.
· GAMESURGE: IRC server: irc.gamesurge.net
· NSPLAYER IRC CHANNEL: #NSPlayer on GameSurge.
· NSPLAYER WEBSITE: http://www.nsplayer.net

1.30 Bracket or Division Placement

Dependent on the style of tournament, clans will be placed in brackets or divisions randomly or how the NSPlayer admins and event organizers see fit to allow for fair and competitive play.To be admitted into any NSPlayer event, you must have a registered IRC channel on the GameSurge IRC Network, as well as 6 members on your roster. The leader and the scheduler will need to idle in the channel. NSPlayer reserves the right to refuse entry or remove any clans/players from any specific tournament or event.

2.10 Player Models, Skins, Sprites and Sounds

All team members must use default models, skins, and textures. This includes all weapon and player models/skins. Any player using enhanced/coloured models/skins will result in a forfeit loss for their team as well as result the probability of disciplinary action. Players must use the default files for in game play. This includes all sprites (excluding those stated below), textures, sounds, etc. Players must use the default files for the current version of NS or ones approved by NSPlayer. No replacement files are allowed. Weapon models must be used, the in game variable r_drawviewmodel must be set to 1 (enabled). Teams caught with players violating these rules may have penalties imposed; including forfeit or suspension. Changes allowed to be made include crosshairs, HUDs, minimaps, ambient sounds (that is map or environment sounds and not footsteps or other game sounds), and any config files. All other changes must seek verification by an NSPlayer admin.

2.20 Messaging

Players have an unrestricted use of messagemode2 (say_team). However messagemode1 (say) is highly restricted; any abuse, baiting, sneering, ridiculing or taunting even in the very slightest will attract an instant ban from the server and possible further suspensions. Teams may not replace a kicked member with a substitute for the remainder of that round.

2.30 Sportsmanship

All participants in NSPlayer events will be required to uphold to the highest standards and observe common sportsmanship. Failure to do so will result in disciplinary action removing the player from the game without substitute.

2.40 Conduct

Any member that belittles or demeans a tournament or official Admins will be immediately suspended until further notice. Personal attacks will not be tolerated. Individuals caught posting private conversations, logs or emails in public sites/forums or sharing the confidential information will be subject to individual penalties. Teams who post private conversations or matters on their sites will face repercussions as well. Logs and emails are not considered proof as they can be easily altered or forged. Confidential or private matters should be respected and logs from third parties should not be considered proof of any action or intention on their own.

Any accusations made in a public forum or other public media will result in a suspension against the team or individuals making the accusation. All disputes or accusations must be sent to NSPlayer admins in a private manner.

2.50 Steam Ids

All individuals competing must have their member profile completely filled out accurately. This includes filling out the Steam ID section. If any player is caught competing with a Steam ID not listed in their profile in advance, they will be suspended for one match and the team issued a forfeit loss. You are allowed only 1 Steam ID. Once a match has started, no dispute may be raised concerning Steam IDs, with the exception of players that join mid-match. Please be aware that a ringing dispute concerning individuals using Steam IDs that are not their own does not apply to this clause.

2.60 In game names

In order to expedite roster verifications during pre-game, players are required to use the alias listed on their profile located on the NSPlayer site. Any player found to be using a different alias in game will not be permitted to play the match.

3.10 Scheduling

Game times are displayed on the NSPlayer website. Teams may reschedule games by contacting the other team and first working out a suitable time for both teams, it is asked teams be reasonable about scheduling new times. Once a new time is agreed upon both team's leaders must inform an admin so the change can be verified and made on the NSPlayer website. Rescheduling should occur as soon as possible in a week, no sympathy will be shown to teams who have left it too late to be able to work something out with thier opposition.

If the match was rescheduled and a team fails to attend then the situation must be reported to an NSPlayer admin immediately. Any dispute regarding match fixtures should be brought up with an NSPlayer admin.

3.20 Server Details

Server details including password can be acquired half an hour before the scheduled start time from an NSPlayer admin. Team captains should idle in the official channel #NSPlayer on GameSurge.

3.30 Player Numbers

Unless otherwise stated, standard Natural Selection matches will be played with up to 6 players on each side. Teams will have 15 minutes to get a minimum of 5 players into the server, afterwhich the game must commence. If a team fails to find 5 players then they forfeit the match. The 6th player is permitted to join once the game has started.

3.40 Pre-match

Teams have fifteen minutes after the agreed upon match time to join the server. Both teams must have the minimum number of five (5) players in the server before the half begins. The game will start when both teams are ready or after 15 minutes has elapsed.

3.50 Player Drops

NSPlayer is not responsible for players who experience connectivity problems. Teams should have back-up players ready to join if a player gets disconnected or lags out. Voice communication software is extremely helpful in such situations. Pausing the server is not permitted once the match has started for any reason.

3.60 Half-Time

After the first half has been completed, teams are allowed an optional ten minute break. Consequent rounds will begin when both teams are again ready.

3.70 Win Conditions

Victory, unless otherwise stated in the tournament information for a standard Natural Selection round will be as per the default winning scenario made by the game. That is, killing (or devouring) all opposing players and destroying all completely built structures that can respawn players (infantry portals or hives) in classic Natural Selection.

3.80 Tiebreaker

Information regarding procedure in the event of a tie can be found with the tournament information. Generally a 1-1 tie during the main two rounds will result in a third round being played to determine the winner. The team which one their round in the fastest time will choose what side they wish to play as for the tiebreaker.

3.90 Post Game

After completion of the match, the scores and standings will be updated by an NSPlayer admin. If an admin or representative was not present during the game both captains should report the score to an NSPlayer admin. Results of victories or losses, or any points systems will be explained in the tournament information.

3.100 Voice Communication

Use of communication programs such as Roger Wilco, Team Speak, Battlecom, or Ventrilo are completely acceptable. No non-NSPlayer officials or representatives will be spectating. HLTV if available is delayed.

3.110 Substitutions

As in all sports, substitutes are allowed and may be made at any time during the match. In the case of a substitution, the player that is being subbed out must leave the side to the ready room before the player being subbed in joins the team. This prevents unbalanced teams during a substitution. Use of voice communication is recommended for timing substitutions correctly.

3.120 Map

The map played will be pre-decided and included in the game information on the NSPlayer website. Except in special cases, all rounds for a match will be played upon the same map. Recommendations or issues about a map should be communicated to an NSPlayer admin.

4.10 Roster Changes

During a league clans may only take on new players which were not in (haven't played a game for) another clan still playing in the league untill week 6, after which rosters will be locked. There may however be special circumstances in which admins approve, in any case though the council of an NSP admin should be made whenever roster changes are considered. In any circumstances however a player can not play for two different teams in the same league round, doing so will see that player supsended from the league. For tournaments, finals and when rosters are locked (after week 6), clans may not take any new players at all.

4.20 Team Inactivity

Repeated failure to attend matches with the correct number of players may see the team removed from the tournament and possibly refused entry to subsequent events.

4.30 Unacceptable Names

Team and player names including but not limited to the following will not be tolerated: profanity, hateful to any race, sex, or religious group, condones drug use, or general vulgarity. Teams or players found to have an offensive name will be neglected participation in any NSPlayer item.

4.40 Team Positions

All teams are required to list at least one leader who will administer the clan and act as a captain. No one individual owns a team, the controlling power can be replaced when the majority of a team makes such a request, the specifics of this request must be sent to an NSPlayer admin, they will be reviewed on a case by case basis. A team’s standings and tournament participation is non-transferable.

5.10 Anti-Cheat

Cheating Death is optional for all matches.

5.20 Server Usage

NSPlayer will do its best to supply or organize a server for each match. Only approved server will be allowed for NSPlayer games. Details regarding server information can be collected from an NSPlayer admin thirty minutes before the match.

General Server Requirements:
· Current version of Natural Selection.
· Using correct map version as designated.
· Must have server variables set to the NSPlayer configuration.
· Dedicated servers are mandatory.
· Must be hosted off a T1 Line or greater.
· Cable modem or listen servers are not permitted.
· Must be located in Australia (If an agreement is reached between both teams to play on a foreign server, an exception can be made).
· Servers should have logging enabled.

5.30 Server Configuration

The server configuration is subject to change as the NSPlayer admins see fit. Any changes to server settings during a match are punishable under the cheating guidelines.

5.31 Tournament Mode: mp_tournamentmode 1

Standard for any competitive game, players will join their teams before game start. The ready command by both teams will then cause the round to begin.

5.32 Friendly Fire: mp_friendlyfire 1

Friendly fire will be enabled at default levels.

5.33 Time Limit: mp_timelimit 0

Unless otherwise previously stated, NSPlayer games will not have a time limit. A round will continue until a team comes out victorious.

5.34 Consistency: mp_consistency 1

As previously stated in 2.10 all players must use default models and files. To enforce this, servers will check for consistency.

5.35 Scripts: mp_blockscripts 1

Following suit with other Australian servers, scripting is currently blocked in all NSPlayer tournaments. This rule may be susceptible to future changes however.

5.36 Late Joins: mp_latejointime 0

Players joining after play has begun will miss out on starting alien resources.

5.40 Ping Imbalance/Server Playability

NSPlayer will do everything in it’s power to give low pings to both sides, this however may not be possible if either team does not reside in Australia. An NSPlayer admin will decide what is unplayable if such a situation arises and take necessary action, generally however a ping difference of up to 100ms is acceptable.

5.50 Server Crashes

If a server crashes before a 10 minute period has been completed, the server will be reset and the round restarted. If a crash happens after the 10 minute period and both teams agree there was a forseen winner, a victory will be given to one of the two teams. Any disputes or agreement clashes will result in the entire round being replayed at an NSPlayer admins discretion.

5.60 HLTV

HLTV will be supplied by NSPlayer whenever possible. The ip to which will be made available on the website and on irc for those wishing to spectate.

5.70 Third Party Software

All Third Party Server Programs (TPSP) are not allowed in NSPlayer. If you use a TPSP to join or admin a server, or check clients, you are required to disable it for the duration of the match.

6.10 Multiple Accounts

Players are prohibited from having more than one account on NSPlayer. Players using more than one account will be suspended with further disciplinary action possible if both were used in matches. To the same extent, a Steam-ID can only be used for a single player and account.

6.20 Multi-Clanning

Multi-Clanning is defined as either playing for or being listed on the roster of more than one team competiting in a particular NSPlayer event. Such action is strictly prohibited, Punishment will involve immediate suspension for as long as the admin sees fit.

6.30 Ringing

The definition of ringing is allowing a player to play for a team when that player is not on the team's roster. This individual could be playing as himself or under an alias. Ringing will not be tolerated in any NSPlayer tournament or event. Players ringing and teams using ringers can expect to be suspended and removed from tournaments.

6.40 Cheating

Anyone who has been caught cheating at any time, whether it be in pubs, LANs, scrims, matches or anything else may be excluded from any NSPlayer event. Please be advised as to what evidence is permissible by NSPlayer. NSPlayer admins will review cases and players may be suspended indefinitely. If a player is caught cheating in an NSPlayer match, their team shall forfeit the game, and the team will be unable to participate in NSPlayer tournaments until that member has been removed from the team. Any matches played with that player up to that point should have the losses overturned. If a member is caught cheating outside of an NSPlayer match, the suspension shall be enforced on the player with no matches overturned. The computer system that you play from is your responsibility. If you allow others to use your computer(s) or you borrow/rent systems to play from, you need to ensure that they are cheat free prior to playing. It is impossible to trust a player who has been caught cheating on a pub to withstand the temptation to cheat when a title or prize is up for grabs.

6.50 Exploits

Natural Selection is a mod under constant development. Any team taking advantage of any exploits, whether new or unknown, will result in the forfeit of that match. NSPlayer will have the final decision on whether something is an exploit.

Although the following may not be actual exploits, they have been deemed exploitive and are illegal in NSPlayer matches:
· Intentionally building structures that do not exist entirely inside the world (sinking chambers and building ‘outside’).
· Building through thin textures.
· Blocking phase gates or infantry portals.
· Blocking a resource point with a structure other than a resource tower.
· Blocking an elevator with a structure or player.
· Blocking a passage with structures to the point where a skulk cannot pass through (excludes vents).
· Attacking through thin textures (bile bombing or acid rocket).
· Sitting below the ip spawn height and biting upwards, still getting the ip hit box.
· Having more than 1 extra player in the ready room. The allowable extra must remain in the ready room at all times. Failure to do so can result in the forfeiture of the round.
· Bypassing built in game timings (old flashlight exploits).
· Any action that bypasses a game design decision.

6.51 Structure Blocking

The ability for the commander to instantly drop buildings anywhere on the map can be exploitive. Whilst marine structures may be used in preparation to restrict alien entry, they may not be intentionally dropped as an unbuilt building near a retreating alien to block their exit.

6.52 Common Sense Clause

If you have a question towards the legality of a possible exploit please speak to an admin as soon as possible to avoid being hit with infractions in the future. If a person is found to have used an exploit that gained them a large advantage they will not be able to hide behind “It wasn't stated as being an exploit in the rules”, “I didn't know” or “other players are doing it”. Spending hours upon hours searching for the next undocumented exploit that will gain you or your team an advantage in a match will no longer be a viable option. Players and teams will be held responsible for your actions when the exploit is found and a ruling is made on it. Punishment could vary and is completely at the admins discretion.

6.60 Disputes

Disputes are a serious issue and will not be taken lightly. Only team leaders or captains may lodge an official dispute and contact NSPlayer admins, any other player’s presence will be asked of if needed. Lodging a dispute should be done through IRC or email and explained in detail. Any evidence and information should be turned over immediately to allow the NSPlayer admins to investigate the issue. Once a case has been filed it may not be brought up again except by an admin’s discretion.Some disputes regarding player names, Ids and server issues must be taken up immediately before the round has started. Action against such disputes can not be done once the game has taken place. If a team continues to make false claims against other teams, the disruption may be viewed as grounds for team suspension. Teams crying wolf regarding cheating repetitively will also be purged.

If teams are caught saying that they are relying on disputes to win their matches, teams may be suspended, removed or have disputes invalidated. For example, if during the course of reviewing demos, a team member says not to worry if they lose and to appeal after to win.

6.70 Appeals

If a judgment and punishment has been levied against a team or player as the result of a dispute, that team has the right to appeal the judgment, the punishment, or both. When filing an appeal, an NSPlayer admin must be notified within 24 hours. At the time of the filing, the team filing the appeal must submit a written statement as to why they are appealing the judgment. In addition, any new or additional evidence they wish to submit for their defence must be given at this time. Admins will not pro-actively gather evidence during this process. During this process a team is given a full twenty-four (24) hours to file the appeal. It is recommended that you use this full twenty-four (24) hours wisely if you intend to appeal. Use it to be certain you have gathered all the evidence you wish to submit in your defence. The written statement should be clear, concise, and contain a well thought out argument as to why you feel the decision was reached in error. Evidence will not be accepted after the appeal has been officially filed.

6.80 Rule Violations

A team who violates any rule may be subject to disciplinary action(s). This includes the specific penalties or suspensions, forfeits, replays, expulsion, or loss of points in standings. NSPlayer may change the penalties as it sees fit.

Disruptive teams will be purged from NSPlayer events. Any team that is repeatedly disruptive in the form of unacceptable language, pointless spamming, server crashing, etc. will be removed.

8.10 Version

Final 1.63 - 24/04/06

8.20 Compilation

Compiled by N3

8.30 Acknowledgements

8.31 Unknown Worlds, Natural Selection Development Team

Makers of the Half-life modification: Natural Selection.
(http://www.naturalselection.com)

8.32 Cyberathlete Amateur League

The basis from which this rule set was formed.
(http://www.caleauge.com)