Lorax74

Hi all,

The other day I was playing a few rounds and ran into a rather annoying situation where someone on the opposing team was camped a short distance away from our SL's beacon. It took me three spawns before i finally spotted the player in the prone position near a corner of a building. I chose a new spawn point and went back to clear the surrounding beacon area of said camper.

My question is this: is this considered acceptable keeping in mind that the spawning player has not yet got their bearings straight (especially due to the initial disorientation from the drop pod landing)? I didn't see specific reference to this in the SOPs, if I missed something please provide a link so I may reread it.

Thanks!

BHack

It is considered acceptable because that particular spawn point is voluntarily placed and used.

I think it's sort of lame myself and will destroy the beacon (rather than camp it) at my earliest opportunity.

__________________

Tempus

Spawning on a beacon is like spawning on a SL. You cannot expect protection to be given there. Often, I will hear squadmates report that a beacon is being camped, and our SL will order us to spawn elsewhere.

__________________
Battlefield 2/2142 Game Officer
Contact me with server/player/admin issues.




-- Suits are what you wear when doing things you shouldn’t want to do anyway.

FROM THE TACTICAL GAMER PRIMER.
3) Support game play in a near-simulation environment. Where the focus of play would not be solely on doing what it takes to win, but doing so utilizing real-world combat strategy and tactics rather than leveraging exploits provided to players by the design of the game engine.

experiment626

As a general rule I shoot any beacons I find that are not my own squads, sorry team mates but there is no way to be sure (possible patch in the future?). I have noticed that when we are hard pressed, like on Gibralter, and my squad is trying to retake ruins or some other rear flag, it may seem like we are camping it...we are not, we just can't find the blasted thing and bad guys keep falling on our heads!

__________________

Shiner

I agree the rule clearly states that spawncamping is not allowed because it exploits the lack of situational awareness a spawning player has when reinforcing. The drop-pod clearly provides both awareness and some cover via the dust cloud. I think a good squad member or squad leader knows to report both a "hot" sqaud beacon (engaged enemy contacts in the area) and a "camped" squad beacon (someone is focused on killing drop podders). It is then up to the squad to decide if they want to spawn in there or not.

__________________

Arf

As your drop pod comes in you get a good bird's eye view of where you're about to land so you actually should have a pretty good idea of what you're getting into and where the enemy is.

__________________

Lorax74

Thanks for the replies and information. I had a feeling this was going to be the case and that is fine, next time I'll know better. In my situation, my SL placed the beacon in an out-of-the way place, not near any enemy engagements. The enemy camper (for lack of a better word) seemed to be a lone wolf, but he/she may have had orders to do attack or defend that area, I'll never know.

Kill me once from a drop pod, shame on you. Kill me twice in a row from a drop pod, shame on me.

thanks again.

Maus

I agree that it's a little lame, but I think "spawn denial" is a valid tactic in that situation. It's one thing to sit by a flag and kill spawners instead of trying to cap the location, but quite another to stop reinforcements coming in to an assaulting group.

I can see a case being made for destroying the beacon being an acceptable alternative, but doing so just means the SL will place another. "Beacon camping" I guess is just fine.

__________________
2142: |TG-Irr| Silverfish
BF2: |TG-Irr| Maus

BHack

I agree, sort of. Instead of sitting prone 10 ft away from an enemy beacon, killing people as they hit the ground, why not just destroy the beacon and stop the spawning altogether?

__________________

Ashenhart

I agree with that to a point.. yes it is lame but a squad that is working together.. will quickly figure that out and will spawn elsewhere and come back and kill him.

__________________
Ikariam.com (Alpha) - Ashenhart
TGA-AshenCrystl 80:56| Send Me Goods
TGA-AshenMarble 80:57| Send Me Goods
TGA-AshenWine 79:55| Send Me Goods
TGA-AshenSulfur 79:56| Send Me Goods

BF2142, BF2, PoE2, CoD4, TF2 - |TG-Irr| TG-Ash
WoW - Ashenhart 70 Warlock | Trinitia 70 Paladin | Duenna 61 Hunter | Monalott 61 Warrior

TG WoW Home Page | TG Required Reading | The Irregulars | Irregulars Forum

Maus

Or one of them will get so totally p***ed at being killed on spawn he'll forge a personal vendetta against the guy and vow to knife the blighter before the round is over. Not that you'd ever catch me ignoring my squad like that, no sir! *ahem*

__________________
2142: |TG-Irr| Silverfish
BF2: |TG-Irr| Maus

Dark Viper

The SL should just come in and pick up the beacon right when he lands.

__________________
|TG-33rd|Dark_Viper

DirtyLude

Podding isn't as disorienting as you can see where you are when you are going down and at least be pointed and running in the right direction when you hit, even if you can't see that much.

I called a bunch of people at a squad beacon cuz I couldn't find the damn beacon. I never did find it, but I think they managed to get it under a supply crate where I couldn't see it.

__________________
The Dirty

Prophaniti

The way I see it...if some idiot (or maybe a couple of 'em) is/are willing to drop in on a camped beacon over-and-over again, it is my duty to keep them coming back for more.
That's effectively taking out one (or more) people from attacking/defending elsewhere, thereby giving my team as a whole the upper hand. In addition, it denies the enemy squad the ability to spawn on the SL (who may have wisened up and is running around elsewhere). If the SL is smart, he'll deploy a resupplied beacon and then pick it up again to get rid of the old beacon. If not that smart, I'll capitalize on his lack of forethought.

The only situation I will destroy an enemy beacon is if it's getting too hot for me to handle. All it takes is a SL getting his squad to hold off on respawning until they can all drop in at once. I'm decent, but not that good...

BHack

This is why I think it's lame. Because that statement is false.

The SL cannot place a new beacon while one is already out -- anywhere on the map. Yes, great, I can have my squad spawn at another flag somewhere and not die instantly, except now I've lost all ability to spawn on me or a 'non-instant-death' beacon point.

So you've effectively killed the squad's forward spawn point ability, which sort of reduces the effectiveness of a squad by a factor of 10.

When I'm SLing people complain and say we need to stop spawning there if its hot. I'd rather keep trying with the intent to kill my own beacon before I get gunned down. The other option is to try and fight for your beacon back by spawning far away and mounting an assault on your beacon. I will only do this if I think the time it takes to get back to the beacon is small enough to make it worthwhile. Otherwise you are trading a few tickets for, what could be, a long period of complete squad ineffectiveness.

And you thought being a squad leader was easy!

__________________