I think we need a player ranking system, so that players can be matched with other players of the same skill level. But what could be used to determine the skill level of the players?

That would fit in with JPs Player Alias Validation thingy (ie a player registers here on classictw and joins a game on a server with jumpgate active, and your server verifies them with classictw)

H

Yes, A player would need a global profile like you are talking about.
Pogo Risk tracks how many games a player has won, placed second, etc... but we don't really have that metric in TradeWars.

Wouldn't this require using the same name over and over again? I tend to get destroyed when I use a certain name(s)

hmm.. I hardly ever use Muss as a game name anymore.

and how would you rank 1st.. or 2nd?

exp and align really don't count as anything.

I can't imagine why, do you play differently based on the name you use? lol

Do your alternate personalies know about each other?

LOL! Depends on the day

You're so vain, I bet you though that pose was about you .... lol

Hey, does anyone know how the ratings system worked on www.twleague.com back in 2005?

http://web.archive.org/web/200306030242 ... eague.com/

Found it - I love the wayback machine!

There are two parts, one for ranking players and one for ranking sysops. The Reverend is still around, he was on the board then.

http://web.archive.org/web/200306082101 ... prules.asp

LEAGUE PLAYER RULES
Return To League Homepage


The following are rules that all league players are expected to adhere to. Punishment for violation of these rules will be determined by the league board and become effective. You have the right to dispute the board's decision and present any evidence that you have concerning the matter. A final decision will follow from the board.



A. Terminology

GAME = a sanctioned league game
SYSOP = gameop, sysop, co-sysop, etc. managing the GAME
SERVER = TWGS server hosting the GAME
PLAYER = a single player account registered in the GAME
LEAGUE = the league governing body
B. Accounts

There shall be no duplicate accounts. This rule shall be enforced by the SYSOP. If a PLAYER legitimately shares a location with another PLAYER, both PLAYERS must demonstrate that legitimacy to the satisfaction of the SYSOP prior to the GAME start.


The LEAGUE board members shall not play a GAME where another LEAGUE board member is acting as SYSOP.
C. Conduct

There shall be no bug use. PLAYERS are prohibited from using flaws in TWGS.

There shall be no team backstabbing. PLAYERS shall only join corporations consisting of their own teammates. PLAYERS shall act in the best interest of their team for the duration of the game. PLAYERS shall only login to their own account.


Each PLAYER shall be part of their team corporation after day 7 or otherwise notify the SYSOP of his/her team affiliation prior to day 7. Once the SYSOP registers each team with the LEAGUE on day 8, team rosters shall be final.
D. Language

PLAYERS shall respect the requests of other PLAYERS to refrain from offensive language regarding race, sex, or religion. SYSOPS shall err on the side of the offended PLAYERS if the problem persists.


There shall be no spamming. Spamming is any communication designed to overwhelm another PLAYER with irrelevant information. For example: attacking figs one at a time is relevant; hailing War and Peace is irrelevant; checking terra more than 20 times per second is irrelevant; attacking sector/planet fighters for 0 repeatedly is irrelevant. Any irrelevant messaging above 1200 characters per minute shall automatically be deemed spam. Irrelevant messaging below 1200 characters per minute shall be deemed spam at the discretion of the SYSOP.
E. Conclusion

Rule violations will be diciplined as outlined in the SYSOP rules. PLAYERS may report GAME irregularities and or possible PLAYER cheating to the SYSOP or LEAGUE for appropriate action. If a PLAYER suspects cheating, un-edited GAME logs must be provided as evidence or no action will be taken.


PLAYERS shall observe the rules of the SERVER and GAME as defined by the SYSOP in addition to the version of the LEAGUE rules which were in effect at the announcement of the GAME. PLAYERS shall be aware that the SYSOP may add to or strengthen any of these rules as a part of the GAME rules. For example, the SYSOP may have GAME rules limiting mega-corping and/or information sharing. The LEAGUE has no jurisdiction over the satisfaction of GAME rules that extend beyond the LEAGUE rules - the decision of the SYSOP shall not be overruled by the LEAGUE in those matters.

Rules Version: 2.0 - Date: 7/15/2002



--------------------------------------------------------------------------------

LEAGUE SYSOP/SERVER/ADMIN RULES
Return To League Homepage


The following are rules that all league sysops/admins are expected to adhere to. Punishment for violation of these rules will be determined by the league board and become effective. You have the right to dispute the board's decision and present any evidence that you have concerning the matter. A final decision will follow from the board.



A. Terminology

GAME = a sanctioned league game
SYSOP = gameop, sysop, co-sysop, etc. managing the GAME
SERVER = TWGS server hosting the GAME
PLAYER = a single player account registered in the GAME
LEAGUE = the league governing body
B. Advertizing a GAME

The GAME shall be advertized in the appropriate public forums at least one week and no more than six weeks in advance of the start time. Such advertizement shall include the start time and date, the SERVER address, the GAME letter, the TWGS version, and the version number of these rules being enforced. The GAME shall be subject to the most recent rules as posted by the LEAGUE at the time of the GAME announcement until the GAME completion. The SYSOP may also include any GAME rules that apply and even strengthen some or all of the LEAGUE player rules.


The SYSOP shall specify the victory conditions in detail. Victory conditions shall be objective and not subjective. Victory may not be shared by more than one team.
C. Hosting a GAME

The SYSOP may not play a GAME on his/her own SERVER. The SYSOP may have an observer account for the GAME on his/her SERVER. The LEAGUE may also request an observer account provided that the LEAGUE observer is not also a PLAYER in the GAME. No other person may have an observer account for the GAME. The SYSOP shall not provide sector or port information to any PLAYER. Furthermore, the SYSOP shall not provide any other GAME information to a PLAYER except what was provided in the advertizement. The SYSOP may reset lost ship and account passwords for PLAYERS who request such help.

The GAME shall start within an hour of the advertized start time. If the start is delayed more than an hour, the GAME shall be delayed a full 24 hours from the original start time.


The GAME shall be closed to new PLAYERS after 7 days, i.e. 168 hours after the start time. The GAME shall remain closed for its duration. The SYSOP shall submit the team rosters to the LEAGUE within 48 hours of closing the game to new PLAYERS. (This part will apply only if the new ratings system is voted in by the players at the end of the year.) Such submission shall include a list of all PLAYERS. The SYSOP shall take measures to ensure that no PLAYER is deleted before he/she submits the team rosters. If the GAME has less PLAYERS than twice the max corp size (MCS) then it shall be de-sanctioned. (This part will apply only if the new ratings system is voted in by the players at the end of the year.)


The SYSOP shall take measures to prevent duplicate IPs from participating in the GAME. PLAYERS suspected of playing duplicate accounts shall have their password changed until the situation can be reviewed. The SYSOP shall resolve such situations in a timely manner.


The SYSOP shall take reasonable measures to ensure that the SERVER is available for the duration of the game. Extended SERVER outages (more than 3 hours) should be announced in public forums if possible. A GAME re-start after an extended outage should be announced at least 12 hours in advance. A PLAYER may be disconnected by the SYSOP upon their explicit request. The SYSOP shall inform the LEAGUE of significant problems with the GAME or with the SERVER.


The SYSOP may host up to two GAMEs simultaneously on a single SERVER, but is only allowed to host a TOTAL of two league games a year currently. (From 1/1 to 12/31).
D. Completing a GAME

Upon satisfaction of the victory conditions, the SYSOP shall close the GAME and submit the GAME results and scores to the LEAGUE within 48 hours. The SYSOP shall be responsible for the accuracy of the GAME results he/she submits. Such results submission shall include the status of each PLAYER whether alive, dead, or deleted, what team they were part of, which PLAYERS are winners and/or runners up, and any rule infractions they committed. In addition, the SYSOP shall submit the max corp size (MCS) and the winning corp size (WCS). The winning corp size is the total number of players on the winning team including non-league players. (This part will apply only if the new ratings system is voted in by the players at the end of the year.)
E. Discipline

The SYSOP shall report PLAYER rule violations to the LEAGUE. PLAYERS may also report GAME irregularities to the LEAGUE. In order to investigate alleged problems, the LEAGUE shall be given administrative access to the SERVER upon request and in a timely manner.


The following disciplinary actions may be taken by the SYSOP or by the LEAGUE:
A - PLAYER password change and IP boot
B - PLAYER turns penalty
C - PLAYER login penalty
D - PLAYER deletion


Type A discipline occurs when the SYSOP or LEAGUE suspects a PLAYER of rule violation, and may be reversed if the evidence fails to convict the PLAYER. Type A discipline will always progress to Type B-D discipline if the evidence convicts the PLAYER. SYSOPS should be aware that Type A discipline can cause harm to the PLAYER and result in their death under certain circumstances; SYSOPS should take measures to prevent this from happening until the case is resolved. Type B discipline is a reduction of PLAYER turns, e.g. 100 turns may be appropriate for spamming. Type C discipline can block a PLAYER from logging in for a number of days, e.g. 2 days may be appropriate for bug use. Type D discipline is PLAYER deletion and loss of the game for that PLAYER. If such a PLAYER was part of the winning team, that team's size will not be reduced for points calculations.


The following disciplinary actions may be taken by the LEAGUE:
E - PLAYER suspension


Type E discipline may be utilized by the LEAGUE. Each suspension will be evaluated on a case-by-case basis. No PLAYER will ever be removed from the LEAGUE, but an indefinite suspension is possible. Suspended PLAYERS will not be shown in the ratings, but their rating will still be stored and used again when their suspension ends. Suspended PLAYERS may complete any GAME other that they are currently playing in good standing.

Rules Version: 2.0 - Date: 7/15/2002

Those are the Rules, not the ranking system. I didn't see the ranking system anywhere on the site in the wayback machine. They used some kind of points system, but it was not based strictly on wins/losses.

If we the players could figure out some sort of points system, perhaps JP can program it into the code to figure points based on player/corp/game for V3. At that point at the end of the game we could simply export the points to a database and update totals? Or even have it done through jumpgate.

T0yman has a script he uses to score the players in his builders games.

That might be fine for the lower ranking players...but there would have to a different point system for each skill level... because the ELITE players arent going to be building planets... you might have to include kills, grid, etc... might take some work ...but might be interesting...