Forum Discussion
You don’t actually need access to the source code to make cheats. Most cheats are created through reverse engineering, memory editing, or hooking into the game while it runs. In many cases, cheat sellers advertise before release because the game is built on the same engine or shares a large amount of code with previous titles, making it easy to adapt existing cheats quickly.
This is a clear indication that the upcoming game will face significant cheating problems. In that case, whether Secure Boot is on doesn’t matter, but completely disabling it won’t make the situation any better either.
SpoolaZ wrote:reverse engineering, memory editing, or hooking into the game while it runs
All that aside, you still need to "edit the source code" to get the program to do something that it was not originally programmed to do. That is what EA needs to rectify.
- Vurp3nkurt12 days agoSeasoned Newcomer
elderwarriors wrote:
All that aside, you still need to "edit the source code" to get the program to do something that it was not originally programmed to do. That is what EA needs to rectify.
You dont actually need to edit the source code to change what a program does. In fact, most cheats are made without ever seeing the source code. Reverse engineering, memory editing, and hooking into the game while it runs can alter values, intercept functions, or inject new behavior directly into the compiled program in memory.
Thats why anti-cheat systems focus on detecting unauthorized memory access, code injection, and suspicious process activity, rather than guarding the original source code. Changing a programs behavior is not the same as having or editing its source code, they are two different things.
About Battlefield 6 Beta General Discussion & Feedback
Community Highlights
Recent Discussions
- 2 hours ago