[Problem]How to deal with Ghosting in server?

[Jolly]

Well, basicaly
PR is a game with teamwork, and those guys in game should destory enemy's fob and cache their own.
But somehow, we've found some very guys who maybe ghosting during game, which makes those players unpleasant and ruined game play.
We find it hard to get any evidence of Ghosting.

Any server admin can share us some experiences about how to find ghosting ??Thanks a lot!

[WeeD-KilleR]

There is really no way to tell if someone is ghosting and therefore no way to bust them. The only thing you could do to reduce ghosting is to tell clans they should play on the same site. BUT this could cause a heavy unbalanced teams.

[LieutenantNessie]

What I remember you can check if 2 person on the opposite sides have same IP's, otherwise it's pretty hard to detect

[killonsight95]

1) If you have the same IP, be on the same team
2) If a squad finds say 3-4 caches in a row fairly easily, write their names down on paper, then use the BF2 replay of the game and follow them around for a bit and see if they search at all or go straight for it.

[KillJoy[Fr]]

I got team switch on time on the CIA servers , 2mins later i got kicked by an admin for ghosting this is so fucking disgusting beause i always play legit

[SGT.MARCO]

USE the DB mod, no unknown cache, no ghosting Problem solved

[saXoni]

Just don't play insurgency.

;1762909']I got team switch on time on the CIA servers , 2mins later i got kicked by an admin for ghosting this is so fucking disgusting beause i always play legit

Take it to their forums.

[Kain888]

It's from hard to impossible. The best way to avoid ghosting destroying gameplay is fine community or not playing INS at all (although ghosthing is massive problem on other modes, CnC for example, less on AAS, but still).

[SmoothIsFast6]

best way to fix insurgency is to have a ammo truck be able to load up the cache and drive it around and/or drop it off in a building

problem solved

[saXoni]

best way to fix insurgency is to have a ammo truck be able to load up the cache and drive it around and/or drop it off in a building

problem solved

Drive it in full speed out of the map and behind a slope so the opposing team won't find it.

Problem solved.

[IINoddyII]

Not easy to catch Jolly.

As others have said - duplicate IP's need to be on the same team. Move them, if they swap back kick them.

Look for lone wolfs who have a habit of finding unknown caches where nobody has spawned on them. Whilst they may be just good ninjas... They aren't playing in a teamwork manner and you could do without on your server.

[Jolly]

Using 3rd communication software....Cheating
Can PB do something?

[IINoddyII]

?

You mean and external voip program?

Then no.

It's usually just a case that you build up enough evidence over a period to put it beyond a doubt in your mind... or at least 99% comfortable.


ETA: - you need to get your server licence owner to add you the list as a server admin. There is a separate sub-forum where all sorts of information you might find useful is shared

[Jolly]

?


ETA: - you need to get your server licence owner to add you the list as a server admin. There is a separate sub-forum where all sorts of information you might find useful is shared

Ok, I'll tell him

Thanks mate, really appreciate your help!

[Jolly]

?

You mean and external voip program?

Then no.

Yeah, external voip program

Maybe I should put a spy and see if they cheated.

[cyprezz]

I bet most ghosting involve one person (greifer) switching from insurgency to BLUFOR. Once the cache is destroyed, they switch back to insurgency to locate the cache and then switch back to the BLUFOR to destroy it again. It's pretty obvious that this is done many times when you check the team player count, you will often see 31 players on the insurgency side and 33 on the BLUFOR side.

I have suggested in the past to include the player name to the yellow text that show up when the cache is destroyed. Often, if the same name keeps showing up after several unknown cache has been destroyed, it's pretty obvious what's going on.

In addition, I recently read that major changes are going to take place soon regarding the new patch release. Instead of two cache at one time, there will be one, which in my opinion is a smart move by the devs. It makes it harder for greifers to ghost alone and destroyed an undefended cache when there is none.

[IINoddyII]

I think one of the servers also has a script which puts up a message whenever somebody teamswitches?

[Vista]

Kind of easy to tell if they're ghosting.

So, if a person with a combat engineer kit asks do get dropped on a precise grid with an unknown there, and has gotten few other caches, there's like 80% chance he's ghosting.

[PLODDITHANLEY]

1. As server admin be insurgent and watch squads.

2. Check on battle recorder that if they went straight to a cache location without checking ANYWHERE else then they are cheating.

3. Produce evidence with Battlerecorder check with others admins and ban them.

[Hfett]

We managed to get a ghosting dude on our server's Twice.

First time there was no rule against it, and it was back when the day's where rally point's would not expire.

I started to notice a lot of my clan rally point's disapearing magicaly.

And there was a guy away on my team from a rival clan.
And his clan squad was on the other team.

So me and a mate changed accounts and stayed on TS with one on each team, watching what this particulary clan was doing ingame and where our clan was putting their Rp's.

We noticed that as soon as one of our clan mate's placed a rally point, that rival clan automatcaly marked a "attack to this position or move to this position" to our RP's.

Since i was admin of that server, we implemented a rule against it and it stoped, cause they didnt want to get their clan exposed, cause it was not the whole clan doing it but just a small group with bad intentions and hate for our clan.

Then, much time latter, on insurgency, we came against a particular dude who had the same IP of a iddle player.

One admin joined his squad with a secondary account (to make sure he would not suspect) and he filmed the whole match.

The dude was marking the caches on exacly positions before ever going to the place to see where they are.

It was prety obvious and after we banned him he assumed, and now we know that he play's fair.

But, now what i see a lot of dude's doing is changing teams on the begining of the round, placing a firebase exacly near one of the not revealed cache's and pretending that they did not saw, and after a few minutes of the match they go to the not revealed cache by "luck".

That case is the worse since we cannot say for sure if he did it on purpose or not.


With DB changes the insurgency improved a lot


Also, like someone else's said, battle recorder, one squad going exacly to the cache every time without going anywhere else = ghosting