v50 Steam/Premium information for editors
- v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
- Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.
Difference between revisions of "40d Talk:Memory hacking/v0.27.169.33a"
Jump to navigation
Jump to search
(New page: How might some of these memory addresses (I'm looking at you, "art defacement malus") correspond to addresses in the executable? -~~~~) |
|||
| Line 1: | Line 1: | ||
How might some of these memory addresses (I'm looking at you, "art defacement malus") correspond to addresses in the executable? -[[User:EarthquakeDamage|EarthquakeDamage]] 22:48, 10 November 2007 (EST) | How might some of these memory addresses (I'm looking at you, "art defacement malus") correspond to addresses in the executable? -[[User:EarthquakeDamage|EarthquakeDamage]] 22:48, 10 November 2007 (EST) | ||
| + | :It looks like you need to subtract 0x400000 from the address. So art defacement is at file offset 0x39DC2F. Be advised that this will only work for memory addresses below 0x900000 or so, as addresses higher than that aren't stored anywhere in the executable. —[[User:0x517A5D|0x517A5D]] 21:42, 11 November 2007 (EST) | ||
Revision as of 02:42, 12 November 2007
How might some of these memory addresses (I'm looking at you, "art defacement malus") correspond to addresses in the executable? -EarthquakeDamage 22:48, 10 November 2007 (EST)
- It looks like you need to subtract 0x400000 from the address. So art defacement is at file offset 0x39DC2F. Be advised that this will only work for memory addresses below 0x900000 or so, as addresses higher than that aren't stored anywhere in the executable. —0x517A5D 21:42, 11 November 2007 (EST)