Good Topic.
Make everyone (servers/users) accept and sign the ROE when they download Patch v1.4 and renew the aggreement on each subsequent patch.
Ranked servers/players need rules to follow or the statistical database is crap. EA could have gone another direction and compartmentalized the database allowing people to classify themselves for example, as Infantry Only or Original Game and only join those type ranked servers. This would allow all the stats to make sense in many ranked environments. But EA didn't give us that.
Somebody said "since we paid for it we should get to make our own rules". We can make our own rules on non-ranked servers or single player if you like. The ranked BF2 database is a nice to have addition and needs to stay clean and balanced as it was intended.
Think of all the cool stuff EA could have added to BF2 if we didn't have stats sucking up bandwidth and computer processes.
We come from all over the world, all ages, races, religions, backgrounds and a couple knuckleheads so unfortunately there is no such thing as "common sense" or people would not disagree about concepts like spawncamping, statpadding, K/P only servers and such. So we can shelve that part of the discussion. K/P is effectively a MOD as it significantly changes designed score per minute.
lol someone said "no rules" Games exist because of rules. The game is to beat the opponent without cheating. There is no game without rules. Basic rule that exists in all games = do [this] to win. Game coding is part of the game rule system as is the EULA/TOS/ROE. The ROE stays and EA will ensure that better coding happens in 2142 to fix the admin intensive environment of BF2...or not.
Rules should make no assumptions.
EA need a concise description of game design to "teach" people the environment they are in. So much of the forum activity is about conflicts in common sense. Try something like this:
GAME DESIGN - NON-LINEAR WARFIGHTING
BF2 is a First Person Shooter (FPS) with a complex enhanced multi-level with both tactical and strategic team play using squad members, leaders, commander roles/assets, minimap operational graphics, orders and Voice over IP (VoIP) to compliment all the requirements of battle. The BF2 built-in communications flow assumes all players habitually play in a squad or command. Each map has a mission scenario included which sets the basic focus for each team. The game win-loss outcome is based on captured flags and/or kills..etc. This design creates a balance between earning individual stats and team wins or losses.
Other helpful items to resolve false claims:
SCOPE - RANKED SERVERS
The ROE applies to all ranked server providers, server operators and administrators contributing to the BF2 statistical database. The ranked server program and ranking system introduced by DICE and EA for Battlefield 2 is designed to promote a system of statistics gathering and rewards for BF2 players on a level playing field in which players can expect the same standard configuration and playing environment on any ranked server they play on. These standards are achieved and maintained by ensuring that all server providers and server administrators are abiding by a common set of rules as determined by EA.
AUTHORITY TO MODIFY OR APPROVE MODIFICATIONS -
EA retains exclusive control over any ranked game modifications, coded or by server rules and/or enforcement. Any permissions or delegated authority provided by EA must be posted in a public access(no account required) location on your server homepage.
PRE-EXISTING AGREEMENTS OR UNDERSTANDINGS
Any agreements with non-EA agents currently in place to deviate from this ROE must be renewed and publicly displayed on the home server site.
Add this:
BF2 UNIVERSAL GAME ETHICS
+ Respect others of all levels
+ Be a team player (cooperate and share the roles/assets)
+ Follow the EULA/TOS/ROE
Next make each sentence stand alone because we have readers at all levels of language and misunderstanding is easy. I lifted and revised from the ROEv2 for the following and ommited lines with no changes.
2. RULES AND POLICIES FOR ALL SERVERS AND ADMINISTRATORS MANAGING RANKED SERVERS (PUBLIC, PRIVATE OR CLAN)
These rules and policies govern everyone running ranked servers. Failure to comply can result in the server being delisted. Servers have no authority to deviate from the EULA/TOS/ROE except with specific written approval by EA which must be posted publicly on their server homepage.
2.2.4 Server Administrators may not abuse users of their server regardless of status of paying member or casual user.
2.2.5 Servers may not use terms like "Knife/Pistol only" to list their server whether the rule is enforced or not.
2.3 “In-House” Ranked Server Rules:
Public Ranked Servers and Private rented clan servers may introduce custom rules that apply uniquely to their servers and which result in minor changes to gameplay. These “in-house” rules are allowed as long as they do not violate the conditions of use of a ranked server as determined by DICE and EA and as long as they are explicitly announced in the server description or on the loading screen, so that players joining the server are aware of them before they start playing. An excessive number of rules may lead to exploitation of game design.
2.3.1 Prohibited “In-House” Ranked Server Rules:
Server Administrators may not implement or enforce server rules on ranked servers that prohibit players from using any roles, kits, weapons, vehicles or other features of the game while playing on their server. Examples of such rules that would violate the conditions of use are:
(a) Servers may not prevent any players from being Commander or Squad Leaders.
(b) Servers may not prevent any players from using certain vehicles such as jets, helicopters or tanks.
(c) Servers may not prevent any players from using commander assets (artillery, vehicle drop, UAV or scans).
(d) Servers may not prevent any players from using certain weapons or items (such as flashbangs or C4) or
(e) Servers may not post or enforce a “pistol only” or “knife only” server rule.
(f) Servers may not post or enforce rules restricting player kit/weapon use on capturable spawnpoints.
(g) Servers may not post or enforce rules restricting specific attacks targeting the enemy commander’s assets.
(h) Servers may not post or enforce rules using maps not available within the game to describe restricted locations.
(h) Servers may not create or enforce zones-of-play within a map/game that violate 2.3.1. a, b, c, d, e, f, g.
2.3.2 Allowed “In-House” Ranked Server Rules:
Server Administrators may implement and enforce rules that result in minor changes to gameplay behaviour or styles as long as these are clearly stated before a player starts playing on a server. These rules typically introduce minor restrictions on how a certain aspect of the game can be used.
Examples of such rules that are acceptable as long as they do not violate any rules listed above are:
(a) Players may be restricted from use of explicit, offensive or racist language in-game.
(b) Players may be restricted from deliberately performing actions that hinder their own team (such as last-minute team-switching, excessive or Intentional Team Killing or Forced Team Killing, destroying friendly vehicles, or placing vehicles to block their own runways.
(c) Players may be restricted from using vehicles as Commander (No Commander in jet/Armor, etc.).
(d) Players may be restricted from attacking enemy main bases (uncapturable flags), including artillery strikes, vehicle drops to block runways, bombing runs with aircraft or sustained infantry attacks, except as in 2.3.1 (g) above.
(e) Players may be restricted from using transport helicopters to capture flags, bypassing enemy forces (flag hopping).
(f) Players may be restricted from using C4 explosives on vehicles to destroy other vehicles (C4-ramming).
(g) Players may be restricted from ignoring requests from Server Administrators or abusing Server Administrators.
(h) Players may be restricted from excessive TK punishment of unintentional TKs.
(i) Players may be restricted from commanding more than 2 rounds in a row unless no other player applies.
[end of ROE]
Some of the standard server settings as well as list of current cheats/hacks should just be refered to and not listed. The post them at a central public place on EA.
Note that since the new ROE is requiring servers to post rules in the JOIN SERVER screen that deviate from the orginal game then two things are true - you can't have alot of rules about spawncamping and do this don't do that stuff. The second is only post changes to orginal design - which means you don't need to say "mainbase attacking is allowed" that's part of the original game
The best idea is still to Code the ROE