Project Reality Forums

Description:
We were firing directly at the known cashe as all the defenders died. After a few rounds the cashe went down and I was punished as a traitor.
Steps to Reproduce:
Set up mortars, fire at the - preferably exposed - cashe.
Screenshots

^it's only the console log
Tested On:
*NwA* UK Reality Mixed Server
Al Basrah insurgency Std (64) layout

I think this may be an intended bug, to stop insurgents/taliban from just constantly mortar spamming their own cache, meaning that the blufor couldn't get to the cache (and without repercussion)

Psyrus wrote:I think this may be an intended bug, to stop insurgents/taliban from just constantly mortar spamming their own cache, meaning that the blufor couldn't get to the cache (and without repercussion)

I agree, it would be a annoying chore for the BLUFOR to have to search for the enemy mortars and neutralize them before approaching a cache if the OPFOR were constantly mortaring their own caches.

Note: Do not fire at the object you are supposed to protect with explosives

Seems like a good way to handle things.

I agree that mortars should be able to destroy own cache to prevent spam on cache position, but the point Moon tried to make is there is no information on change and it wasn't like that earlier. ;] So would be nice to have clarification and test if it's both side or only insurgent mortars, if Blufor can get caches it would be very harmful for gameplay. Also Militia have mortars same as blufor so it would be nice to see if they can destroy caches.

Shooting at your own cache....and you are suprised what happened....

iirc the mortars do very little damage to caches, but eventually will destroy them. The problem here is that the Afghan statics are slightly penetrable, which is why on this particular map the cache gets destroyed this way after a few minutes of shelling.

but moral of the day is still - don't shoot your own cache.

[R-DEV]Rudd wrote:Shooting at your own cache....and you are suprised what happened....

I don't think someone is surprised here that they destroy cache, but people are surprised that it's now possible because it weren't. So it was "silently" changed in 0.96 or 0.97? If so it would be nice to mention it - it's very reasonable and gameplay enhancing change. Also does it mean that we can destroy enemy cache by firing mortars on it? I hope not.

[R-DEV]Rudd wrote:iirc the mortars do very little damage to caches, but eventually will destroy them.

I checked the BR file. The cashe took 1 (one) direct hit from mortars (round exploded on it). No hits anywhere near it prior to this point, no incendiary/c4/rpg/whatever. After the hit cashe exploded right away. Hardly "very little damage".
We took a full squad of brits at the same time who were about to burn it anyway. ;>

Certainly worth blufor raining mortars on a cache till friendlies arrive.

Lord Jesus wrote:I agree, it would be a annoying chore for the BLUFOR to have to search for the enemy mortars and neutralize them before approaching a cache if the OPFOR were constantly mortaring their own caches.

Well just try to shoot on your own cashe and soon you will see that you have at least over 9000 teamkills. And that makes constant mortaring your own cashe impossible In addition BLUFOR can mortar insurgents cashe gaining not only kills but also destroying the cashe.

qubolo wrote:Well just try to shoot on your own cashe and soon you will see that you have at least over 9000 teamkills. And that makes constant mortaring your own cashe impossible In addition BLUFOR can mortar insurgents cashe gaining not only kills but also destroying the cashe.

The difference is information, OPFOR knows the precise position of the cache. BLUFOR does not, unless they know it's on a rooftop and which building, their mortars are not always gonna hit the right spot to destroy the cache. When the OPFOR mortars their own cache, they have a marker on the map and usually aim for that. Which leads to dead accurate shots that really hurt the cache if it's exposed.

I srsly start to feel like it's feedback section.

I merely reported what seemed to me to be a bug : a fact that a single direct hit from mortar can take down a cashe. Sure, it's hard to achieve but still, supposedly, a bug. Only exposed cashes seem to be vulnerable and I've failed so far to test if BLUFOR mortars can destroy cashes as well.
Furthermore I'd appreciate refraining from posting how it affects gameplay/how supposedly dumb it is to mortar own cashe. I'd really be glad, on the other hand, to know if it's considered a bug or is an intentional change.