Discrepancy between same map data pre-and-post to_lumps about omgifol HOT 4 CLOSED

Back when I was first adding Python 3 support, I had to deal with cases where some IWAD maps had garbage following the ending null bytes in sidedef texture names. It's possible/likely that the only reason the MD5s differ after saving is because MapEditor removes these at load time.

I'm not really sure if there's a very good way to account for those cases that doesn't affect the MD5 of a map, though. It's kind of unfortunate that the sums can end up being affected by something that is totally invisible to the user and liable to be silently removed by WAD editing tools.

from omgifol.

Hmm. All I need out of omgifol in this case is to copy the map lumps' data directly into a new standalone file, is there a way to do that that doesn't even involve creating a MapEditor?

from omgifol.

In that case, you can just put a shallow copy of the map's lumps into a new omg.WAD instance and save that, i.e.:

src  = omg.WAD("doom.wad")
dest = omg.WAD()

dest.maps['E1M1'] = src.maps['E1M1']
dest.to_file("e1m1.wad")

This creates a new WAD with a byte-for-byte identical map to the source and is probably also significantly faster than having to parse and save all the map data each time.

from omgifol.

This works great, thanks very much. Feel free to close this as WONTFIX or whatever's appropriate.

from omgifol.