Project Reality Forums

Happend on chicago hardocore the other day 3 caches were in play.


CACHE LOCATIONS: A5,H7,C4 (theres alot of people on that cachce you can see the tip of the marker)

myles wrote:Happend on chicago hardocore the other day 3 caches were in play.


CACHE LOCATIONS: A5,H7,C4 (theres alot of people on that cachce you can see the tip of the marker)

Check if that cache was active. Sometimes they spawn and die immediately. Especially in G7 region.

ytman wrote:Check if that cache was active. Sometimes they spawn and die immediately. Especially in G7 region.

I can hardley check it now but as i do rcall i rember the cache in G7 was active as i spawned in on it

That H7 cache is a glitch cache, destroyed at round start so Insurgents only have 60 tickets instead, its always that cache and the defend marker will be there all game. Happens on Koregal sometimes too not sure which cache but known issue as far as i know.

This issue struck hard a few nights ago on the same map. 4 caches spawned, 3 in a row and then the last cache spawned in the same area, in the H7/8 area. It was clearly game breaking, as we could not risk going in to defend the last cache due to heavy Canadian presence. Instead it was decided the best tactic would be to draw them away from the area by defending one of the few caches that spawned elsewhere on the map.

I think this issue needs to be seriously looked into as it really ruined a perfectly good game. If it were possible to make the new cache unable to spawn within X distance of an already active one the issue could easily be avoided. As it stands the "randomness" of the spawns seems to randomly favor BluFor. Needless to say someone stumbled upon our unknown cache as it was probably near an enemy FOB.

this is a common prob on insurgency, we had 3 like this on ramiel

It had happend as a few rounds prior to it on Karbala when we were Blufor attacking a known cache and we killed three unknowns in the same area before finally finding the known.