fabioxxxx wrote:dude haha "realistic" cache defence is not a very common tactic in real world ... once discovered they will not stay there defending something they know will be hammered by jets artillery and heavy vehicles...
take lashkar valley for example, most caches are in the open once blufor set up mortars you are done for. You need to stay close to the revealed cache , the fox hole is the only defence against mortars .
I agree that it isn't very realistic that insurgents will place a lot of men on one static position that is already engaged and dig in.
It's even more unrealistic that insurgents would leave there caches in an open place so I wonder why these cache locations are made in the first place. they would place them under there sofa or something
not visible in a field where Air recon can spot it.
even insurgents would dig down there weapons underground, place them in different buildings or disguise it as something common.
Years ago I thought it was exiting to go on unknown cache hunt as blu-for but today it feels more like I'm cheating when i find one and take it out, so id like to see the mod that's already made where 1 cache is in play at a time instead of 2 (forgot the name of it) as the standard.
If caches where in buildings and 32 insurgents where defending it it would mean that 1 tank couldn't take it out (unless if the building is destroy-able), and a coordinated attack would be necessary from the blu-for.
it would also remove the "why did you spawn on unknown you *****" behavior, that happens at-least a few times every round.
guilty as charged ..
played Iron Ridge INS , 2 caches on the forest , mortar fire starts you run away from the cache or stay on the cache holding your **** to be hit by mortar fire...