Content: Slate Blackcurrant Watermelon Strawberry Orange Banana Apple Emerald Chocolate Marble
Background: Slate Blackcurrant Watermelon Strawberry Orange Banana Apple Emerald Chocolate Marble
Pattern: Blank Waves Notes Sharp Wood Rockface Leather Honey Vertical Triangles
Welcome to Xbox Chaos: Modding Evolved

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

lukeymoo

Members
  • Content count

    1
  • Joined

  • Last visited

About lukeymoo

Profile Information

  • Gender
    Male
  1. Are there resources to learn about interpreting map file raw data? I have only found older resources which give me the jist such as daeh, version num, file size but I am absolutely stumped on index header offset. It's stated to be a 32 bit number on most available resources however it appears to be a 64 bit number when comparing raw hex values to Assembly output. This has been absolutely infuriating for the last week. I have a map file(modified beachhead map with AI enabled) I have managed to put together with a few older guides -- the `index header offset` I am seeing is 00000001`CA4A174C when properly interpreted. This matches assembly's output; Problem is this address is out of range for the map file, using the process base address in debugger it points to junk or non accessible memory. My understanding is I am supposed to use this offset to find a magic that would help me translate all further ptrs in the map. I'm trying to write more complex scripts that could be quickly edited & also learn about lexing/parsing in the process. Does anyone have some knowledge on the back end of modding GUIs?