Introducing ClosetCleaner (new Addon)

Note: 12/9/17
This should be live now as gearswap library I think most of the bugs I originally mentioned are fixed.

just type //gs cc to run it, and it will generate the file. Make sure you set up your ccConfig.xml file (it will download a sample one initially)


Ok first time trying to make an addon so anyone interested in testing it out please do so (or helping develop it)

https://github.com/Fox214/closetCleaner

From the readme:

Other musings:
It looks like I'm wasting about 80 inv. spots on stuff I'm not using.

If you abuse set_combine() a lot the counts may show up a lot higher than actually searching for them will. (I have my bladeborn earring in 635 sets across 16 jobs)

I want to fix the known issues stuff, but not sure how (Not sure if it would make more sense to integrate this into gearswap or keepit a separate addon?)

I was hoping to put options on what to do with gear in the report (ie AHable, send to mule, store on npc or slip, trade for voucher etc..) but I'm not sure that data is in the resources file.

It will also help you find typos in your files (if you shows gear you know you're using it could be because you've misspelled the gear or slot named (I had ranged instead of range on a few ugh...)

Feedback & help welcome.

I get gearswap/data/MNK.lua:196 attempt to index field 'DarkRing' (a nil value)

I don't have a mnk lua

I use windower.raw_register_event functions in a couple of my lua files and cc report throws a runtime error on each of those lines: "attempt to call field 'raw_register_event' (a nil value)"

See known issue #3, just comment them out (you can uncomment them immediately afterwards) I hope to fix this eventually. (if you use notepad++ hightlight the lines, hit cntl-Q,(to comment), cntl-S (to save) run //cc report, then it cntl-Q (to uncomment), cntl-S (save again) and its back to how it started, I know its annoying work around but it should only take a couple seconds. (and I really don't expect people to run this tool but once a week or so)

Thanks, I should learn to read the whole post... Could you make it use the <job>_gear.lua or <player>_<job>_gear.lua files that are commonly used, especially in motes.

I have no idea how you'd get that error if the file doesn't exist.

But if you don't play MNK edit the ccjobs list in ccConfig.lua should be only the jobs you care about tracking gear for. So if you play 5 jobs and have lua files for all 22 then put only those 5 jobs in the ccjobs list in ccConfig.lua. (conversely if you change ccJobs list to all 22 jobs and only have 5 lua files you should be fine, I think there's only 16 jobs in the initial list (which are the ones I play))

Sidiov: I can make that change tomorrow I assume look in this order (all .lua):
<player>_<job>_gear
<player>_<job>
<job>_gear
<job>

In fact if you want to test it before I do change lines 263 to 275 in closetCleaner.lua to this (untested hopefully no typos):

I made that change and ran it with just BLM in the ccconfig.lua, and I get a "lua file for BLM not found".
edit: I have a BLM.lua and a pname_blm_gear.lua in the data dir.

Add these lines in the else:
print('lua file for '..v..' not found!')
print('Checked: '..lgname)
print('Checked: '..lname)
print('Checked: '..sgname)
print('Checked: '..sname)

Make sure those files look like the path and names match. (only 1, don't need all 4)

lua is case sensitive, windows is not. I'm not sure if the dofile or file exists check are case sensitive or not. Make sure its the name of the character you're running from as well (although it should still see BLM.lua) I did put this in my version and it works fine for <job>.lua didn't test other formats but it should work too.

ok figured it out, basically had to force everything to lowercase to account for non-standard case junk:

I think thatll end my testing though, the stack overflows kill it for me, I have several hundred set = set configs that I dont want to go through changing.

So wait, this tells you if stuff in all your storage options isn't being used? Blimey, I've been needing something like this for a long time!

Yes, part of me wanted to call it "*** paying for mog wardrobe 3 &4", and rather than simply report unused items, it counts how often everything is used. So you have the option to get look for alternatives for things that are only used once or twice.

Sidiov: sorry I didn't update yesterday, I'll put the changes in for the lowercase file names tonight hopefully.

I put the changes for the _gear stuff up last night

Just released v0.5, should fixed all the known issues from the initial release. README has been updated as well. Let me know if you have any questions/issues I will try and help.

I had run into a few hiccups in trying to get this to work for me. In case others are having the same problem I figured I'd share what I did to get it to work in my environment.

The fpath variable returns a string in all lowercase, but the gsub function is trying to match a string that contains an upper case C and the substitution doesn't take place.

Lua would complain that 'init_gear_sets()' is a nil value. Doing a search for that function, it seems only Motes files use it(?). I don't use motes myself, and my filenames are Ratie_<job>.lua so to get around that I replaced the instances of 'init_gear_sets()' with 'get_sets()' (which was already in use on line 304).

This line captures almost every alternative spelling for equip slots, just not mine :P We just need to add before 'then' at the end:
I'm not sure of any other alternative spellings for equip slots.

I hope this helps anyone else in the same boat.

oh honey, let me suggest


to (just easier to read)


Is "name" supposed to be an option?

Name gets the augmented gear. Sorry I'll try and spend some time with this soon and get another update out.

OK new version Up I've tried to address the issues raised here, please let me know if you see anything else.

I'm pretty sure problem you have with the path name is likely due to you naming the folder you put the tool in closetcleaner instead of closetCleaner. I just lower case the string though so as long as its spelled correctly that won't matter.

Tried this and love it, but in the report there were some errors. It's like he didn't load a couple of my luas (two: PUP and RDM ones), so all the items in those sets were appearing as "0" uses in no sets at all.

Also, is there a way to make the "//cc report" command ignore some repositories?
Say I don't want it to check into MogSafe and MogSatchel, can I set such filters somewhere?

In ccConfig.lua make sure PUP and RDM are in the ccjobs list, the default list there is most jobs but not all (I don't happen to play those, so I'm guessing that's your problem)

Also at the bottom is the other config:
-- List bags you want to not check against
skipBags = { 'Storage' }
just change to (needs to match Location column in the report):
skipBags = { 'Mog Safe', 'Mog Satchel' }

Might want to delete, add, change stuff to ccignore as well.

Thanks a ton, will keep testing this very useful addon.

One more feature you might be thinking about for the future.
The report already lists the number of times an item appears in different sets, and this is already a very useful information by itself. But know what would be even better?
To know how many times an item X appears in different Luas.
Like if item X appears 4 times in WAR lua, 7 times in WHM lua and 2 times in BLU lua, the result in this column should display "3".
This number would be perfect to decide which items to prioritize into wardrobes.

Not sure how complicated this addition would be, but thought I would ask regardless.

As FYI --
It failed for a friend if the .lua had a sub set without a main set. I do not recall what error that caused, but I can look it up later.

e.g. just having the following would fail:
sets.midcast.Cure = {ammo="Random Item"}


While it would work when I have:
sets.midcast = {}
sets.midcast.Cure = {ammo="Random Item"}

This is working only partially for me, what did I do wrong in the syntax of the config?

This is expected, lua won't let you define:
a.b.c = {}

unless you
a = {}
a.b = {}
first.

All I can figure is something he's got init_gear_sets or get_sets serialized with whatever function defines sets.midcast = {} (or its possibly in an include file I can't find)

ie if in a function he has:
sets.midcast = {}
get_sets()

His lua will work but this program will not because after it loads your file it just calls get_sets() so that table is not initialized, I was hacking around this in an eariler version but when I figured out how to read through Mote's include files I removed a few of these dummy tables figuring people would have them initialized.

Sechs:
Make sure you reloar //lua r closetCleaner if you edit your config file or change your inventory, those items are read when the program loads and not when the report is generated. That's the only reason I could figure why what you typed won't work.

Also I have a version which tries to show which jobs the gear is being used for, but I'm stuck I can post it some where if someone wants to look at it. The problem I'm having is lua doesn't seem to be crawling through he tables recursively it seems to be flattening them and going through in a random order.

so most lua should have:
sets.idle
sets.engaged

I'm reading through all the files can create:
supersets.BLM.sets.idle
supersets.BLM.sets.engaged
supersets.BLU.sets.idle
supersets.BLU.sets.engaged

so I pass supersets to list_sets function, and was thinking it would go through them recursively ie:
supersets is a table, descend:
supersets.BLM is a table, descend (store BLM here)
supersets.BLM.sets. is a table, descend
supersets.BLM.sets.idle is a table, but there are gear slots I recognize record that data. move on...

But it looks like its all randomized, so it might search like this:
supersets.BLU.sets.engaged
supersets.BLM.sets.idle
supersets.BLM.sets.engaged
supersets.BLU.sets.idle

which using the method above has my blm idle and engaged gear show as coming from the BLU file.

I don't know how to qualify a full table name in lua (in fact I think its a generic problem with languages that use references)

Fortunately the random order doesn't matter when I don't care where things come from. (which the current code does not)

So if anyone has ideas I'm all ears.

DISCLAIMER: I'm a total hack sorry if I offend any compSci types with my feeble explanations.

Edit #2: I wasn't planning on putting a count in I was trying to just make a list so Inyanga Jubbah +1 would just show WHM, SMN, BRD next to it (or some subset thereof) its the same as 3 but more informative. I don't think I can give 3 now either though since it gives false positives.

Of course I was unloading and reloading the addon, it still reports every repository in the Report txt file :x


Btw, before you created this awesome addon, the way I was cleaning my inventory was through the "Validate" function built-in in Gearswap.
More details if anybody is curious:

Of course ClosetCleaner is so much better and offers so much more potentially than my primitive thing was able to do.
You should submit it to the Windower Github and turn it into an "official" addon btw.

If you can find a manageable way to "count" in how many luas/jobs an item is used and display that number, I think it's gonna be quite useful.
That, combined with how many sets a certain item is present in (an info CC already gives) will be awesome to decide which items to prioritize into wardrobes and maybe which items to get rid of.

For instance an item that offers stat+1 over another option but is used on a single job.
When I encounter these situations, I sometimes decide to get rid of that single item and eat the small stat loss, to gain an inventory slot.
It's not always an easy choice of course.

This is the exact reason I decided to print the count, obviously "0" is generally good candidates for /toss but things only used in a couple of sets that offer +1 STR or something over an alternative piece are nice candidates for saving space too.

The way I handles this though is I just have all my luas open in tabs in np++ I hit cntl-F for find and paste the name in and hit "Find in open documents" button. I tend to use short form names in my lua but I printed the long form off to the right in case others aren't then you can search for that too, so 2 searches max to find all locations for a piece of gear.

Yeah, I kinda do the same. As I said, love it.
I already found 5 items in my wardrobes that I no longer used (replaced by other, newer items) and I didn't notice I wasn't using them anymore :D

I figured this out and should have an update out tomorrow.

I actually discovered a major bug too, the whole problem wasn't lua reading tables in random order it was that I didn't reinitialize sets = {} before reading each file so extra gear was getting appended to it that I did not expect.

0 counts should still be correct but everything else will drop in numbers. (particularly with unique set names that would not get overwritten by subsequent files)

I just need a bit of time to clean up the code before I release it.

Nomnomnom, can't wait.


(you should submit it to Windower Github and make it an official addon btw)

Ok its up, oddly I was getting a bug with the skipBags feature after I made updates (but not to that section of the code) so I ended up rewriting it and wondered how it worked for me.

Anything it previously counted 2+ for could be reduced in number as well (0 or 1s would have been correct).

I also got rid of the _sets, _inventory and _ignored files unless you set the debug flag in the config file. (and the input commands from help)

I also just cleaned up the code somewhat. so its hopefully a bit easier to read/maintain.

Is it supposed to find and use the gearswap include files if they are already installed?