04/20/2025
General:
  • General system stability improvements to enhance the user's experience.

PUBG:
  • Fixed potential Aimbot/Magnet Triggerbot snapping
  • Aimbot/Magnet Triggerbot smoothness improvements
  • Added a "Tracking Gain" option for Aimbot and Magnet Triggerbot, which helps to track moving players better rather than lagging behind. Default is 0.5, set to 0 to disable and revert to the classic aimbot
  • Prediction improvements

CS2:
  • Fixed potential Aimbot/Magnet Triggerbot snapping
  • Aimbot/Magnet Triggerbot speed is now always the same regardless of target FPS, even with tracking gain
  • Aimbot/Magnet Triggerbot smoothness improvements
NOTE: Tracking gain 0.5 and tracking damp 0.7 are now the default values. It's highly recommend you start off with these values after this update!
04/16/2025
General:
  • General system stability improvements to enhance the user's experience.

Apex Legends:
  • Updated for the newest game version
04/15/2025
General:
  • General system stability improvements to enhance the user's experience.

PUBG:
  • Updated for the newest game version
04/12/2025
General:
  • General system stability improvements to enhance the user's experience.

Apex Legends:
  • Fixed potential Aimbot/Magnet Triggerbot snapping with memwrite mouse simulation mode
  • Aimbot/Magnet Triggerbot speed is now always the same regardless of target FPS, even with tracking gain
  • Aimbot/Magnet Triggerbot smoothness improvements
  • Removed Aimbot/Magnet Triggerbot recoil scale options. Setting this to anything other than 1 had the effect of Aimbot/Magnet Triggerbot aiming above or below people
NOTE: Tracking gain 0.5 and tracking damp 0.7 are now the default values. It's highly recommend you start off with these values after this update!
04/10/2025
General:
  • General system stability improvements to enhance the user's experience.

DMA Loader:
  • Changed the way the "winlogen.exe has an invalid session ID" warning works. If this warning occurs, there's now still a chance that key states work properly if the winlogon.exe session ID is 1 (which it is in 99% of cases)