My theory is probably wrong as I am new and not very familar with the backend of simba, if I am wrong please explain why. The argument that color bots can't be stopped is because see the screen just like a person. This is true but way the image is processed is very different:
- simba analyzes a image to know when to click, type, etc
- you use multiple images to visualize in 3D
So simba and color bots "scrape the screen" by reading the gpu buffer. Correct?
Runescape's rendering speed (frames per second) is based on your processor and not your gpu.
"This means that (despite there being an impact on 'FPS' as well as loading times) this is not a 'graphics' problem - i.e. your graphics card and level of graphics detail are unlikely to have much impact." mod jacmob rs forums Quick find code: 25-26-187-63506974 page 233)
This means they can use your unused gpu processing power for other stuff. If each frame was split into say 10 parts each divided up "randomly". There is a 90% chance that the image simba scrapes will be one frame with random pixels from the next frame ontop of it. This would probably mess up color density algorithms at the least. I'm not sure but i believe you would rarely notice a difference because computer moniters refresh much slower than gpu's.
This wouldn't affect bots that stand still most of the time. Could adding in a screen shift of one or two pixels, similar to plasma tvs anti-burn in feature, mess up bots alone and standing still?
Can simba scrape a screen that hasn't been rendered yet aka in the rendering pipeline? Im guessing it can but could runescape obfuscate the rendering pipeline?
- I don't know if simba could be timed/scripted to scrape only good frames.
- Would limiting video memory make it easier to unobfuscate the rendering pipeline?
- This wouldn't completely stop color bot but it could make the slower and some untended clicking
- Spliting a frame into 10 parts and obfuscating would propably reduce FPS
After typing this it seems a bit excessive for a "side project" of Optimus, but this could be the last step before GrayScape or BlackWhiteScape.
tldr;
If each frame is randomly broken into parts and moved to the front buffer part by part simba will likely scape an image that is a combination of the current and previous frame. This would trick simba so it can't tell if the scraped frame is a combination of 2 frames or one normal frame.
front buffer-is what the moniter will display when it refreshes.


Reply With Quote









, thanks for the feedback!


