Open punpun0707 opened 9 months ago
This avoids entity glow related writes.
这避免了实体发光相关的写入。
The overlay feature in NokVM doesn't seem to work. When I use it, I encounter a segmentation fault. I've tried it on Ubuntu 23.10, Pop!_OS, and Linux Mint, but it doesn't work on any of them. Also, there seem to be issues with trigger settings. I can't trigger with the 111 key, but it works with the 112 key. I'm using a Logitech G502 mouse.
这避免了实体发光相关的写入。
The overlay feature in NokVM doesn't seem to work. When I use it, I encounter a segmentation fault. I've tried it on Ubuntu 23.10, Pop!_OS, and Linux Mint, but it doesn't work on any of them. Also, there seem to be issues with trigger settings. I can't trigger with the 111 key, but it works with the 112 key. I'm using a Logitech G502 mouse.
me too ,when I set trigger key to 111,the aimbot not working too
As you said on UC: Detection possibilities are then narrowed down to two points: detecting specific memory alterations (such as the team ID variable becoming a value impossible in normal gameplay, which can be compared for banning), and detecting the environment (for example, determining if the game is running in a VM and the IP address does not belong to a registered cloud service provider, increasing the risk level and prioritizing bans in case of reports).
For the second point, I (QEMU user) use this method to make my virtual machine like a real one . It works well, which I think is enough to get through EA’s possible detection.
For the first point, I have a question. Some people says overlay version requires less memory alternations, like player/item glow without memory alterations . Is that true? Does overlay version has a lower risk to get banned compared to no-overlay version?