Star Trek Legacy Competition Ladder League and On-line RPG Campaign

Star Trek Legacy Rules Submenu
		Select a section of the rules you wish to go to. Please read these rules before you play on Star Trek Legacy.

1.1 Fleet Requirements

Fleet Requirements/Specifications

Each Fleet in Star Trek Legacy League must have at least 1 valid leader and 2 valid players for a total of 3 valid/active players and not more then 25 active players per Fleet. All members must have a valid email address and a valid callsign. Any locked players while locked do not include in active head count in Fleet. If Fleet falls under 3 active members for more then 2 weeks the Fleet will be then deleted.

1.2 Fleet Structure

Fleet Structure

A Fleet Structure must be Maintained at all times! Please follow the outline of the proper format for your Fleet Structure:

One Rank 10
One Rank 9
Three Rank 8
Three Rank 7's
Rank 6 thru 1 any ammount

With this structure it will always give 51 percent control of Fleet to Unit Leaders.
Please do not give control of Fleet fuctions to anybody you don't know.

Fleet Limit

All fleets will be limited to 25 members per roster, this is to give all fleets a shot at 1st place in a cycle, and make more Fleets (more people to match)there are and will be no exceptions to this rule.

Fleet Allies

All Fleets will be allowed 5 Allies. Allies can play Multi-Fleet Battles with your Fleet. Unless your are listed in Allies section of the Fleet page you can not do Multi-Fleet Battles with that Fleet.

1.3 Match Types

Single Battles (1 vs 1 Merc)

Waiting for Game (Rule in consideration)

2 Fleet Battles (1 vs 1)

If more than one member in your Fleet is going to participate in a match, this is known as a Fleet Battle. Both Fleets must have the same amount of players. ie. If Fleet A has 3 players wanting to play in a match, then Fleet B must find 3 players from thier own Fleet to participate. However, if a Fleet wanted to player under-manned (less players), then this is acceptable and is encouraged by STL.

Multi Fleet Battles (2v2, 3v3... 8v8)

Waiting for Game (Rule in consideration).

Free For All

This type of battle is for players who wants a bigger match then a singles match, but dont have a buddy. 3 players are minimum to play this type. There may not be two (2) players from same Fleet. All must agree upon used kit and weapons before launch. Also all must agree upon what map is going to be used. Only one map is used. Timer is set to 3 minits. And the player first to reach 15 kills win. If two players have same amount of kills. They will have to fight it out 1v1. If the duel comes out with no winners, they will redo it. All matches reported with more the 16 kills will automaticly be voided.

Ransom Matches

Ransom matches, is when a wager of points is bet on the match. You can ransom all your Personal and/or Fleet points in this wager. If you do not have enough points to Ranson you will show negative for your personal and/or Fleet Points.

1.4 Game Rules

Callsigns / GSA names

Callsigns, GSA names, and game names will match. Example if your callsign is SmackTard, than your GSA name and the name that you use while playing on the Star Trek Legacy Ladder should match. Also your GSA and Star Trek Legacy E-mail addresses should match this is to help you and to make this easier for Admins to do their job if at anytime you need help with your callsign, Battles, Fleet problems and so on this is to help us Identify you. Your GSA account MUST have email info in it

Screenshots from GSA

All screenshots from GSA must have playerinfo with email in it. Otherwiser we wont accept them

Symbols in callsigns

We do not allow any symbols in callsigns if we see / \ { } ) ( * & ^ $ # @ !" : ;< >=+ in any callsign we will edit the your callsign you will have one(1)and only one warning all callsigns will be as follows [Fleet]callsign.there will be no exceptions to this rule.

Pre-Match

While in search of a match, whether it be on GameSpy or any gaming platform. if you insist on making a room to wait for a challenger, it is suggested to make the room name begin with the Star Trek Legacy prefix (STL), for example "STL (Fleet Prefix) v ???/(Fleet Prefix)". This is to ensure of no confusion as to whom you are playing or to simply state the fact that you are awaiting a challenge. You may also add the size of the match you are looking for (1v1, 2v2.. 8v8) to avoid unwanted challenges. The minimum size is a 1v1, with the maximum size being a 8v8.

If challenged, you do have a choice to whether or not you wish to accept. You do not have to accept the challenge, do not feel pressured or intimidated by the challenger.

Once a challenge has been accepted, and once the size of the match has been agreed upon by both teams, you can decide what match type to play (see details below (Match Types)).

A host must then be decided. The team who was challenged (either hosting the room or was challenged through other means) have the chance to host first. If the host's connection is unsatisfactory, where agreed upon in the lag test, the challenging Fleet will then have thier chance to host.
all games are a standard 3/5 3/5 series of maps

Crashes/Drops (Players)

If a player drops whilst the game is in progress, and at least 1 minute has gone, the team who lost the player will have to continue under-manned. If a player drops within one (1) minute of when the game started, the team who lost the player have the opportunity to call for an abort (using the global chat), making sure that the host can see it (It is the hosts job to make sure the game gets aborted) or they may wish to continue under-manned. If, however, a player has been killed, on either team, the game must continue, no exception. If a player disconnects whilst the game is loading, the host must abort straight away if the dropped player's team call for an abort. The dropped player then has five (5) minutes to return. If a player drops during the weapon selection screen, the host must abort the countdown, if necessary, and players may sit and chat amongst each other while the dropped player reurns. The disconnected player has approximately 5 minutes in which to return. If, after 5 minutes, the disconnected player has not reurned, a substitute may be found. Further details about substitutes can be found below. If a player drops three (3) times whilst the game is in progress, he/she must be subsituted, if no substitute can be found, the team or Fleet must continue under-manned. There is no limit on how many times a player may drop in the weapon selection screen.

Crashes/Drops (Host)

If the host disconnects whilst the game is in progress for the first time, the game must be continued with the same host. The match must be continued from when the host crashes, using the correct map, time limit, format and insertions points and the host must tk him/herself. If the host crashes three (3) times, the non-hosting team or Fleet may have the opportunity to host. If the non-hosting Fleet can not produce a host, a neutral host may be brought it (The team or Fleet has approximately 5 mines to find a neutral host). If a neutral host can not be found, the original host must be used, despite whether he/she crashes a lot.

Crashes in Singles

If a player disconnects during a 1v1 or singles match, he/she has ten (10) minuts to return, otherwise the other participant may fill out a forfeit form on the STL ladder. The same rules apply for the host as above. No substitutes can be used in singles matches.The dropped player is considered KIA (Killed In Action) and kill count.

Substitutes

Substitutes must be from the same Fleet. A maximum of two (2) substitutes may be used in any one match (except for single's match's, where no substitutes can be used). The substitute may inherit the amount of kills the disconnected player had, if he/she wishes.

Redo's

If all player's are killed in any one round, a redo must be played. The score will remain and player's must not add thier kills for that round.

If a player is not greened up and the host launches the game, a redo will automatically be enforced unless agreed upon by both sides. (with exception to the fact that if the person not greened up has been gone more than 2 minutes)

Screenshots

STL recommends that player's take screenshots at important events, such as results screens, suspicions of glitching/cheating or of profane or foul language. This is hard evidence and will help in any investigations STL may have to carry out. Please take a screenshot of the final results screen. If a player does not confirm a match, this screenshot is proof that the match existed and was completed. Screenshot of finalscore must be saved for 3 days.

1.5 Post-Matches

Reporting/Confirming

The winner of the match must report the match by filling in the correct details on the Legacy League site. The loser then has to confirm the match. It is recommended that the winner informs the confirmand of the battle number to avoid any confusion. The losing player or unit has one (1) hour to confirm the match. If after an hour the match has not been confirmed, the winning player or unit may approach an administator with evidence of the match. Star Trek Legacy League will not tolerate unconfirmed matches. The winning player or unit will then have the option to enforce a penalty to the losing player or unit. If a player fills out the report form incorrectly, but is unaware of it, the losing player or unit should inform the reporter of his/her mistakes, then it may be re-reported.All battles must be reported right as soon as they have ended. Waiting to report a match and just play a rematch and maby more, then report them all. Could give admins the impretion that something is fishy. Battles reported in a row can be voided by admins without evidence that the game took place.Therefor match then report. And then continue matching

Reporting a Forfiet

A forfiet is a game that never ended. If you play a 1v1 and the other player disconnect, and is not back in 10 mins. A forfiet is reported. Forfeits are reported as if all players were actually in the game but losing teams kills are set to zero and the winning team reports their kills as normal.in a forfiet you must have a ss and report this to a Star Trek Legacy League admin if a admin is not on E-Mail all ss's and tell the Admin why this was a forfiet.

Reporting Substitutes

The player who has substituted, has the choice whether he/she wishes to be included in the final match report, whether win or loss. If the substitute chooses to be excluded from the final report, the dropped player must be reported with all the kills that he/she got, plus all the kills that the substitute got, if any. Star Trek Legacy League recommends that the substitute should be informed of the match situation before he/she participates.

Sportsmanship And General Behavior And Profanity

Star Trek Legacy League enforces fair play for everyone and wouldn't want anyone to suffer from unacceptable behavior from other Star Trek Legacy League members. Any forms of profanity, bad language or racism or Any accusations made towards any Star Trek Legacy League member, without hard evidence, will not be tolerated . Anyone found doing this with in Star Trek Legacy League matches, on the Star Trek Legacy League site or forums or any gaming platform Star Trek Legacy League matches are played on will be dealt with severley.As part of our fair play scheme, players should acknowledge fair play and always abide by the rules. Everyone has more fun when players are good sportsman. Complaining and whining is a sign of bad sportsmanship and just creates a negative atmosphere, which is what we do not want on the Star Trek Legacy League network.See Profane Language for Penalities.

1.6 Breaching of Rules

Moderations

Star Trek Legacy League does support some mods . Any external mods other then the mods on our list must not be used in Star Trek Legacy League competition. Anyone found using any other mods of any sort will be punished accordingly.

Glitching

Glitching is a form of cheating, it is a way to gain an unfair advanatage and Star Trek Legacy League will not tolerate it. Anyone found glitching will be punished accordingly. If, however, a player glitches due to misfortune, ie. warped or fell into a glitch, it is up to the other player's in the match to recognise this and redo that game.

False Reporting

Reporting battles that didn't take place is another form of cheating. If found reporting false battles, a punishment will be forced upon. Adding extra kills whilst in game or in the report is classified as false reporting and the same punishment will apply.

Multiple Callsigns

As a Star Trek Legacy League member you are entitled to one (1) and only one callsign. We understand that you may have other members in the househould that play as well, but these members must be on same unit. Failure to comply with the above will result in all callsigns involved being locked.

Imitation of Star Trek Legacy League Members

Imitating another member of Star Trek Legacy League or a Star Trek Legacy League admin is an offense and a punishment will be enforsed if a player is found doing so.

Confirmation of Battles

If after an hour of when the match was reported, the match still isn't confirmed, an admin may be approached and a punishment will be applied by choice.

If you have a comment or a suggestion about these rules, please send an e-mail to us with your feedback. Thank you for participating in Star Trek Legacy League!

1.7 Penalities

1. Accusations of Cheating

Any accusation of cheating on a member of Star Trek Legacy League without proof of cheating will be enforced with a 48 hour lock, and will be fined 1000 personal points. Multiple offenses will have increase the period of the lock and fine, and could result in a permanent lock. This is based on the discretion of a Star Trek Legacy League Genre Admin.

2. Glitching/Cheating

Glitching and Cheating is frowned upon within Star Trek Legacy League. If there is proof of either or in a Star Trek Legacy League match, the player�s callsign/IP will be banned for life.

If upon launch you insert into a glitch, it is your duty to ask for an abort. If you do not ask for the abort, and continue play, this will be considered cheating as well.

3. Owning 2 or more callsigns and reporting against them

Star Trek Legacy League will only acknowledge the use of one callsign per player. If a player has multiple callsigns, and starts to report false battles against each them, then both callsigns will be banned as will the IP of the callsigns.

4. Profane Language:

We must all be aware that not everyone playing this game is old. Obsessive use of profane language/cussing after being asked to stop by any member in the room can lead to a 72 hour lock and a 2000 point fine to the player or players caught doing so, along with a 5000 point deduction to the unit the offender(s) belong to. To be released from the lock a written apology must be written to the clan you were competing against.
all apologies must be posted on the BO public forum. http://www.wgleague.com/forum/
Screenshots must be provided from the clan with the complaint. The screenshots must include them asking the clan to watch their language, and screenshots of when the clan failed to do so.

5. Imitation

Imitating administration from Star Trek Legacy League is not looked upon lightly. If you are caught doing so, a permanent lock can be enforced.

6. Admin Abuse:

Administration abuse is something that all leagues must deal with. However, Star Trek Legacy League will not tolerate excessive abuse of its staff. All administrative abuse reports will be handled by the lead of that league. Screenshots of the abuse must be available for both the player and the lead. After fully reviewing the case, the lead will determine the duration of the penalty.

7. Confirming Battles:

Star Trek Legacy League will use a progressive system towards punishment of non-confirmers. The system is as follows:

First non-confirmation violations will be warned via a written warning, by email or chat.
Second offenses are warned again, however this time a fine may be imposed. (Fines are determined by each individual league).
Third time offenders are dealt with strictly. A mandatory fine is imposed, aswell as a lock with a duration of no longer than 3 days, which may be imposed aswell.
Fourth time offenders are mandatorly locked fined. Locks will last the extent of 7 days.

All lifetime locks will have the IP of the callsign banned aswell.
All additional penalties and fines defined on a per league basis.

1.8 Mod Testing

Mod Testing

Rule in Consideration