exi

Head Moderator
Head Moderator
Head Moderator
Head Moderator
Status
Offline
Joined
Oct 22, 2024
Messages
127
Reaction score
81
Hi everyone! Continuing to fill the section with good sources of cheats for Valorant. Today I want to share with you an improved aimbot source from berk000x. I already uploaded it before, you can search for the topic. Even original source is undetect, so for now this cheat also not detected by anticheat, can be used safely. Hack is tested, no viruses, especially since this is source code, you can edit and use it as you want. Author: rhaym.

hXNbQ6a.jpeg

View hidden content is available for registered users!


What was changed?

  1. Rewritten in another language. Was C#, now cheat is on C++.
  2. Code fully restructured for writing convenience, specifically by sections:
  • Changes in screen capture part.
  1. In old version, function "get_screenshot" took parameter "save_name", which allowed to save screen directly to file. Return type was pointer to memory "unsigned int*", which indicated dynamically allocated memory.
  2. In new version this parameter (I mean save_name) is removed, now function just returns pixel buffer. New version use modern C++ "std::unique_ptr" parameter, which makes memory management easier and will cause less bugs in future.
  • Memory part.
  1. In old version raw pointers "malloc" and "free" were used for memory allocation. Author of updated source did research and found that this created risks of memory leaks if errors happened before calling "free".
  2. In new version all this was replaced with "std::unique_ptr", which automatically manages memory and possible leaks are fixed.
  • Bitmap config part.
  1. In old version headers were created manually using own calculations.
  2. In new version headers are easier to do, since image height is set negative (biHeight = -crop_height). This helps implement usability of format for DIB format, which is intuitively clear and works better with top part of image.
  • File saving.
  1. In old version in "get screenshot" file saving logic was already built-in.
  2. In new version author moved this logic to separate function pixelsToBMP, which improves modularity and usability of code.

TthHWAT.jpeg

What new was added?

  • Config system.
Now cheat has cfg system. Before all info about settings was parsed from simple txt file, now everything saves in config.dat. This file is encrypted, which (in author opinion) helps protect it from reverse (I really don’t understand why this is actually needed, but okay…).
  • Multithreading.
In this reworked source added support for multitasking code. Now at same time goes screen capture, waiting for key presses, parsing updates and in-game events.
  • Performance.
Now process of aim activation (screen capture) takes about 15 milliseconds, which is perfect time for 60 FPS gamers. Code became more optimized and fast, so now hack almost don’t load PC and don’t affect game performance.
  • GUI (user interface).
In new source added hack interface, which now shows which config parameters are loaded, bot status, response time. Became much more convenient to edit and check hack work.

What is planned to do?

  1. Direct access to GPU: author wants to rewrite code to use DXGI Desktop Duplication API. It much faster than BitBlt (that is, everything else based on GDI) and it will be possible to use aimbot with FPS above 144 frames, which in Valorant is very important. The more FPS, the nicer to play and faster aim will trigger on enemies. And considering that almost all of us have monitors 144–165 hertz and higher, I really looking forward to adding this method to source. As soon as update is out, I will immediately upload it.
  2. Refuse from low-level hooks: instead of WH_MOUSE_LL use Raw Input API (functions RegisterRawInputDevices, GetRawInputData). When using direct input response time is reduced and in general it is less invasive. Although author is not sure if detect chance from Vanguard will decrease, API Raw Input does not change memory in any way, does not block, only reads input. As I read and found out, any input method that edits/blocks memory in Valik will be insta-banned. So this is good bypass method. Also waiting and will immediately upload update as soon as it is ready.

FAQ

  1. Can download and use immediately?
    No, this is source code. Need to compile it through Visual Studio.
  2. Cheat not detected by Vanguard?
    For now not detected, what will be next - unknown. But author did everything so hack will continue to work stealthily.
  3. Need something besides Visual Studio for hack?
    Straight hands, C++ knowledge, ability to google.

Conclusion

Came out great source, with cool and necessary improvements, good groundwork for future and already with good fixes and well-developed base. Hope coder will not abandon his project and then this will be one of top undetect projects for Valorant, not even surprised if someone will add his developments to private cheat and start selling it.
 
Top