Terr I feel awful about insulting your hard work. When I first used PackBSP it frustrated me greatly. As for the blob error, it may be because I have some permanently paused downloads. I have not been fair. Let me try and explain my beef better:
my workflow is like this: compile map -> move map & custom assets to a seperate TF folder -> pack assets -> copy map back to maps folder. I do it in this order because of times in which I've corrupted cubemaps and entire bsp's fiddling with pack operations. Doing this lets me keep the mapsrc and maps folders bsp's until the pack succeeds.
Now, let's say I scan for assets and it misses a few things, I then have to hunt down what it missed and hope that I don't break the bsp with a second pack operation. If the bsp breaks then it's trial and error from there, having to repack stuff in a new copy of the bsp until it works.
However, if I simply keep my assets in folders on a per-map basis then all I have to do is select the folders and I know for a fact that nothing is being missed.
Please except my humble apology for calling your work crap, it is not crap, it simply doesn't fit my workflow. Scan function scares me. As soon as I get used to using scan function bsp's start breaking. In the end I've spent less time per map manually packing assets on a per folder basis than using scan.
As for name fixup, this would actually I think fix most of the problems I have with packbsp. Let's say, for example, that you scan and it misses five assets. You remove the assets from your folder and notice that. With name fixup you can add the assets to the bsp from where you moved them to easily.
It all has to do with redundancy, have had many problems over the years so I developed a workflow, and that workflow is slower if I use packbsp. Even if packbsp has a 100% successful scan it would still take more clicks to use since it's broken into several screens.
One last time let me apologize, you must have worked very hard on this and you did do a very good job. It simply doesn't do what I want it to. It does everything at a minimum level, which in theory is fine, but in the real world, in practical situations, things don't always perform as well as you think they will.
I am scared about using a manual add operation after using the scan add operation on the same bsp. The reason I want export pak is that I have a map with six versions, six game modes.
If everything was on one screen and you had five buttons, "Open" "Save" "Scan" "Manual Add" "Export," could add folders and could it had automatic name fixup it would be perfect. As it is people still have troubles with the scan feature and the lack of these other features means that it takes more work to fix a failed scan than to not use it in the first place. Maybe an analogy would be good. To me, packbsp is like a family sedan with an automatic transition while packrat is like a sports car with an automatic transition that occassionally rips itself apart in a firey explosion.
Just because a feature might seem redundant in the face of scanning doesn't mean it doesn't have it's uses.
I intend to finish my paused downloads on steam overnight so that I can reevaulate packbsp.