Speaking of which, do you know why it scans Developer directories (i.e., "--Projects")?
Offhand, I think that's an oversight. Those files would never be installed by BAIN, so I don't see any reason they should be indexed.
There might be some reason for it, but I really can't think of any. That said, it's been so long since I looked at the Bash code, I'm not as familiar with it as I once was.
Does this have anything to do with why BAIN keeps overlooking the DLCShiveringIsles.esp when I initialize it?
Bash has been updated so many times since I was actively involved, that I can't definitively answer that. It does sound related...odd that it would only affect DLCShiveringIsles.esp though.
Edit: showler is exactly right. It is simply a way for BAIN to tell if a file has changed. Unfortunately, to calculate the crc32, it has to read in the entire file. Hard drives are relatively slow, and the data directory can have a LOT of files, so it takes time to process everything. When I add CBash support to Bash, I might be able to speed it up by having CBash do the file reading and crc32 calculating. I really doubt it'll speed it up much though...python isn't as fast as c/c++, but the hard drive is really the limiting factor. I'd be surprised if it shaves off more than a couple seconds from the scan speed. I'll look into other ways of speeding it up later after CBash hits v1.0. Might be some windows api calls that could be used to monitor the folders...really not sure.