BF2S Forums Your Opinion is need on proposed Server Rules

Too many rules to follow in a battle.
2. The main base is part of the battlefield, to steal vehicles you have to attack most of the time.
4. Commanders don't always know what is going on where you are at and often want you to go to a different  flag when you are trying to stop another from being capped by that lone wolf giving your team hell.
5. The commander should be able to jump in a tank that has been sitting idle for 3-5 min in main base.  I do this and take the tank or APC to the front line and give it to my teamates.  Some people would rather stay near the front line to try to hold the enemy off.
6. Do what ever you have to do to stay alive, if that mean bunnyhopping your ass to the nearest cover then so be it. How many jumps constitutes BunnyHopping?
7. Paratroopers are part of the battlefield.  Very wierd rule. I have never seen this one before
9. Like in rule #2. What if the last base left is an uncappable?  Do you enter and rape the enemy or stay out side and rape the enemy.Edit An example of a good tactic in karkand is to take to tank or Apc as USMC and Spawncamp the hotel just one road over to the west in the archway and alley. Cuts their team in half and allows US to get hotel early and move on with the game.End Edit
10. Can they debate the rules in game before they break them.

The rules I didn't list are expected.  Too many to follow and harsh punishments with no warning.

Last edited by JG1567JG (2006-08-13 02:07:32)

fierce wrote:

I reedited your ruleset:

1. Hacking / Cheating / Glitching / Stats Padding. Anyone who feels the need of hacking, cheating, glitching and/or Stats Padding will be severely punished. To remind you, Glitching is the use of known errors in the code, like (Cartillery <- that's not a glitch or error in the Code) the Karkand Hotel Glitch. Stats Padding is the artificial boosting of your Score.

I disagree with every other rule you posted.

I second that. It is total bullshit to play on a server that has so damn many rules you cant even enjoy your stay. I joined a karkand map the other night and was shooting people with my G36C (i think that is the one for medic) and got kicked because the server didnt want medics....?.....  It wasnt a P/K, they just wanted no revives so the game went faster.

Oh well, just my .02....

RULES ARE MEANT TO BE BROKEN

MILHOUS

cyborg_ninja-117 wrote:

spawncamping: if you are spawncamped go spawn elsewhere, if its last uncap, your team suck.
bunnyhopping: cant shoot me? go play sumthing else
intentional tk: if i see a noob in my jet, n00b jecter to the rescue
disobeying commanders: i can do whatever i want, sumtimes the commanders are idiots

fierce wrote:

I reedited your ruleset:

1. Hacking / Cheating / Glitching / Stats Padding. Anyone who feels the need of hacking, cheating, glitching and/or Stats Padding will be severely punished. To remind you, Glitching is the use of known errors in the code, like (Cartillery <- that's not a glitch or error in the Code) the Karkand Hotel Glitch. Stats Padding is the artificial boosting of your Score.

I disagree with every other rule you posted.

Same here

9.. Well, as much as I don't like spawn camping, it's, unfortunately, part of the game.

The rules 4, 5, 7 and 10 are just stupid and ridiculous, imo, and need to be removed.

4. What if the guy doesnt want to be part of a squad for whatever reason? You shouldn't need to be forced just because -you- can't stand lone wolves for whatever reason -you- have.

5. The commander should be permitted to take any vehicle he wants, lest it detracts him from performing his duty as a commander properly. Though I think commanders that jump in attack helicopters and aircraft should be replaced.

7. What? A rule against paratroopers? Are you kidding me? What's next? Let the enemy engineer repair his tank before you're allowed to engage him again? He decided to bail out, therefore he's at the disadvantage. Tough luck.

10. Whereas incessant whining is only annoying and won't do any good, discussions about what can be improved and what is simply stupid are always appreciated, in my book.

Which column is agree and which is disagree?

Rule 1. OK

Rule 2. OK, but this should be limited to players in the area, and to vehicles that belong in the area. I say this because I have seen players get vehicles from other spawn points and drive them back to a main base and then say you cant shoot them. This is an issue on SF maps that are small rather than BF2 maps, but it is worth thinking about.

Rule 3. OK, but in reality very hard to admin, how can you tell if a TK was acidental?

Rule 4. LAME, cant be admined properly. the teamwork and squad thing, OK ish as a rule, but players in squads wont follow orders if they dont want to, just like long wolves can be the best teamwork players. As for people following commanders orders,  the respect of the squad leader or commander is earned, not just by being one, but by actions. a good commander wont need your server rules to get squad to do want he wants.

Rule 5. I agree in prinsipal, as long as you have 32 or 64 players. But if there is not commander, and the you want a UAV or supply create, but do not want to stop fighting you should be alllowed. I would suggest that you say that if a commander wants to be in the action, he should resign if any other player wants to command only.

Rule 6. OK

Rule 7. LAME, as far as the SAS spawn point goes, there is always the other uncap, as for people jumping out of jets or helos, if you have done enough to get them to jump out then you deserve to try and get the kill. What about a player that gets in a jet, fly over an enemy base and bails over a tank or chooper or jet, not being allowed to shot them while dropping means they can get the vehicle before they even touch the ground.

Rule 8. OK

Rule 9. OK, but add the word repeated. If I'm rtrying to a flag and someone spawns in front of me I shoot them, and that should be OK, but to then stay in that place and shoot more people should be wrong.

Rule 10. OK, but there is a difference between arguing about a rule and questioning aspects of them. Make sure that there is a website where players can get detailed info on the rules and debate their good and bad points.



DrM

Last edited by DrM (2006-08-13 12:44:50)

usmarine2005 wrote:

Do not allow cyborg_ninja-117 to carry the M95 and all will be well.

oh you no likey m95? how about turning off TK's in the server and all will be well

usmarine2005 wrote:

cyborg_ninja-117 wrote:

usmarine2005 wrote:

Do not allow cyborg_ninja-117 to carry the M95 and all will be well.

oh you no likey m95?

LOL.  It is a great weapon, that is if you shoot the enemy with it.

sometimes, there are real noobs flying, and you have to kill em b4 you get baseraped.

I feel you can't tell a commander to totally stay out of vehicles ... especially when tanks are left behind for the enemy to steal

the paratrooper one will never work, neither will spawncaming or both commander ones...

rules: there are no rules but people hanging around jet/heli spawns will be classed AFK and kicked.

play rough

The only rules any server should have are:

-No Hacking.
-No Racism.

Anything else goes, it's war, deal with it.  Don't bitch about baserape, go cap a flag.  If you wait around for a jet/helo, you deserve to get raped by the other teams jets/helos. 

I can't shoot you while your parachuting, I have to wait until you hit the ground and have a better chance at killing me? Bullshit.

Intentional TK's.  If some fucktard on my team keeps blowing up our jets/helos/tanks, or is placing arty on our bases, I will TK/revive him every 14 seconds and take the neg's until our planes are off the runway and my team is out of harms way.

And you can't ban someone for not listening to commander.  I've played with a lot of commanders who don't know their ass from a hole in the ground.  Sometimes, it's more beneficial to cap a flag you are running towards, than to go all the way across the damn map to destroy a bridge, just because the commander gave you an order.