Empyre wrote:I am not suggesting that you open a PK3 like a WAD. If you open a PK3 like a folder (it is just a ZIP file, after all), any map inside will have to be in a WAD file, which you already know how to edit. If it is not as simple as I think it is, I will take your word for it and drop it.
This is not complex as in very complex algorithms involved, but more complex as in it requires some non-monkey coding to accomplish and might take some days to implement.
The difference between loading a WAD from a folder and loading a WAD from a PK3 is that I load it from folder by using one API (filesystem one), while with filesystem->PK3->WAD there's one layer added.
I also have no idea how I'll implement saving into a PK3 because I haven't looked into the current load/save mechanism much and I think saving into PK3 would require severe refactoring (because there's 2 levels of abstraction and I'll have to save the current PK3
and the location of WAD and mapname inside that PK3 instead of just mapname, also "unpack wad -> save map -> pack wad", plus I'm not sure if the ZIP library used supports writing, not just reading...)
Also: there are at least two ways to add maps in a PK3, they look similar but one is intended while another works by accident. First, you can put your map to /maps/ and then it'll be loaded as wad's name (IIRC). Second, you can put your map to a .wad file that sits anywhere in your PK3, and then it'll load by "wad in zip" mechanism. So yea this will need some actual nested file selection dialog to work.
So to sum it up: not interested right now, might do in few days/weeks
Xabis: yes. One moment, will fix. Sorry for that.
edit - pushed