dMw BF3 Server Rules - Explained - Post your feedback here

Started by Gone_Away, November 14, 2011, 11:45:32 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Gone_Away

Here's our thoughts. Constructive Feedback Welcome:

1. No Spawnraping or Shooting into the Uncaps (including Mortars) - even on Rush, once it's cleared you can't go back or shoot into it.

Spawnraping will always be unacceptable on our servers. The inclusion of Mortars into this rule and the corresponding rule number 3 will hopefully remove some of the frustration in the current game.

2. No bunny-hopping, including jumping around corners - this is a standard on most of our games.

This is normally a problem in games with CQC (close quarter combat). In BC2 it wasn't a problem as it wasn't that tight. BF3 has these tight corners and as a rule dMw have always frowned on bunny-hopping and jumping around corners.

3. No Sitting in the Uncap or Spawn and using Mortars. - as this encourages spawn raping. If you want to get your mortars out, run away from your uncap for a minimum of five seconds and then feel free to setup.


We want to eliminate spawnraping as much as possible. Firing mortars from within your uncap or spawn will only encourage others to sneak in and stab you. Run away from your uncap for 5 seconds and then set up.


The 5v5 rule on Vechicle Use has been eliminated completely as the admins and I feel that the game is much more balanced than BC2.

Feel free to comment.

TheDvEight

with the rush game mode what is the stance on a "defender" staying in an old m-com site once those two m-coms are blown up to "frag hunt" once the map has moved on to the next set of m-coms and where the "defender" is now is the attackers spawn area.
"Mira Mira on the wall who\'s the fairest of them all?" - Dickdastardly "it\'ll sting a lot" - Lesion

RizZy

I think it probably will run the same as BC2 did Dick, it's upto the attacking team to clear the area & not you to get out of there, but once you've been removed from the old site you shouldn't go back there.

Vargen

Quote from: RizZy;337395I think it probably will run the same as BC2 did Dick, it's upto the attacking team to clear the area & not you to get out of there, but once you've been removed from the old site you shouldn't go back there.

This is what was said in an earlier thread. It is up to the attackers to clear the area, but once it is clear you may no longer go back there.

 One question I would ask is as to what out stance is on the rush map at the tunnel. As to if the attackers can use the helicopter to enter the tunel from the defenders side. I don't know where the defenders spawn on that part of the map, as I've never been pushed that far back ;) /flex
Battle.net - Varg#2301 | Steam - Varg1983 | Origin - Varg1983 | Warframe - Varg1


faust82

Spawn is at the tunnel opening if I recall, so firing anywhere near that would border on spawn rape. Rushing a chopper through it and landing people in behind the objectives, while still on the right side of the spawn.. You'd get some flak from the whiners, but as far as I see it, it's within the rules. The key element is, are you killing people IN their spawn? If no, then go :D

The five second running rule on the mortars does seem like a good idea, but it's not until we try it in practice one would start seeing flaws. My concern is that this will be biased against defending side in Rush, since five seconds out of spawn you're in the main meat grinder. Then again, until we've tested it I'm not sure it'll be a problem.

Will be interesting to see how the rules impact our server, and if we can get the games running the way we all know they can :D
Coppula Eam, Se Non Posit Acceptera Jocularum!

Vargen

That's my interpretation as well. I got some comments on it when I did it to break the tunnel camp/blockade last night, so I didn't land and kept flying inside the tunnel from the defender side. My passengers didn't like that though, so they abandoned ship :narnar:  

Also there is one more rush map I would like to see removed from the map rotation, Noshahar Canals. That should be the one where the carrier is fairly close to the harbor area. I guess we can leave it a bit longer just to see if some rules and enforcement is enough to keep that map fun. If it still ends up being one sided we should consider ditching it though.
Battle.net - Varg#2301 | Steam - Varg1983 | Origin - Varg1983 | Warframe - Varg1


Gone_Away

Guys,

Just to be Clear.. THERE IS NO VEHICLE LIMITATION RULE.. IF IT'S 1 V 1 - KNOCK YOURSELF OUT!! :D

5V5 DOES NOT APPLY IN BF3.

Hope that clears up any misunderstanding.

TheDvEight

Ninja can you sticky this post? also encounterd a problem with the rush rule i was in there uncap i was defending both m-com sites had gone, but i was not killed so not breaking the rules, but a squad member spawned on me (so therefore is) i can see this being hard to admin unless a member of dMw. is in one squad at a time out of all the sqauds on the attackers side
"Mira Mira on the wall who\'s the fairest of them all?" - Dickdastardly "it\'ll sting a lot" - Lesion

Gone_Away

Quote from: .DickDastardly.;337491Ninja can you sticky this post? also encounterd a problem with the rush rule i was in there uncap i was defending both m-com sites had gone, but i was not killed so not breaking the rules, but a squad member spawned on me (so therefore is) i can see this being hard to admin unless a member of dMw. is in one squad at a time out of all the sqauds on the attackers side

I'll sticky but tbh your squad should be able to spawn on you where ever you are..

Blunt

Quote from: .DickDastardly.;337491Ninja can you sticky this post? also encounterd a problem with the rush rule i was in there uncap i was defending both m-com sites had gone, but i was not killed so not breaking the rules, but a squad member spawned on me (so therefore is) i can see this being hard to admin unless a member of dMw. is in one squad at a time out of all the sqauds on the attackers side

Quote from: Ninja_Freak;337503I'll sticky but tbh your squad should be able to spawn on you where ever you are..

I agree Ninja, if the game allows you to spawn on your surviving team-mate, then you should.
After all, he is behind enemy lines and in grave danger.
It is down to the attacking team to ensure that their new base is cleaned out.
I do a sweep of the base if I have suspicions that there are "left-overs"

I really think this "spawn rape" moaning is getting out of hand.
If we are after "realism", and I am, then in the situation that you can see your enemy, you can shoot them.
I've been pinned down in spawn on more FPS titles than I care to remember, and I reckon it's up to you and your team to fight your way out.
There may be a few exceptions to that rule, but, on the whole, it's up to your side to sort it out.
Some of the best team-play I've ever been involved in has been a battle out of spawn;
We may not have won, but the experience was invaluable.

Team comms helps :)
Regards
Blunt


People who blow things out of proportion are worse than Hitler.


TwoBad

Quote from: .DickDastardly.;337491Ninja can you sticky this post? also encounterd a problem with the rush rule i was in there uncap i was defending both m-com sites had gone, but i was not killed so not breaking the rules, but a squad member spawned on me (so therefore is) i can see this being hard to admin unless a member of dMw. is in one squad at a time out of all the sqauds on the attackers side
I might be wrong but once the m-cons are gone you can only spawn on your squad until the new m-con's appear?  If that is the case then it’s a bit of a non-issue.
The Battle of Damnation Alley, 25th January 2015
\'You are hereby awarded the Military Cross, posthumously, for an act of exemplary gallantry during active operations against the enemy on land.\'
[SIGPIC][/SIGPIC]

TheDvEight

"Mira Mira on the wall who\'s the fairest of them all?" - Dickdastardly "it\'ll sting a lot" - Lesion