Server Rules

1. All listed servers must be relevant to the RuneScape Classic community.
2. Server owners must provide accurate server names, descriptions, website links, and other requested information.
3. You may only submit or manage a server you own or have permission to represent.
4. Duplicate listings for the same server are prohibited unless approved by site administration.
5. Server owners are responsible for keeping their listing information up to date.
6. Administrators may reject listings containing misleading information or violating these rules.

1. Server owners must make a reasonable effort to provide accurate player counts.
2. Artificially inflating player counts to improve leaderboard rankings is prohibited.
3. Fabricated statistics and deliberate manipulation of reported counts are not permitted.
4. Registered accounts and historical logins must not be misrepresented as currently connected players.
5. Administrators may investigate suspicious counts and request clarification from server owners.
6. A suspicious count may be marked for review while the issue is investigated.

1. Server owners should distinguish bots and automated clients from genuine human players when reporting statistics.
2. Bots must not be deliberately represented as real human players to mislead visitors or manipulate rankings.
3. RSC Server List plans to introduce a standardized system for reporting human players and bots separately.
4. Until that system is available, owners are expected to report their statistics honestly.
5. Further technical requirements will be published when the new system is ready.

The Player Count API has not been implemented yet. Integration is not currently mandatory.

1. RSC Server List plans to introduce a standardized Player Count API to improve the accuracy and reliability of server statistics.
2. Once introduced, the API will have published technical specifications explaining how servers must report their statistics.
3. The planned format may include real_players, bots, players_online, and a timestamp.
4. Server owners will receive documentation explaining how to implement and test the API.
5. A reasonable transition period will be announced before compliance becomes mandatory.
6. Existing servers will not be penalized for failing to implement an API before the official requirement takes effect.
7. After the announced deadline, noncompliant servers may lose leaderboard eligibility or be removed from the listing.

1. RSC Server List may automatically retrieve publicly available server statistics to display player counts and listing information.
2. Server owners must not deliberately provide misleading data to manipulate statistics.
3. Missing, outdated, inconsistent, or suspicious information may be flagged for review.
4. Temporary network problems and server outages will not automatically be treated as deliberate misconduct.
5. The site may update its scraping and verification methods to improve reliability and accuracy.
6. Future API requirements may supplement or replace existing methods of collecting player statistics.
7. New mandatory technical requirements will be announced before enforcement begins.

1. Votes must represent genuine community support.
2. Automated voting, fake accounts, and vote manipulation are prohibited.
3. Server owners must not exploit site features to gain an unfair ranking advantage.
4. Administrators may investigate suspicious voting activity and remove fraudulent votes.
5. Paid promotions, if offered, must not be misrepresented as organic popularity.

1. Attempts to disrupt, exploit, or compromise RSC Server List are prohibited.
2. Intentionally overloading the website or interfering with its data collection systems is prohibited.
3. Malicious links, deceptive redirects, and harmful content may result in listing rejection or removal.
4. Attempts to bypass site restrictions or manipulate the listing system may result in administrative action.

1. Depending on the severity of a violation, administrators may issue warnings, request corrections, restrict rankings, suspend listings, or remove servers.
2. Whenever practical, owners will have an opportunity to correct ordinary problems before removal.
3. Serious intentional fraud, security abuse, or repeated manipulation may result in immediate action.
4. Temporary outages alone will not automatically result in permanent removal.
5. Failure to implement the future API will only become grounds for enforcement after the requirements and deadline have been announced.
6. Owners may contact site administration to appeal an incorrect decision.

1. Rules should be applied consistently to all listed servers.
2. Administrators may request additional information when ownership or reported statistics cannot be verified.
3. Material policy changes will be announced before enforcement where practical.
4. New requirements will not be applied retroactively to penalize conduct that complied with the rules at the time.

1. RSC Server List may revise these rules as the website develops.
2. Additional technical requirements may be introduced to improve accuracy, reliability, and security.
3. Server owners are responsible for reviewing published updates.
4. By submitting or managing a server, owners agree to follow the applicable listing requirements.