• MxReps
    User
    Member since 6 years ago
    Reasons for reporting UTDP

    Aimbot, ESP/Wallhack

    Battlereports
    Report #1
    Additional Information

    Giving as much info as I can. I'll let you be the judge of this...

    A few regulars on the other team mentioned this player is sus and a potential bot. I immediatley
    became suspicious myself when he gained 18 kills two minutes into the game so decided to spectate and see for
    myself. To no surprise I see a player literally locking onto every player of the opposite team. Never once was
    there an adjustments/drag to his aiming, its always spot on even when enemies are moving, far away, or behind obstacles.
    It looks entirely automated. Later into the game after I call him out to see his response I immedeatly see a
    drastic change in his game play almost as if there isn't an aim assist in use, shocker... Now he's aiming like a human player,
    never spot on 100% and locked onto someone each time later in the video.

    Video link: https://www.youtube.com/watch?v=TU8htDt5JW4

    *One part of the video you'll notice after his triple kill he has his m9 pistol targeted behind a wall on someone not spotted
    on the map, tracking them then almost instakills them immediately after showing himself. Another aiming through broken glass
    you can't even see through

    Also BF4DB screenshot...
    stats at the time of the report:  https://gyazo.com/e7b48eab8424e1c0616291fbf643c2c8  (only 3 weapons)

    stats a few hours later: https://gyazo.com/1af0d665d4fce4e7352621cb0f2354b0  (multiple random weapons)

    looks like a stat reset to fabricate overall stats...



    https://gyazo.com/65fa06f9d89f6ad767374d2bd814af2d < updated stats after the name change 2 days later

  • neonardo1
    Retired Staff
    Member since 7 years ago

    Good catch, definite aimbot.

  • neonardo1
    Retired Staff
    Member since 7 years ago

    Banned!

    This player has been banned by BF4DB and any game server protected by our anti-cheat plugin

    Reason: Aimbot

    This thread is now closed

    JXPR Battlelog Ban Policy