Patch 1.3 rumour discussion!

[SaladFork]

Re: Patch 1.3 rumour discussion!

That's a perty solid source on that issue.

While he is part of BFRoE, the BFRoE staff was not involved in this round of patch testing.

~Salad

[WarGimp]

Re: Patch 1.3 rumour discussion!

While he is part of BFRoE, the BFRoE staff was not involved in this round of patch testing.

~Salad

Good point. However, his info has been solid in the past and he's not really one to spread false rumors. Thus "perty" solid in this case. Would be nice to get some offical info tho. Let people know if they should be practicing their SL skills.

[SaladFork]

Re: Patch 1.3 rumour discussion!

Good point. However, his info has been solid in the past and he's not really one to spread false rumors. Thus "perty" solid in this case. Would be nice to get some offical info tho. Let people know if they should be practicing their SL skills.

I have full respect for IndianScout, and I know that he would not violate the NDA just to enforce a rumor. The NDA is very clear as to what it means, and I'm sure IndianScout knows all about the NDA, and its significance.

The only time the NDA does not apply to a person (and said person can say whatever they want), is when said person is not testing the patch, and thus is not bound by the NDA.

~Salad

[Auto-ER-]

Re: Patch 1.3 rumour discussion!

Still these markers were put into the game for a reason, and it makes no sense to delete them if squadhopping was an intended style of gameplay that already occured during the testing phase (otherwise it would be unintended). It's ridiculous that you have to rotate the ability to call supplies etc. to be more effective.

Why do kits linger for 30 or so seconds after a player dies? Surely it's just as ridiculous to completely change your "training", uniform, and job function by clicking G. That is changing your function by clicking a button is it not?

On a VoIP disabled server this aspect doesn't matter and it isn't that important from an overall point of view, but the developers clearly stated in some interviews that they wanted to implement a chain of command. This chain is represented by the VoIP system (commander talks to SLs, SLs talk to SMs), and it's damaged by squadhopping IMHO.

The commander is still talking to the squad leader, just one that got promoted when the other one died. Nothing is damaged, no one has any real rank, or responsibility, it's a game. You are playing squadleader, you are not a squadleader, see the difference? You, nor many that plaly have any training that makes them any more qualified then anyone else, and everyone can be a squadleader/commander.

Well the fact that YOU'RE screwed just because you have to spawn at a flag instead at a squadleader once in a while doesn't mean that everybody else is. You can apply that "creative" label to C4 tossing and dolphin diving and bunny hopping too, still it was obviously NOT what the developers intended, as that stuff was already removed.

I (as you imply by capitalizing you're) am never screwed. I can play the game, and deal with tactics like squadhopping, dolphindiving, bunnyhopping, etc. They don't bother me because I have the inclination to be better than them creators intent or not. And since as I have already said, there is a command to divide and form multipule squads, and they made it so you could do this, and no, it isn't an accidental side effect of the programming. Of course since one of the head programmers thought you could get the Aerial service ribbon from a helicopter, what they say doesn't really impress me as far as "what they intended"

The latest patchs are nothing more than PR catering to the weakest links. Those that couldn't deal and cried the loudest. So far there have been threads bitching about every aspect of this game, I wonder if anyone actually likes playing it.


For the record, I myself have squad hopped to a random squad to be nearer a fight maybe twice since I started playing. USually the guys I play with a all on TS and we'll be in a few squads throughout the team, so we have a good idea of how the whole battle is going. Personally, if I am squadleader, I want my guys on me, I kick lonewolfs that aren't talking or staying with us. If the situation dictates, I'll rotate, but mostly I try to keep the position incase the aforemention nooblet gets it, it can halt momentum, and I likie being able to talk to the commander to get the big picture.

[WarGimp]

Re: Patch 1.3 rumour discussion!

I have full respect for IndianScout, and I know that he would not violate the NDA just to enforce a rumor. The NDA is very clear as to what it means, and I'm sure IndianScout knows all about the NDA, and its significance.

The only time the NDA does not apply to a person (and said person can say whatever they want), is when said person is not testing the patch, and thus is not bound by the NDA.

~Salad

So... what yer saying is every tester needs a buddy to look over his shoulder 'n start yappin, eh?
:p

[SaladFork]

Re: Patch 1.3 rumour discussion!

So... what yer saying is every tester needs a buddy to look over his shoulder 'n start yappin, eh?
:p

The NDA includes the fact that a tester must use his/her best effort to prevent leaks of the included material(s). Having a friend look over your shoulder and leaking the information will still legally make you responsible.

All I'm saying is that while IndianScout has a high ranking position in BFRoE, and is probably 'privy' to information normal BF2 players aren't, it doesn't mean his word is always fact.

~Salad

[DrunkenPirate]

Re: Patch 1.3 rumour discussion!

[WarGimp]

Re: Patch 1.3 rumour discussion!

Well, we know one thing for sure...

Demize was right.
Speculation is fun.

[colony]

Re: Patch 1.3 rumour discussion!

Really not concerned with coop or squad hopping. As long as they fix balance issues(J10), red tag bug and better menu interface i'm happy.

[BIC]

Re: Patch 1.3 rumour discussion!

I hpe Squad hopping will be banned for the game, this is why:

When a SQUAD tries to get a FLAG, ususally the SL would stay back a little bit to stay alive and allows his squad members to respawn on him. If at one point the FLAG defenders soldiers succeed to kill the attacking SL and by doing this kind of stop the continious attack from that particular SQUAD, then the defenders did a very good job and the attacking SQUAD should regroup and replan from a FLAG RESPAWN POINT. They were defeated in their attack, go back to a FALG point.

To my point of view, it is ridiculous that a SQUAD can continously attack a FLAG by doing SQUAG hopping. Even more, when a SQUAD member respawns on the attacking SL, he can leave the SQUAD and then make another spot available for any other dead team player on the map that wants to joint the attacking SQUAD. At the end, the whole team could respawn at that specific FLAG, just using a single SQUAD LEADER: respawn, leave, respawn, leave, .... Think about it, that is ridiculous!!!!

When you don't succeed to get a FLAG, you should go back to a FLAG respawn point. The game was not meant to have 32 changing (over time) mobile respawn points.

Hey!!! That just my personel opinon. I like BF2 and I think it's a shame to see squads using lame tactics like squad hopping.

[Curtis12]

Re: Patch 1.3 rumour discussion!

well i really could care less about squad hopping as i never do it one thing that looks nice is dropping humvees

[Red Devil]

Re: Patch 1.3 rumour discussion!

Is the shelf life of mines, C4, and claymores set by the server or is it hard-coded?

If it's hardcoded, it sure would be better if they weren't removed after a couple minutes. Kinda pointless to mine the ramps on Karkand (or whereever) only to have them disappear on you...

Also, EA/Dice, can you have The Ride Of The Valkyries play when we're in the USMC transport chopper like in Apocalypse Now? :)

[Miniman]

Re: Patch 1.3 rumour discussion!

i thought the patch was out when i logged onto xfire this morn.
13 out of 20 ppl were playing bf2

[MrBrown]

Re: Patch 1.3 rumour discussion!

Why do kits linger for 30 or so seconds after a player dies? Surely it's just as ridiculous to completely change your "training", uniform, and job function by clicking G. That is changing your function by clicking a button is it not?

I didn't mean "unrealistic". I mean: If the developers intended to force you to rotate the squadleader to be more efficient, there would have been no reason for them to delete the squad's orders while rotating. That's a clear indicator for "unintended".

The commander is still talking to the squad leader, just one that got promoted when the other one died. Nothing is damaged, no one has any real rank, or responsibility, it's a game. You are playing squadleader, you are not a squadleader, see the difference?

Well if you leave you don't hear the squad until you join again. You might miss something important. Visual orders could help as you can see them all the time even if you overheard something, but that's rendered pretty useless by squadhopping. If they had planned this stile of gameplay, they would have given us a button to transfer leadership to the next person (or do that automatically) instead of forcing us to leave and join with all these stupid little side-effects.

I (as you imply by capitalizing you're) am never screwed. I can play the game, and deal with tactics like squadhopping, dolphindiving, bunnyhopping, etc. They don't bother me because I have the inclination to be better than them creators intent or not. And since as I have already said, there is a command to divide and form multipule squads, and they made it so you could do this, and no, it isn't an accidental side effect of the programming.

Well you actually can still split your squad even if squadhopping was removed. The leave/join/create buttons are supposed to be disabled while dead only. So this is in no way an indicator for squadhopping being intended. People splitting up are not my problem anyway, it's when dozens of people suddenly spawn at some SL near the enemy's HQ and leave the squad right afterwards, bypassing the 6 member squadlimit by exploiting the squad system.

If the situation dictates, I'll rotate, but mostly I try to keep the position incase the aforemention nooblet gets it, it can halt momentum, and I likie being able to talk to the commander to get the big picture.

LOL it's so obvious that it would be more convenient if you could STAY squadleader and keep talking with the commander for the whole round instead. The spawnpoint could be transferred to the "co-leader" as long as you are dead instead of that dull rotation thing.

[DrJambo]

Re: Squad hopping to be gone in 1.3?

Terrorser, you might think it's "cute" or something writing posts that make no sence. Sorry if english is your second language... but it needs a lot of work. You'd prolly be better off using babelfish or something. You're also kinda... um, how to say it diplomaticly? Ya can't. Yer an idiot.

Not meant as a flame but it might be advisable to check your own English before calling someone else an idiot for poor spelling/grammar (although I agree his was poor!). Sorry for griping at you, but here's just a few examples of words I commonly see you get wrong:

Consideration (consiteration)
Appreciation (apresiation)
Kind of (kinda)
You're (yer)
Probably (prolly)
Diplomatically (diplomaticly)
Technically (technicly)
Sense (sence)
Surprise (suprise)
Pretty (perty)
Controversial (contravertial)
Cries (crys)
Academic (achademic)

It's almost like you're spelling phonetically and I imagine that things like "perty" may be a local colloquialism for you..

Anyway, on-topic, although it doesn't massively bother me the way it currently is, I think "fixing" squadhopping will be beneficial in the long run to how the game might have been intended to be played.