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 "User:Belal/Memory research"

From Dwarf Fortress Wiki
Jump to navigation Jump to search
 
m (-category)
 
(26 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Category:Hacking|Memory research]]
+
[[Category:Hacking|Memory research|]]
=Feburary 17, 2010=
+
 
 +
=Feburary 17, 2010 - Windows Version 0.28.181.40d17=
 +
==Addresses==
 +
 
 +
{| width="100%" border="1" cellspacing="0" cellpadding="2"
 +
! width="12%" align="right" | Address
 +
! width="25%" | Type
 +
! width="13%" | Name
 +
! width="50%" | Information
 +
 
 +
|-
 +
| align="right" | 0x014240A4
 +
| std::vector()
 +
| Notes
 +
| holds the notes for the map
 +
 
 +
|-
 +
| align="right" | 0x01E185DC
 +
| std::vector()
 +
| Fort
 +
| vector of fort objects, however only has the currently active fort in it
 +
 
 +
|-
 +
| align="right" | 0x01E18510
 +
| std::vector()
 +
| Settlements
 +
| holds data for all the settlements in the world, they are in the vector by creation date, so the current fort is always length-1
 +
 
 +
|}
 +
 
 +
==Offsets==
 
===Notes===
 
===Notes===
 +
Looks like:
 +
struct Note {
 +
  char symbol;
 +
  int foreground;
 +
  int background;
 +
  string name;
 +
  int x;
 +
  int y;
 +
  int z;
 +
}
 +
 
{| width="100%" border="1" cellspacing="0" cellpadding="2"
 
{| width="100%" border="1" cellspacing="0" cellpadding="2"
 
! width="12%" align="right" | Offset (+Hex)
 
! width="12%" align="right" | Offset (+Hex)
Line 7: Line 48:
 
! width="13%" | Name
 
! width="13%" | Name
 
! width="50%" | Information
 
! width="50%" | Information
 +
 +
|-
 +
| align="right" | 0x0
 +
| char
 +
| symbol type
 +
| ascii char for the symbol to use
 +
 +
|-
 +
| align="right" | 0x2
 +
| int
 +
| foreground color
 +
| foreground color for the note
 +
 +
|-
 +
| align="right" | 0x4
 +
| int
 +
| background color
 +
| background color for the note
  
 
|-
 
|-
Line 15: Line 74:
  
 
|-
 
|-
| align="right" | 0x34
+
| align="right" | 0x24
 
| int
 
| int
 
| x
 
| x
Line 21: Line 80:
  
 
|-
 
|-
| align="right" | 0x36
+
| align="right" | 0x26
 
| int
 
| int
 
| y
 
| y
Line 27: Line 86:
  
 
|-
 
|-
| align="right" | 0x38
+
| align="right" | 0x28
 
| int
 
| int
 
| z
 
| z
Line 33: Line 92:
  
 
|}
 
|}
 +
 +
This is interesting: the ints are two bytes each, yet the string starts at offset 0x8, implying something in it requires four-byte alignment. Moving char symbol to immediately after string name in the structure should immediately save at least two bytes per instance without having to change the types of any of the members.
 +
 +
==Forts==
 +
 +
settlements 8B 0D ? ? ? ? 8B 0C A9 83 79  70 FF
 +
current_settlement 8B 0D ? ? ? ? 8B 0C B1 83 B9 14 01 00 00 00
 +
 +
{| width="100%" border="1" cellspacing="0" cellpadding="2"
 +
! width="12%" align="right" | Offset (+Hex)
 +
! width="25%" | Type
 +
! width="13%" | Name
 +
! width="50%" | Information
 +
 +
|-
 +
| align="right" | 0x38
 +
| dword
 +
| prefix
 +
| the index for the first part of the fort name
 +
 +
|-
 +
| align="right" | 0x3C
 +
| dword
 +
| suffix
 +
| the index for the last part of the fort name
 +
 +
|-
 +
| align="right" | 0x7a
 +
| word
 +
| world_map x
 +
|
 +
 +
|-
 +
| align="right" | 0x7c
 +
| word
 +
| world_map y
 +
|
 +
 +
|-
 +
| align="right" | 0x100
 +
| word
 +
| local_map x_begin
 +
|
 +
 +
 +
|-
 +
| align="right" | 0x102
 +
| word
 +
| local_map x_end
 +
|
 +
 +
 +
|-
 +
| align="right" | 0x104
 +
| word
 +
| local_map y_begin
 +
|
 +
 +
 +
|-
 +
| align="right" | 0x106
 +
| word
 +
| local_map y_end
 +
|
 +
 +
 +
|}
 +
 +
Object Size = 0x198
 +
 +
These are indexes to the name vectors, in the stock screen both the dwarven name and the generic name are displayed
 +
 +
=Linux d16=
 +
 +
==Addresses==
 +
settlements 8B 15 ? ? ? ? 29 D0 C1 E8  02 0F 84 B1 00 00 00 0x08F9C77C
 +
current_settlement A1 ? ? ? ? 8B 1C 30 8B 83 A8 00 00 00 89 2C 24 0x08F9C7E8

Latest revision as of 15:34, 12 March 2010


Feburary 17, 2010 - Windows Version 0.28.181.40d17[edit]

Addresses[edit]

Address Type Name Information
0x014240A4 std::vector() Notes holds the notes for the map
0x01E185DC std::vector() Fort vector of fort objects, however only has the currently active fort in it
0x01E18510 std::vector() Settlements holds data for all the settlements in the world, they are in the vector by creation date, so the current fort is always length-1

Offsets[edit]

Notes[edit]

Looks like:

struct Note {
  char symbol;
  int foreground;
  int background;
  string name;
  int x;
  int y;
  int z;
}
Offset (+Hex) Type Name Information
0x0 char symbol type ascii char for the symbol to use
0x2 int foreground color foreground color for the note
0x4 int background color background color for the note
0x8 string name text for the note
0x24 int x
0x26 int y
0x28 int z

This is interesting: the ints are two bytes each, yet the string starts at offset 0x8, implying something in it requires four-byte alignment. Moving char symbol to immediately after string name in the structure should immediately save at least two bytes per instance without having to change the types of any of the members.

Forts[edit]

settlements		8B 0D ? ? ? ? 8B 0C A9 83 79  70 FF
current_settlement 	8B 0D ? ? ? ? 8B 0C B1 83 B9 14 01 00 00 00
Offset (+Hex) Type Name Information
0x38 dword prefix the index for the first part of the fort name
0x3C dword suffix the index for the last part of the fort name
0x7a word world_map x
0x7c word world_map y
0x100 word local_map x_begin


0x102 word local_map x_end


0x104 word local_map y_begin


0x106 word local_map y_end


Object Size = 0x198

These are indexes to the name vectors, in the stock screen both the dwarven name and the generic name are displayed

Linux d16[edit]

Addresses[edit]

settlements		8B 15 ? ? ? ? 29 D0 C1 E8  02 0F 84 B1 00 00 00	0x08F9C77C
current_settlement	A1 ? ? ? ? 8B 1C 30 8B 83 A8 00 00 00 89 2C 24	0x08F9C7E8