Quote:
|
Originally Posted by CaptainCox
A good way to be sure that you have the right address in the Tweakfile is actually not to use the address at all...he?
It is connected to what WEBSTER is saying in above post. If you have a word appear more then one time in a .dat we can use "SEARCH" instead of putting the exact address in the Tweakfile.
For example, lets say we have the word "Displacement" appear...lets say 2 times in a .dat/sim/zon.
We know all of them are 2 BYTES after the search word (In this case the word "Displacement")
Could look like in this example
So lets do the 1st "Displacement" for our Tweakfile code
Quote:
|
search,displacement,1,single,>2,displacementSurfaced
|
Notice the 1, its means, THE FIRST INSTANCE of the word "displacement"
>2 means, TWO BYTES AFTER THE SEARCH WORD!
Ok, lets put in out second "Displacement" search...I think you figured this already, but here goes 
Quote:
|
search,displacement,2,single,>2,displacementSubmerged
|
Notice the 2, its means, THE SECOND INSTANCE of the word "displacement"
No address and this method might also work after a patch, as it will not search for a specific address location, but rather find the value specified by the search word...
Easy peasy
Most of this stuff I think should be Credited to Timetraveller, I am not 100% if more people contributed to this, I guess there was, but I only know of Time traveller and of course Nvdrifter doing some outstanding work on Tweakfiles. |
how do you do this when the location is in the middle of the word.
using the word displacement as your example, i found a few of my hex locations were found in the second m inside the word displacement when i was working on #burning_oil_smoke.
do you just list it so many bytes after whatever word it is after , even if it is inside of another word?