Bay 12 Games Forum

Dwarf Fortress => DF Modding => Topic started by: PTTG?? on March 17, 2008, 03:15:00 pm

Title: Can I Has Memory.ini?
Post by: PTTG?? on March 17, 2008, 03:15:00 pm
Do we have any idea when we will get a new version of Memory.ini? I'm dying to use Heal and -wound again; it is inspiring to have annoying invaders spontaneously explode.
Title: Re: Can I Has Memory.ini?
Post by: Nite/m4re on March 17, 2008, 06:46:00 pm
code:
[generic]
DWARF_FORTRESS=0x008D9A58

[address]
MAP_DATA=0x014A60A4
MAP_X_COUNT=0x014A60BC
MAP_Y_COUNT=0x014A60C0
MAP_Z_COUNT=0x014A60C4
MENU_STATE=0x01288D14
FOCUSED_CREATURE=0x00C7CC04
STARTING_DWARF_COUNT=0x007BBDB5
STARTING_POINT_COUNT=0x007BAF5A
MOUSE_X=0x0094228C
MOUSE_Y=0x00942290
MOUSE_Z=0x00942294
CREATURE_VECTOR=0x01464574

[offset]
MAP_DATA_DESIGNATION_OFFSET=0x0260
MAP_DATA_OCCUPANCY_OFFSET=0x0660
CREATURE_NAME_OFFSET=0x0000
CREATURE_X_OFFSET=0x0094
CREATURE_Y_OFFSET=0x0096
CREATURE_Z_OFFSET=0x0098
CREATURE_BODY_PART_HEAL_VECTOR_OFFSET=0x02FC  


Title: Re: Can I Has Memory.ini?
Post by: PTTG?? on March 17, 2008, 08:25:00 pm
Thank you, this is the current version. Unfortunately, this does not cover all the utilities du Rick, in particular Heal. Anyone know how to find the new numbers for the body part health? By the way, is it possible to create a utility that instead of merely mangleing a creature causes all of it's body parts to "explode" away? I would pay dollars upon dollars for that!
Title: Re: Can I Has Memory.ini?
Post by: Logan on March 17, 2008, 09:00:00 pm
The problem isn't memory addresses, it's that (V)iew Creature works differently as of 38a. The utilities that use V to "target" their effects need to be recoded, possibly from scratch (we still haven't figured out exactly what changed).
Title: Re: Can I Has Memory.ini?
Post by: vilehermit on March 19, 2008, 01:12:00 am
Where do I put all of that code?
Title: Re: Can I Has Memory.ini?
Post by: n9103 on March 19, 2008, 05:20:00 pm
in a new file called memory.ini that sits next to your collection of Rick's Utils.
make sure the actual filename is memory.ini, and not memory.ini.txt, as happens when extensions are hidden in Windows.