I would say they just need to be removed. If incomplete they serve no real function anyway.

Yes - I agree with that.

Works for me. I've been compiling a collection of notes as I anolyze the master list so I'll add that to them.

--version returns 2.3.1 o.o

Though I'm preeeety sure I downloaded 2.3.2, removed 2.3.1, and installed it.

I downloaded boss_installer.7z from git. Are you sure the exe is the correct version there? I'm trying the zip now

Update: got the zip and just extracted the files myself overwriting stuff. Passed version and it still says 2.3.1. This got me curious : D

I did a CRC64 checksum of the exe from the boss 2.3.2 page, "boss.zip" download (never used checksums before so no idea if crc64 is good)

CRC64 0be7abb1b55a9b15

let me know how I can help? haha (if I need boss I'll just use 2.3.0 )

Yep, I just checked the CRCs of the installer each archive contains and I'm pretty sure I uploaded the right versions. Let me know if they continue to read 2.3.1 and I'll try reuploading things.

Reuploaded. Apparently, I was using an old packaging script and had forgotten to update the archives appropriately.

Leading zeroes are assumed for CRCs if they're less than 8 characters long, IIRC. As for the other, when I converted all the dirty messages to LOOT's specific metadata structure, I just threw away any messages without a CRC.

Got it, thanks.


For the cleaning guide URL, should that be hard coded or go in a settings file somewhere, perhaps the INI? All of this is still conceptual but I'm planning to do this as part of the refactoring.

Good. : D I managed to get 2.3.2 as well. I had a shortcut pointing to another place confusing me apparently. All good on my end then.

*checks commit log*

commit f6f104faced54b3989642ae447410db5776739e8
Author: deaths_soul (MCP) 
Date:   Fri Jan 22 16:59:19 2016 -0500

    Restoring the API.

It still needs work but it's been restored!

Does anyone have any requests for the UI? I think I may tackle that next as I begin the refactoring process.


Don't worry, the spinner is on my checklist.

Restore the option to reverse the colouring, dark background with light writing so there's less screen glare when viewing the results or a resort.

Would you prefer it being set with a setting and stored on disk or the same method it used to have?

A setting stored permanently please, as the old method kept resetting itself.

Added to the list.


I'm thinking of setting it up so that users can set it to use any CSS file as an override as long as it's in the correct directory. If the requested file doesn't exist, fall back on the current default one.


Does that sound like a good solution?

As long as a CSS file can be edited and made sense of by non-programmers, sure.

Like me for example. I'm with Vorians....the whole package should be simple to use.

The log already uses CSS for the styles. All I'm going to do is separate out the dark scheme into another file and add a setting to allow for any CSS file to be used as an override.

I've just updated the code for the dirty list generator to be functional again. What it does is it extracts all dirty mods from the master list (currently, it doesn't extract those that have messages saying not to be cleaned but I can change this) along with the corresponding CRCs, ITM counts, and UDR counts. I've generated a list using the current Oblivion master list as a sample: http://gitlab.theassimilationlab.com/deaths_soul/boss/snippets/5/raw

Not sure how useful it'll be but I figured that, at the very least, it'd help by also listing the mods that are tagged as dirty but don't contain do not clean lines or all of the other information (that is, ITM/UDR counts and CRCs).