Spawning on unknown cache

[Jevski]

Another thing I thing players forget in this new version is, that now the UAV is working. You will never know if you are observed from above.

I do get the idea of one guy spawns on unknown, and very quietly crawls away, without any seeing him. But the problem is, as soon as one guy does it, then 6 or more follow and then this trickle of ins running from the cache will be noticed sooner than later.

I employ many thing to find an unknown, both sound and visual contact.
I have 5.1 headphones, and can hear and pinpoint the location of any vehicle far away. So as soon I hear an car or bike drive somewhere stop for around 2 min then drive off, Ill go and have a look.

Seeing several ins running from a certain direction towards the known or where the action is. I go in that direction and observe some more to pinpoint the excat location.

[sprint113]

Another thing I thing players forget in this new version is, that now the UAV is working. You will never know if you are observed from above.

This. I've commanded only a couple rounds in .96 and at least once every insurgency round I have located an unknown cache with the UAV because 2-3 guys grab RPGs and sit on the cache waiting for vehicles to roll by. 2/3 of the blufor team with armor support closing in on an unknown cache defended by a handful of insurgents, mostly armed with RPGs with no backup spawn points took us tops, 5 min to take down. During that period, I actually hope that we don't get intel so the cache will remain lightly defended.

Oh and everything looks more awesome when viewed in thermals from the UAV.

[Bringerof_D]

;1631543']Last night I found unknown cache all by myself, I saw few guys getting out of the compound with RPGs, went there and found it.

again, easily preventable if players took a second to listen before stepping through a door, vehicles can be heard almost quarter way across any map, footsteps are loud as **** and always take a peak around the corner before stepping out completely.

this is not a problem of spawning at the unknown, its a matter of impatient players. Servers should not enforce that rule as it again more often than not hurts the defenders. there's a reason the devs put two caches on the map, and there's a reason why there is a spawn point on it.

[Jevski]

again, easily preventable if players took a second to listen before stepping through a door, vehicles can be heard almost quarter way across any map, footsteps are loud as **** and always take a peak around the corner before stepping out completely.

You presume, that the guy who took out the cache was
a) driving
b) running around right next door to the cache


As ive said before, as soon as you leave the general area, and when more than 1 player does, it will attract attention towards the direction of the cache. Its just a question of the blurfor to change position every time he sees movement towards the direction they are coming from.

Then next time you "peak" out I will spot you. Its like triangulating a radio signal. You take a bearing from far away, and the more intercepts you pick up, the closer you get to the signal.

And again dont forget the UAV. It cant be heard, nor seen.

[80HD]

Was talking about this on TG last night, what if only the commander could see unknowns?

[Sneak Attack]

I hate it when people spawn on the unknowns. Being on the insurgent side is all about building hideouts. I like to build squads that do nothing but build hideouts. Put down 2 or 3 hideouts for every known cache at a reasonable distance and it makes the team very hard to beat. No or few hideouts right by the cache is a sure way to loose in a short amount of time.

[Dev1200]

TBH, only one cache should spawn at a time.


It's quite easy to feign a cache with ammo boxes and a borrowed RPG kit. What I don't like about that rule is that usually there are roaming squads looking for unknowns. You can't defend it if nobody spawns on it.

However, it's a big debate right now. Don't spawn on cache = They won't find it vs Spawn on cache and defend it from enemies.

[Sidewinder Zulu]

sidewinder, go play on the =]H[= server. u will see how they search every building even if they see one person.

I've played there frequently, and never seen BLUFOR do that.

A BLUFOR squad that searches every nearby building whenever they see an RPG or PKM is wasting their time. If a squad were to see someone enter a building with an AK and then leave with an RPG, then I would say it would be prudent to search the building.
Otherwise it's exposing your squad to unnecesary danger, at least if they're in an urban area, like many insurgency maps are.

[Cassius]

TBH, only one cache should spawn at a time.


It's quite easy to feign a cache with ammo boxes and a borrowed RPG kit. What I don't like about that rule is that usually there are roaming squads looking for unknowns. You can't defend it if nobody spawns on it.

However, it's a big debate right now. Don't spawn on cache = They won't find it vs Spawn on cache and defend it from enemies.

I think the reason 2 caches spawn is that a cache held by 30 insurgents is too hard to take out. However it really depends on the situation. A cache in the open with Tanks and APCs on overwatch might as well have 50 insurgents on it.

[Rissien]

I've played there frequently, and never seen BLUFOR do that.

A BLUFOR squad that searches every nearby building whenever they see an RPG or PKM is wasting their time. If a squad were to see someone enter a building with an AK and then leave with an RPG, then I would say it would be prudent to search the building.
Otherwise it's exposing your squad to unnecesary danger, at least if they're in an urban area, like many insurgency maps are.

You see a rpg and more often than not it is a cache. Only a few spawn off a cache and even fewer are taken away from the caches. Besides clearing them out helps the team by getting rid of any ambushes that could be laid at that same spot to another squad.

[NyteMyre]

Last night on Korengal, there was an unknown cache in the beginning near the US main base.
Half the team spawned on it and we did a ton of damage before they could destroy it.

So it can't always be bad

[Jamaican]

When blufor i see enemy movements as important targets. I dont search buildings ramdomly. I just look for enemy and search that area.

When insurgent i think as if im playing against myself, i stay away from uknown and try to get the blufor attention somewhere else with use of hideouts, ammo boxes and a cache weapon.

I know not everyone plays my way, others may like to search everthing and avoid contacts. But most likely from what ive seen while playing is that when someone sees or hears the enemy they go towards them. So id say its better to stay of uknowns for now.

[Jevski]

Last night on Korengal, there was an unknown cache in the beginning near the US main base.
Half the team spawned on it and we did a ton of damage before they could destroy it.

So it can't always be bad

I agree i depends on the map, and we also react differently in regards to this on the server.
Korengal is one of the most difficult maps in regards to movement for bluefor. And there is much cover for the Ins to move around in.

But take Basrah, Fallujah is an entirely different thing. Here spawning on an unknown, will 9 out of 10 be seen either by a lone soldier or the UAV.