Project Reality Forums

Hi, guys.
This suggestion is not for DEVs. It is for server admins.
As you know, there are a problem with ghosting and it is not solved yet. And if there was no ghosting, the unknown caches are easy to find and destroy.
But what is the purpose of caches? Like the AAS capping zones, they are for concentrating teams in one location for the best awesome fights. And what happens if unknown cache is destroyed? Yep, no fun at all.
Some of you can say that insurgents must defend all of the caches, but what about admins kicking people for spawning at unknowns?

So, I want to suggest a public server rule for not destroying unknown caches even if you found it. The punishment is kick/ban.

I think, this will solve the major insurgency gameplay issue.
Thank you.

I understand what you are saying completely but I cant agree with this what you are proposing. The reason is simple - it cant be real. You're saying that we should kick or ban people if they find or destroy unknown/undefended cache, but as soon as someone finds it and let others in team know about it, its not unknown anymore is it? It shows as unknown to defending team sure but attacking team has intel where cache is. So whats up with this rule should we kick or ban the whole attacking team?
I appreciate your suggestion but I think that you see too that this will not work right. For very same and few other reasons I removed insurgency from our servers and until those are fixed I don't want to get them back unless people want it back.

MaSSive wrote:but as soon as someone finds it and let others in team know about it, its not unknown anymore is it? It shows as unknown to defending team sure but attacking team has intel where cache is.

We have an ingame intel system. The system shows you if the cache is known or it is not. So, if it is not known, you are not allowed to destroy it. Simple.

But its not that simple. We cant force people to go "blind" on such obvious thing. If someone has found it he will pass the info on his team and in that point it is not unknown anymore even if ingame system is not showing it it can be marked on map as enemy objective.

You're saying that we should forbid destroying that cache until it gets known by ingame system, but as attacking team knows where cache is they will constantly send forces in that area and plan assault on it. This will cause them to possibly lose large amount of tickets for nothing and will probably cause some people that do not know about this rule to get kicked or banned. It will only bring more problems as I can see it. More bad than good.
I'm sorry but I cant force this rule but I'm aware of issues that you're pointing at.

MaSSive wrote:But its not that simple.

I understand. Yes, this hard, but possible.

What just removing the damn unknown? Just having 2 knowns instead, that would be simplier I think. Because ghosting IS a problem, and admins kicking because you spawn at an unknown is even easier for the ghosters.

Another solution would be to just get the insurgent team organized enough to defend both caches. Whether or not they show up in-game as known or unknown.

Spawning at the unknown should not be punished, it should be encouraged. It's the only way to stop ghosters and unknown-hunter squads.. to have a defending force ready for them.

Hard to realize man.
Not every server has enough admin to control it.

PS:Experienced players know where the cache probably is, which makes it harder for insurgents to defend caches. Telling the truth, I dont know how to figure it out too.

PS:Experienced players know where the cache probably is, which makes it harder for insurgents to defend caches. Telling the truth, I dont know how to figure it out too.

just wondering that how many different places there are for caches?
is there any change to update those locations with patch?from server side?
so there would be alternative versions of a cache locations.

so in one server could have different locations than some another server.

Unrealistic, stupid and its not going to work. Someone finds unknown and plants C4 on it. As soon as its known they will push button and boomb.

Ok. How about this:

Step 1: round start, one unknown cache becomes known to blufor after 300sec.
Step 2: BluFor get 50 intel points and unknown cache spawns. Insurgents get information about new cache location
Step 3: after 300 sec. unknown cache becomes known on insurgents map.
Step 4: after another 300 sec. BluFor get information about new known cache.

In this case ghosting is not really possible and insurgents get enough time to prepare defences (time intervals can be changed) .

maarit wrote:just wondering that how many different places there are for caches?
is there any change to update those locations with patch?from server side?
so there would be alternative versions of a cache locations.

so in one server could have different locations than some another server.

There are lots of places for caches, and those location won't change.(at least in chinese server)
Alternative INS does exist but it's for different vehicle layout.

'[md wrote:MadMak[rus];1706416']Ok. How about this:

Step 1: round start, one unknown cache becomes known to blufor after 300sec.
Step 2: BluFor get 50 intel points and unknown cache spawns. Insurgents get information about new cache location
Step 3: after 300 sec. unknown cache becomes known on insurgents map.
Step 4: after another 300 sec. BluFor get information about new known cache.

In this case ghosting is not really possible and insurgents get enough time to prepare defences (time intervals can be changed) .

Step2, I dont know it's meaning, Would you plz explain more?

Jolly wrote:Step2, I dont know it's meaning, Would you plz explain more?

Second cache spawn only when BluFor earn 50 intel points. Till that time there is only 1 cache on the map.

It wont work MadMak...by that system all blufor has to do, is to wait in main for cache to show up on their map, and to attack it. So they wait 6*300=1800sec or 30 minutes and all caches become known. That is bad.
By system we have now they need to kill or arrest enough insurgents to gain intel points for cache to become known. So, yeah no free intel

'[md wrote:MadMak[rus];1706416']Ok. How about this:

Step 1: round start, one unknown cache becomes known to blufor after 300sec.
Step 2: BluFor get 50 intel points and unknown cache spawns. Insurgents get information about new cache location
Step 3: after 300 sec. unknown cache becomes known on insurgents map.
Step 4: after another 300 sec. BluFor get information about new known cache.

In this case ghosting is not really possible and insurgents get enough time to prepare defences (time intervals can be changed) .

*Cough* Take it over here *Cough*

'[md wrote:MadMak[rus];1706434']Second cache spawn only when BluFor earn 50 intel points. Till that time there is only 1 cache on the map.

So ,no insurgent spawn at unknown till it appear?This might be good, But 300 sec for insurgent to prepare, that's a litte be tight isn't it?

Remove Insurgency from Project Reality, as it's unrealistic and ridiculous.

MaSSive wrote:6*300=1800sec or 30 minutes and all caches become known.

Nope, cache spawns only when blufor get 50 intel points. The approximate time is needed for insurgents to be ready for defending the new cache. Blufor need to do something to get intel points, not just wait at main or the new cache will not spawn.
I've wrote the just an approximate time.

Anyway, something must be done with the current system.