Difference between revisions of "Help File:Structure spider"
(Replaced content with '<span style="font-size:25px;color:red">Sorry! Content not available.</span>') |
m (Fixed small typing error: De -> Do & rephrased the sentence) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | [[Category:Help]] | |
| + | The structure spider is like the structure dissect, a useful tool for finding common values and differences between structures. | ||
| + | The structure spider goes a bit further in that it automatically follows all possible pointer paths. | ||
| + | |||
| + | When doing a scan, you can give two base pointers and tell the scanner that the values should be the same, or different | ||
| + | |||
| + | Another use of the structure spider is that it can focus on stringscans, which is useful for heavily scripted games. | ||
| + | For example, if a script engine changes the value of a variable named "ammo" you could do a structure scan for the | ||
| + | text "ammo". | ||
| + | This will show all paths to that variablename. | ||
| + | |||
| + | Do a rescan a few times to filter out the wrong paths, | ||
| + | and you'll have a pretty stable pointerpath you can use in a code injection to see if the script engine is going | ||
| + | to change ammo, or something else. | ||
| + | |||
| + | == Links == | ||
| + | * [[Cheat Engine:Help File|Help File]] | ||
| + | |||
| + | * [[Help_File:Break_and_trace|Back]] | ||
| + | |||
| + | * [[Help_File:Plugin_system|Next]] | ||
Latest revision as of 12:32, 25 February 2023
The structure spider is like the structure dissect, a useful tool for finding common values and differences between structures. The structure spider goes a bit further in that it automatically follows all possible pointer paths.
When doing a scan, you can give two base pointers and tell the scanner that the values should be the same, or different
Another use of the structure spider is that it can focus on stringscans, which is useful for heavily scripted games. For example, if a script engine changes the value of a variable named "ammo" you could do a structure scan for the text "ammo". This will show all paths to that variablename.
Do a rescan a few times to filter out the wrong paths, and you'll have a pretty stable pointerpath you can use in a code injection to see if the script engine is going to change ammo, or something else.
