Description:
Pretty straightfoward. Was defending a cache last night on Kokan when we had a JDAM dropped on our heads. The cache was on the bottom floor of the compound completley covered and with full health but it was still destroyed (along with all my poor comrades lol)
Steps to Reproduce:
1.Request JDAM
2.Enjoy the show
Tested On:
Ive also tested this on an emptied online server. During my test however it did not completley destroy the cache but severley damaged it as shown in this photo:
Silly_Savage wrote:Well, it is a 2,000lb bomb exploding. I'd it expect it to level that compound and anything inside of it.
Yes but a few versions ago it was changed such that areas attacks (mortars) didn't kill caches... I guess that no longer applies with the player controlled arty now not damaging caches?
pretty sure this is not intended. this is not about realism but about gameplay. would suck as hell if u can just wipe a cache out by simply jdaming the area since the mapmarkers are more accurate and the amount of caches has already been decreased
It's not like you can call down a JDAM every other minute. 1hr cooldown + initial cooldown is totally fair. So you could use it to destroy 1, maybe 2 caches if the round is slow.
Also it doesnt always destroy the cache. I was playing as insurgenct the other day and JDAM blasted the village with everyone in it, but the cache survived. It's NOT overpowered as it is, if it destroys a cache every now and then.
Your missing the point. A few releases back it was changed so that all forms of fire support (Mortars, Arty and JDAM) could not damage the cache. This was nice cause it meant that you still had a chance to defend it after being blown to hell.
Now im thinking its a bug because the Devs never said that this was changed and there was nothing about it in the changelogs.
ADF_Shadow wrote:Your missing the point. A few releases back it was changed so that all forms of fire support (Mortars, Arty and JDAM) could not damage the cache. This was nice cause it meant that you still had a chance to defend it after being blown to hell.
Now im thinking its a bug because the Devs never said that this was changed and there was nothing about it in the changelogs.
I belive it has something to do with the JDAM being changed so that it kills anything regardless of cover at certain radius(75m?). I think this part of damage may kill cashes (and it couldn't even have been tested before because no ins maps had JDAM requestable).
I don't consider it a bug-bug, JDAM has 1 hour cooldown and, if I'm correct, it has to be called precisely on the cashe location to the effect to occur.
This is totally fine and probably not a bug. JDAMS only happen once a round - something this rare can be realistic.
--- currently reduced activity --- Thanks to [R-MOD]IINoddyII for the signature! _____________________________ Propriety is an adequate basis for behavior towards strangers, honesty is the only respectful way to treat friends.
You can not call them in all the time, its on one map and i don't remember them saying they stopped jdams from detroying caches. I know they stop mortars and arty but not a jdam.
I don't see the problem with a jdam destorying the cache it has a huge cool downtimer and warmup timer you can only really use it once per game.
If you can give a good reason why or an example of how this ruins gameplay im listening.
ive made the same experience, but it doesnt work with every JDAM. we once put a JDAM on a damaged cellar cache on Kokan and it got destroyed by it. the next day or so we put a JDAM on some other cache on Kokan, the one close to the Taliban vehicle depot, and it survived. it didnt even take proper damage and it was located in a small hut. see the difference?
A few releases ago they only stopped Mortars and Field Artillery from damaging caches. The reason you may think this is a bug is because Kokan is the first and only Insurgent map with JDAM's as an Area Attack.
This is how JDAM's in PR work: if something/someone is within direct line of sight of the impact for up to 300m(?) you are hurt/wounded/killed depending on distance from blast. This is if you are in the open/out of cover.
However, if you are within a certain distance of the point of impact (70m iirc?) it does not matter if you are in cover or not. The damage goes through any object/terrain within this distance to simulate the tremendous concussion from a munition that size. That is why JDAM's will kill you if one hits the roof of a Kashan bunker while you're hiding inside, or why an indoor or underground cache will get destroyed if it is close enough to the JDAM impact.
Again, this is not a bug and is perfectly fine from both a gameplay and- as several people pointed out- a realism aspect in my opinion. They have a long reload and are only on one map.
In fact, I think they should be available on several other maps like Lashkar and Korengal cause of some of those imfamous cave caches.
