-
-
Notifications
You must be signed in to change notification settings - Fork 122
WAD: add support for tags and labels #57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
I've modified the commit to only allow certain elements in a folder: those that are part of a map. This is the output for doom2.wad: Output of `./test_physfs "mount /tmp/DOOM2.WAD /doom2 0" "tree /doom2" "quit" ` |
|
I have no idea if this is going to cause some Doom port that's using PhysicsFS to explode when files move around, but I also don't know if any such Doom port exists. I'm cool with merging this otherwise. |
|
Let me ask on a doom forum first. |
Currently, the WAD loader flattens all files in one folder, but the unofficial DOOM specs says a zero-size directory entry means a label/marker.
This pr modifes the WAD loader to put all directory entries that follow this label/marker in a new directory.
When built on top of #56 (because this uses the `tree` command), this results in the following tree
It looks
E1M9collects a lot of extra directory entries.Perhaps the loader should only allow the 10 specific elements(BLOCKMAP - VERTEXES) when it sees a
ExMyorMAPxxlabel. But I don't know how much doom specific we want this WAD loader to be.Anyways, the current WAD loader will overwrite names with equal filename.