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.

Reclaimer Shawn

ASMP vs. PATCHDAT

7 posts in this topic

So, whenever I was making a patch for my custom map, I used Alteration to create a .patchdat. It was about 16.1 MB. I then used Assembly to create a .asmp file, and it was 154 MB. In terms of functionality, is there any difference between the two files? If I imported a lot of resources, which would be the best to use?

Share this post


Link to post
Share on other sites

Not sure what all patchdat supports but asmp is the way to go these days. I'm pretty sure if you try applying the patchdat you made to a fresh map you'll just get a corrupted map.

Reclaimer Shawn likes this

Share this post


Link to post
Share on other sites
11 minutes ago, Lord Zedd said:

Not sure what all patchdat supports but asmp is the way to go these days. I'm pretty sure if you try applying the patchdat you made to a fresh map you'll just get a corrupted map.

There should be some legacy patching support for ascension/alteration patches in Assembly.  Why would using a patchdat on a clean map cause corruption?

Reclaimer Shawn likes this

Share this post


Link to post
Share on other sites
2 minutes ago, Reclaimer Shawn said:

Alright, I'll use the .ASMP format then. Thanks!

Yeah, just to be clear.  Patchdat is an old legacy format pre-Assembly.  Assembly (and thus ASMP) replaced the old toolsets.

Share this post


Link to post
Share on other sites
2 hours ago, Thunder said:

There should be some legacy patching support for ascension/alteration patches in Assembly.  Why would using a patchdat on a clean map cause corruption?

Applying an old patchdat wouldn't harm anything, but creating a new patchdat from a map with tag injection might cause problems. In which case applying said patchdat would only change the 16mb contained in the original map, but not apply the 100+ mb of injected tags/resources to go with it, corrupting the map.

Share this post


Link to post
Share on other sites
21 minutes ago, Lord Zedd said:

Applying an old patchdat wouldn't harm anything, but creating a new patchdat from a map with tag injection might cause problems. In which case applying said patchdat would only change the 16mb contained in the original map, but not apply the 100+ mb of injected tags/resources to go with it, corrupting the map.

Oh I misunderstood.  When you said "clean map" I thought you meant an unmodified map.

Share this post


Link to post
Share on other sites