May 2019 - last edited May 2019 by EA_Barry
The player with the game tag [Removed - Admin.] is using a speed hack and appears to be in the game twice as you can see from one of the attached photos. This player has been reported before by others and I have done so as well. The other attached photo shows him harassing other players. It's bad enough that TF1 servers can be crashed on demand by a script kiddie (I suspect this guy is the one) but even when they don't crash, this bad guy makes it impossible to enjoy the game we paid good money for. Please stop these unacceptable behaviors from this person
May 2019
Please do not name any player you suspect may be cheating, this is called "Naming and Shaming" and is not allowed on Answers HQ.
If you suspect a player may be playing unfairly you can use the steps detailed at the following link to report them.
https://help.ea.com/en-us/help/faq/report-players-for-cheating-abuse-and-harassment/
Thanks.
May 2019
The hacker does well, smarter from EA developers. I hope that hackers hack all EA servers and close EA stores
May 2019
Barry,
I've uploaded photographic evidence of this person hacking and cheating. How about doing something about Him/Her ruining a game I paid good money for instead of dinging me for naming and shaming. He/she deserves to be named and shamed and you at EA are complicit as you've done nothing about it. I've followed the procedures you've outlined numerous times for his and other (although probably just the same person with a different name) cheater and NOTHING HAPPENS. Please stop covering for these lowlifes and do something to STOP them instead!
May 2019
Here we go again. Someone being accused of name shaming....I just don't get it?
The hackers are there, in game every single day running scripts to kill what's left of Titanfall.
EA and everyone else refuses to do anything and just let the hackers run free !!
'Name shaming is not allowed' !!! Either is hacking, why can't you get rid of them Barry ? I know this forum does not go any higher up than your eyes and the other 'Community Managers' , otherwise this issue would have been solved months ago.