Undetected [Release] Valorant Sunoki Triggerbot v4 — OBS Capture Bypass

[byte_corvus]

Bypassing Vanguard's screen capture protection is getting sweatier by the day, but Sunoki just dropped an update that pivots the logic toward OBS. This build fixes the previous capture failures by leveraging OBS hooks to grab the frame buffer, making it significantly harder for the anti-cheat to flag the screen capture process as a malicious overlay or recording tool.

Architecture & Method
The core logic relies on a Python wrapper interfacing with a custom GameCapture.dll. Instead of standard GDI or Desktop Duplication, which Vanguard monitors closely, this version forces the game capture through the OBS backend.

Technical Stack:

1. Python 3.11.0 (Strict dependency for the C-types interfacing).
2. OpenCV + NumPy for real-time HSV color filtering.
3. Custom C++ DLL (GameCapture.dll) for the OBS bridge.
4. Win32API for PostMessage input simulation.

Configuration and Logic Setup
To get this running without the script puking errors, you need a specific environment setup. This isn't a one-click 'pasted-exe' — you actually need to understand how the capture pipeline flows.

You cant view this link please login.

You cant view this link please login.

Spoiler: Technical Setup Guide

1. Install Python 3.11.0 and ensure it is added to your PATH.
2. Install dependencies: opencv-python, numpy, pywin32.
3. Keep the Python script and GameCapture.dll in the same directory.
4. Install the latest version of OBS in the default C: drive directory.
5. Launch Valorant and stay in the menu/range.
6. Run the script and map your fire key to '0' (must be the top row, not the numpad).

The Capture Logic
Below is the core implementation of the OBS capture interface. It uses ctypes to pull raw frame data from the DLL's memory buffer into a NumPy array for the CV2 mask to process.

class OBSCapture:
    def __init__(self, dll_path: str, fov_w: int, fov_h: int, screen_w: int, screen_h: int, window_title: str):
        if not os.path.exists(dll_path):
            raise FileNotFoundError(f\"Missing DLL: {dll_path}\")
        self.dll = C.WinDLL(dll_path)
        self.dll.gc_create.argtypes = [C.c_int32, C.c_int32, C.c_int32, C.c_int32, C.c_char_p]
        self.dll.gc_create.restype = C.c_void_p
        self.handle = self.dll.gc_create(int(fov_w), int(fov_h), int(screen_w), int(screen_h), window_title.encode(\"utf-8\"))

    def get_latest_frame(self):
        ok = self.dll.gc_get_frame(self.handle, C.byref(self._img))
        if not ok or not self._img.data:
            return None
        raw = C.string_at(self._img.data, self._img.height * self._img.pitch)
        buf = np.frombuffer(raw, dtype=np.uint8).reshape((self._img.height, self._img.pitch))
        return buf[:, :self._img.width * 4].reshape((self._img.height, self._img.width, 4)).copy()

Underground Advice & Risks
While the OBS method is 'safer' than public BitBlt pastes, remember that PostMessageW is a known vector. If Vanguard sees a high frequency of mouse events coming from a non-exclusive input source, you're toast. Keep your shooting rate humanized — don't set the MS delay to zero unless you want to test the automated ban system.

Features Included:

1. Adjustable FOV (defines the capture window size).
2. Configurable Shooting Rate (ms delay between shots).
3. Pre-set HSV profiles for Red, Yellow, and Purple outlines.
4. Custom HSV range support for high-contrast visibility.

Credits to Sunoki for the original logic and the ASCII art. Don't be a skid — keep the headers intact if you're planning to mess with the source.

Anyone finding the OBS capture laggy on lower-end setups, or has anyone tuned the HSV ranges for better performance on the new maps?