- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 104
- Reaction score
- 7
Anyone else running into issues with the new Raw Input Buffer settings for colorbots in Val?
Just got back into the scene after a multi-year hiatus and realized my old setup is effectively bricked. I'm currently rocking a Raspberry Pi Pico W as a USB HID endpoint, with a Python script pushing movement commands via socket over Wi-Fi. It handles desktop movement perfectly, but the moment I launch and get into a match, the game completely ignores the input.
The Technical Breakdown:
I am trying to avoid a perma on my main, but I need to get this working for a secondary account experiment. I have been looking at different ways to emulate the HID packets to appear more like a physical mouse, but I am worried about the behavioral detection on the server side if the timing isn't perfect.
Has anyone here successfully pushed movement commands through a KMBox while Raw Input is active, or are you guys just forcing the settings to play without the buffer (which usually isn't an option anymore)?
If anyone has updated their Python logic or found a way to bridge the gap between the socket listener and the game's current input requirements, please drop some knowledge. Really trying to avoid a full re-write of the stack if I can just adjust the packet structure.
Curious if anyone else is still trying to get pixel-based logic to work in this environment or if it is time to just shelf the colorbot approach entirely.
Just got back into the scene after a multi-year hiatus and realized my old setup is effectively bricked. I'm currently rocking a Raspberry Pi Pico W as a USB HID endpoint, with a Python script pushing movement commands via socket over Wi-Fi. It handles desktop movement perfectly, but the moment I launch and get into a match, the game completely ignores the input.
The Technical Breakdown:
- The Input Issue: It is pretty clear that the forced Raw Input Buffer is the culprit here. Riot basically locked out standard Windows mouse API calls for aim-assist scripts, which is why your old-school Python scripts are hitting a wall.
- Hardware Hook: Using a Pico W via Wi-Fi is clean for isolation, but if the game isn't registering the HID reports because of the buffer shift, you need to look at how you are interfacing with the mouse driver layer.
- The Bypass Path: Has anyone found a reliable way to hook into the buffer, or is the consensus just to move toward a full DMA setup with a KMBox? I know people are still using AI-based scripts, but the manual ban risk is higher if the mouse movement doesn't feel native to the buffer.
I am trying to avoid a perma on my main, but I need to get this working for a secondary account experiment. I have been looking at different ways to emulate the HID packets to appear more like a physical mouse, but I am worried about the behavioral detection on the server side if the timing isn't perfect.
Has anyone here successfully pushed movement commands through a KMBox while Raw Input is active, or are you guys just forcing the settings to play without the buffer (which usually isn't an option anymore)?
If anyone has updated their Python logic or found a way to bridge the gap between the socket listener and the game's current input requirements, please drop some knowledge. Really trying to avoid a full re-write of the stack if I can just adjust the packet structure.
Curious if anyone else is still trying to get pixel-based logic to work in this environment or if it is time to just shelf the colorbot approach entirely.
