Do not spawn unknown caches near enemy FOB

[Jorgee!]

Could it be possible to check in a 300mt radius before spawning a cache?

There were lots of times when unknown spawns next to a full enemy FOB, then known gets dstroyed,.

[Outlawz7]

And where will caches spawn if blufor manages to block most of the map by building fobs in strategic spots?

[C@$PER]

In a random spot like it does already. Unknown/secondary caches also seem pointless and are vulnerable to cheaters. One cache at a time can be balanced.

[Murphy]

Those "random spots" are actually hand picked by the mapper, there are only so many locations that are logical for a cache.

[Jorgee!]

And where will caches spawn if blufor manages to block most of the map by building fobs in strategic spots?

In 1km maps the distance could be 100 mts.
In 2km 150 mts and in 4km maps 300mts

Obviously, mapper should set various cache points in order to take this into account.

The blufor can only spawn 6 fobs and caches are 4 and are not repeated. So mapper should at least put 10 caches separated by 100 meters each or add more than 10, like 20 or 25 positions.
i think that would do.

Another option could be to destroy enemy fobs under 100 mts of cache on spawn, but that is not a very good solution.

You could also program this to check if there is a position that fulfills this requirement, and spawn the cache there. Otherwise, proceed as usual and that cache would be a lost one,but game would continue normally