BF2S Forums Write a ROE of your own...

In great appreciation of the task at hand... I'll be cleaning the spam.
Be constructive or don't respond;

R

I will pass this on to my clan, we will reply soon .. ....

in my opinion, the anti-ROE craze going on at bf2s has been started by a few (populair) members *cough*TOP*cough* and now the entire forum is against it. although I don't entirely agree with the ROE i think that was it is supposed to do, keep stats-enabled servers fair, has been achieved.

ExecutionerStyle wrote:

No stat padding rules will be difficult. As you are aware, it's a cause for problems in the community. Accusations everywhere of padding, people caring more about other's stats. Indeed, this is mostly from the player itself, but if there is no punishment for having stats, then there would be less "OMFG PADDER" and more "omg i hate ur high scores bitch".

Another thing that would be REQUIRED if there were to be rules regarding padding would be that EACS needs to be WAY more cooperative in reset appeals. Having seen mele and Ins4n3's email exchanges with EA, it's disgusting. EA needs to:

1) Provide evidence if possible

2) Provide the real reason for the reset so the player knows not to do it again

Third, resets should be done depending on the severity. If they padded a few hundred points, reset those points. If they padded for some awards, reset those awards. If they continue the behavior, THEN reset the entire stats of the player. It may be more time consuming for EA but it would be much better and less Draconian than the current system.

EDIT: The 'chink spic' wouldn't be in the real ROE, i just put it there as an example of why that thing in the ROE would be far better than 'no infantry only'

as you see the BF2RS/BFROE programs were started from scratch, and had to deal with the many different aspects of BF2 and the community at large,

the reason I started this thread was to give a little insight on just how hard our job is, not only do we have to keep the community happy dealing with not only the exploiters and cheaters but the padders and EA as a whole..

so if you think it's hard to try and write an ROE, then the next logical step is to define and code a reporting system that ensures that innocent players do not fall thru the cracks and get reset by accident,  we are only human and a few mistakes have been made, but as a whole I believe we do a great job..  both programs..

so you guys have just touched the tip of the iceburg..  keep going...

Indian

yes we will, along with alot of other new games that are coming out..

In real life the enemy doesn't have rules.  So, why do these server like to make them.   Stupid servers with no uncappable base raping allowed.   I was following a guy in a jet and just as he got into his airspace I fired my missiles and killed him and they said I wasn't following the rules.   How gay is that.  I say none of this stay out of enemy airspace.  The enemy doesn't follow rules like that.

while I agree with you,

here is the challenge tho,  you have to deal with the code and players that are handed to you..

it's not our job to rewrite the game, but to enforce what is handed to us...

so as you see this gets harder

Last edited by BFROE|IndianScout (2006-07-20 14:28:50)

All I can say is how can you claim that you are shutting down against ROE servers when searching the word knife in the search....thing you get a list of around 40 strong.....

usmarine2005 wrote:

Gee, when I say that it gets deleted.

i'm sure it'll go soon enough..

but seriously.. if there were no ROE.. there would be no "OMFG WIPED!!LOLZ!" or I CAUGHT A STAZPADDR!! CUM SEE!!"

and people would be able to have fun once more.. my theory.. if you dont like what someones doing on a server.. then dont go on that server..

if someone statpads you? who cares? its their way of fun.. just like playing the game YOUR way is YOUR way of having fun..

fair enough glitching should be enforced.. but theres only two real invincible spots in the whole of vanilla bf2.. and they were introduced with the "revolutionary car drop" feature.. which has caused more trouble than benefit to the community as far as the amounts of complaints go..


i'm up for debating this as long as we get change that benefits people other than those who cant help getting owned by someone "baseraping"


p.s. who the fuck made that term up? its one of the lamest things i've ever heard..

DecJW wrote:

Infantry only is allowed. The rules set on a server which is paid for by admins - should be able to run it how they want

Very true.  Servers are expensive, so leave it up to the people who paid for it.  Unless you paid for it, who are you to tell them how to run it?

Last edited by usmarine2005 (2006-07-20 14:40:16)

BFROE|IndianScout wrote:

guys PWING the TK NOOB doesnt make an ROE

Hear hear. Given all the stick you get personally and the ROE gets, actually having the opportunity to provide some input shouldn't be wasted on juvenile one-liners.

BFROE|IndianScout wrote:

it has to be written so that the 2 million people who purchased BF2 can understand and abide by it,  there are more rules and such that have to be followed...

I'm actually for rules since we sign an agreement that we agree to abide by when we join up but "there are more rules and such that have to be followed" is only true if there are actually more rules. If you don't start with the prior assumption of the many rules we have now but from a clean slate it might be better.

BFROE|IndianScout wrote:

Admins who make their own ROE and dont abide by the official one will get delisted or shut down, that is already stated in the new ROE...

Like when? Is this like the 'rules' on eBay which, for all practical purposes, apply to the sellers and not the buyers?

In all seriousness pick a day and I could find you a half-dozen servers I bet that have at least one rule that's against the letter of the ROE, and maybe a couple more with rules that are against the spirit of them (assuming I've understood them correctly, some are a little vaguely worded). I can give you three of four examples right here if you want them.

Okay, on the suggestions.

FWIW I think that having something coded is the best idea going... if EA don't want X or Y to be done simply make it physically impossible. With the exception of cheating obviously, in every FPS I've ever played if you can do it it's fair game and that's the way it should be.

Example: they changed the way vehicles work so that only the driver counted for the flag-capturing speed (so you had to bail out to capture at the speed of a whole squad). Personally I think that was a good thing for a couple of reasons, but anyway, then we get a rule about not being allowed to heal, resupply or repair from within a transport helicopter... okay, then why not code it?! Then, instead of a system where you have the potential temptation to 'cheat' you simply can't do it, end of story.

Failing hardcoding it I think ExecutionerStyle's rules (post #12) are a good start from what I can think of now. That last one:
4) Servers must clearly show server rules.
Emphasis on the must. That way if you don't like their rules (no baserape for example) you can cancel the loading and find another server that's more to your liking. BF2 is slow enough to start, log in to and load each server/map without having to waste additional time because you're finally in but then realise that some rule or setting isn't to your liking.

ROE:
1 GLOBALLY ENFORCED SERVER RULES

§1.1 A player may market or advertise anything they wish unless specifically told by an admin not to do so.

§1.2 Server admins can customize standard Ranked game settings, such as round time, tickets, ect, but cannot password a Ranked server.

§1.3 Server admins can choose to enforce what vehicles and weapons are used in-game. This includes but is not limited to:
     §Knife-Pistol Server
     §Infantry-Only servers
     §Limiting the types of vehicles used in-game

§1.4 Server admins can enforce what kits are used so long as they are enforced fairly.

§1.5 Server administrators may not use non-standard (custom map packs) maps or modified versions of standard maps.

§1.6 Players can feel free to harass or impersonate BF2RS admins, but by doing so acknowledge that they will be perma banned or wiped if caught.

§1.7 TK Punish can be set to off, and is the default option in Ranked servers.

2 EA OFFICIAL PUBLIC SERVER RULES

§2.1 You may not use any rascist language in the All, or Team chat.

3 LOCAL (PRIVATELY RENTED) RANKED SERVER RULES MODIFICATIONS

§3.1 Rules that a private Server administrator may think he has the ability to enforce, but does not include, but are not limited to:

§ Artillery fire or bombing runs on main (uncapturable) bases.
§ Prolonged or sustained attacks on main (uncapturable) bases (i.e. spawncamping).
§ Using the Transport Helicopters to take flags (Blackhawk whoring or flag hopping).
§ Using C4 on jeeps, or other fast moving vehicles to take out other vehicles.

However, Clans may customize and enforce the rules providing they don't break the above ROE (eg. impersonating clan members ect.)

EDIT: Oh, and dont hack, sorry left that out

Last edited by Ben>You (2006-07-20 14:53:04)