Project Reality Forums

Psyko wrote:yeah but be honest, it was because the opposite team was clan stacking yeah?

I'm guessing, Muttrah, and as soon as the cas whores crashed all their assets they raged and the MEC took back their flags...........am I warm?


Just dont make it sound like it was an even fight, it never is in those situations.

Alright guy.
Whatever you say.
We were US.
But yeah, clearly you know better than I do.

Iron ridge has this problem, capped enemys last flag, held it 20min. Got capped out and lost.

Their bleed was less than what they gained in capping 3 flags.

Clan stacking is the issue and cause for most steamrolls imo. Then you have a team of 90% rookies. But I can name a lot of times where we've came back from our last flag being lost... we captured it and boom. Our commander gave a motivation speech for like 5 minutes... IT worked!

It was on Khamisiyah iirc.

matty1053 wrote:Clan stacking is the issue and cause for most steamrolls imo. Then you have a team of 90% rookies. But I can name a lot of times where we've came back from our last flag being lost... we captured it and boom. Our commander gave a motivation speech for like 5 minutes... IT worked!

It was on Khamisiyah iirc.

Yup, I seen it happen too many times to disagree. But what can be done?

Psyko wrote:Yup, I seen it happen too many times to disagree. But what can be done?

About one sided teams... admins can scramble. But they usually fail to do so since their friends and clan buddies are on the same team they are on. I'm taking a break from a few servers because of one sided ****. The beginning of the round: "ADMIN, can you switch blahblahblah please????". There too many times that you have admins constantly allowing shitrounds that steamroll. I can understand ONE round... but 2+ is ridiculous. But I have seen a lot of players comeback since the group of friends on the team that is steamrolling... their tanks and heavy assets get's killed. Then they start whining and blame everyone else for losing. (I find it hilarious honestly, then you really see who the immature ones are).

I am very mixed on this suggestion...

Pro's:
It would help end steamroll rounds end quicker.
MAYBE help rounds end "quicker".

Cons:
If a team rushes the other team... they can easily win in like 30 minutes.


Middle:
It could help people play better defensively and smarter.

I just won't really support this, as...
1. I like rounds that last longer.
2. Really would kill the amount of tactics you have to use.
3. People would be stupid and abuse this somehow.
4. If people didn't like the map being played... they'd intentionally lose it quick so they can get to a overplayed map.

matty1053 wrote: Cons:
If a team is even doing really good and they lose the last flag... they don't deserve to lose.
If a team rushes the other team... they can easily win in like 30 minutes.

if the team is doing good they not even gonna lose the last flag, that mean the other team is doing better.

Roque_THE_GAMER wrote:is the team is doing good they not even gonna lose the last flag, that mean the other team is doing better.

Ugh... my fault lol. I'm tired, it's late... definitely NOT what I wanted to say at all. I'm gonna edit that bit out and act like it never happened.

have a script use tags to identify clan tags (any tags the same as each other) then count them, (theres 5 NEW guys, 4 3Dac guys) put one clan on one team and the other clan on the other team?



players vote for scramble?

Well !scramble should really consider clantags, since clan people will switch after it anyway.
I'll have a look at it.

The game is not always over on the last flag.. I've seen it many times when e.g Blufor gets steamrolled and Opfor just caps flags but doesn't build fobs. Then they loose the spearhead squad at the last flag and then Blufor steamrolls Opfor back to their last flag and wins the game.

it's rare but happens

The question is this: does the chance of a possible come back lead to more player satisfaction than the mercy of ending a probable agonisingly slow defeat would? I'd say in almost every instance we're better off ending the game on last flag, especially on a pure attack-defence map (e.g Pavlovsk Bay, Ramiel AAS)

We are going to standardize the bleed if a team is out capped.

we are going to try*

[R-DEV]Mineral wrote:we are going to try*

Somebody make a version of that green screen with BF2 error windows and bf editor in the background.

[R-DEV]Mats391 wrote:We are going to standardize the bleed if a team is out capped.

that mean the round will over when the last flag will be captured?

Roque_THE_GAMER wrote:that mean the round will over when the last flag will be captured?

Not instantly over, but a reasonable bleed so it wont have hours to finish.

It we haven't discussed it yet but personally if you can't take it in 15m then might as well ene the round.

if they blend allot they gonna lose anyway it will just take longer to finish they.

How about a delayed heavy bleed? Easy to implement.

5-10 minutes after the cap of the last flag a heavy bleed starts. That way you get the chance to retake it, without having a boring 2 hour aftermatch.