![]() In newer code/languages you have the option to run all sorts of bits of code in different orders, and have the code handle noting where things are in memory rather than typically having them baked into the code. ![]() For memory based stuff, at least as far as cheats were concerned, they were rare and everything would be in the same place boot after boot after boot with no scope for any change. In old school games (anything that ran in REAL mode on X86 or anything 16 bit or older, though it took a long time for it to get phased out - 95% of the time this works just fine on the DS for example) you might have encountered a pointer mainly only in dealing with text and the like, or as a jump in the code. I will note it is a valid thing to do in programming to have multiple pointers nested, not that it really matters for the would be cheat maker if it is a valid coding reason, the dev having a good time or just a frustration to would be cheat makers/cheat users as it is still the same problem to solve. indeed stacking 20 of them up with a few other things is a common question when they teach new programmers to make sure they truly get the idea but I will hold off there for a moment. You can have a pointer to a pointer to a pointer. The pointer literally pointing the way to said data or part of the code. Anyway pointers are a concept in programming that allow you to note where something else is in a program/memory. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |