Project Reality Forums

There are 3 caches on the map at a time, this is changing to 2 according to .86 changelog.

Blue diamond = Bluefor have a marker showing its location within 140m accuracy

purple shield = Undiscovered cache

Blufor can destroy ANY of the 3 active caches on the map and get full credit.

The cache locations are random afaik, from a selection of around 300 locations on the map.

Sometimes people are lucky and happen to stumble on an unmarked cache. You still get the same "Weapon cache 1 of 10 destroyed" whether the cache is blue / purple / totally unmarked or not.

There should be 3 visible cache to the U.S (the blue ones) at max and the Insurgents can have more marked as purple on their maps.

dhl1986 wrote:also, a scenario i couldn't help but think of.... what's to stop a player on the US side switching teams, making a quick note of the cache locations, and then switching back?

nothing, thats why only 3 (or 2 in .86) caches are shown at a time.

as an Admin, I do keep an eye out for those kind of people.

Its more common and harder to find som1 who is on teamspeak/whatever with a mate on the insurgent team. But tbh, I don't think this happens too much.

If undiscovered caches start going down very quickly, the admin will realise whats happening and start the hunt.

i've played as US forces a few times where our squad will luckily stumble upon a unmarked cache. its an easy kill.
sometimes though, i see US forces players looking for a lucky chance to find a unmarked cache. i think that waste resources

Depends, there are some spots where a couple of caches spawn near each other, so checking those can net some cache kills. Also, even if people do it now, it's not as bad as it used to be. Back in the earlier days of Basrah someone could teamswitch at the start of the round, take a screenshot and know the location of -all- the caches.

Remember to not confuse the spawn points with Caches.

Only this is a cache:


Anything else is not a cache, and will not be blown up.

once I was playing insurgency... my team was so fast that we destroyed 5 out of 10 caches bfore they were even discovered...

Meza82 wrote:i've played as US forces a few times where our squad will luckily stumble upon a unmarked cache. its an easy kill.
sometimes though, i see US forces players looking for a lucky chance to find a unmarked cache. i think that waste resources

you should have seen teh good old days when all the caches spawned at once


"Lets do a sweep of the village" and so on

I loved it, but it was so easily exploitable

Unmarked caches are there - they just aren't marked. Once a cache is destroyed, the next one seems to be chosen randomly from already randomly placed caches (at the beginning of the round).

On Ramiel the other day, I led a squad the the Northeast (A1 area) and headed west. At the last checked building, we found a cache (that wasn't on the map). Then we head south to known caches.

Anyway, don't waste time looking for caches without markers unless there are no markers. In that case, find the Insurgents. They will either be near a cache, or a hideout.

It's easier to destroy a bad-defended cache than a cache that isn't defended. Even if it isn't or is marked.

Rockets flying from windows of a building are often signs of a cache in it.

Last night I was team switched by Autobalance from insurgent to infidel luckily I don't like any form of cheating and I have real bad memory but it is a danger. This kind of stuff also keeps me away from mumble until it is sorted out so no accidental info reaches enemy ears.
When I play insurgent I try and get the squad to hang out in a neighbouring building and to hold fire until the infidels are ontop of us, but of course it can be a bit 'boring' like that!
Fun versus tactics I guess, where as insurgents is a great oppurtunity to be a bit silly and let your hair down!