SilverWolf4 12 Posted July 31, 2012 (edited) I'm not sure if this should be directed at the BattleEye Devs instead, but here goes:1. Include Player (GUID) killed Player (GUID) in the server logs.2. Include murders in the match statistics page.Currently, the only way to ban a hacker is if the server catches them running a script. Give the admins the power to defend their own servers FFS. Edited July 31, 2012 by SilverWolf4 9 Share this post Link to post Share on other sites
insidejob 1 Posted July 31, 2012 Agreed...Too many hacker experiences the past few days Share this post Link to post Share on other sites
kylej007 0 Posted July 31, 2012 10/10this needs to happen Share this post Link to post Share on other sites
Spookz0r 12 Posted July 31, 2012 Hackers can spoof GUID meaning you might ban someone elses account and not the hacker. Share this post Link to post Share on other sites
SilverWolf4 12 Posted July 31, 2012 Hackers can spoof GUID meaning you might ban someone elses account and not the hacker.Great, so we have no effective way of ridding our servers of them? Share this post Link to post Share on other sites
Guest Posted July 31, 2012 This is helpful, but if the hacker simply runs a bypass and then uses kill commands to kill players, it won't log anything. Share this post Link to post Share on other sites
GhostSe7en 20 Posted July 31, 2012 This is helpful, but if the hacker simply runs a bypass and then uses kill commands to kill players, it won't log anything.This is correct, BattleEye isn't REALLY the issue as it will stop most script kiddies from pooping on players chests. The real issue is the ability to bypass BE protection, in which case not much if anything will show up on logs.It is the pain SA's live with everyday. Share this post Link to post Share on other sites