SanyaWaffles wrote:Since the inclusion of the tncluded editor functionality, GZDB has been locking the map WADs, causing this to break., It only did that after MaxED introduced the scripting additions. I mean, the map is loaded into a temporary WAD anyhow, why should the map WAD be read-only? Doesn't make sense to me.
Actually I'm trying to fix this currently. For example I made the script editor reload resources as readwrite only before writing the changed file, then reload them back as readonly (unlocked).
Not sure if it works currently ATM.
If I make GZDB properly unlock stuff (and still save files), I might keep the script editor in, as there are apparently a lot of people using it (I honestly expected a number around 2).
Currently with file locking it looks like this:
First time map loads, it locks everything.
Then when you edit your map and save, it unlocks resources and you can edit them again.
Afterwards, I think, it should work properly too. Files should only be locked when GZDB reads and writes them.
With PK3 there's one slight problem though: normally PK3 readers dynamically read stuff back from the disk, so when the archive changes, you get very weird results.
Try running GZDoom and changing the used PK3 on-disk, and see what happens.
Quitting to console or completely broken graphics (and possible memory corruption) are the best things you can get out of it

Since GZDB only reads archives during resource reload stage, I'll try to limit locking to that part somehow.