I agree.
Would storage of enhancements be clustered in individual screens (and thus permissions) by individual table, or would they share a single collective, with the number of tables serving only to limit the total storage?
Personally, I like keeping them by table - specifically for the permissions issue - but if they can be combined (with permissions determining who sees what, or 'greying out' unavailable enhancements,) I'd be fine with that, too.
Okay. Seperated by table--to keep the permissions setup the same. I'm fine with that.
So, it was time for me to go and work on the SG enhancement and salvage bins for one of my SGs. Now, salvage isn't too bad - I decided to add another salvage rack and do a bit of organizing, but every type of salvage has just one name, no range, etc.
When I got to the enhancement bins (Standard, Common IOs by range, Set IOs) - it's a mess. Since I generally do a good chunk of the crafting there, level-range wise it's not bad (I have to shuffle some over,) but trying to sort through them? Here's one -
Lvl/IO
30 - Taunt
30 - defense
30 - Acc
30 - Damage
35 - Acc
30 Resist
30 - End Reduction
25 - Jumping
35 - Run
25 - Damage
30 - Slow
25 - End mod
25 - Acc (which I have to make fewer of, apparently.)
And let's not get into the set IOs.
Simply put, I'd like to have these arrange by name/type and level, preferrably automatically - so they resemble NPC stores, really. Set IOs can go by set name, piece, level (so, say, Posi's 35 Acc/Dam, Posi's 37 Acc/Dam, Posi's 35 Dam/Range, etc.)