Originally Posted by tralce

Fair points, all.
Speed, efficiency, convenience. I very often find myself wondering "the heck does THIS go in?" and have to search on uesp to read an article on Perfect Roe or PMoP to find out what it's used in, and searching by ingredient would make that vastly more efficient.

Originally Posted by code65536

I thought it would be straightforward. Maybe I was a bit too verbose...

Simple version:

• Plus sign: Use it yourself.
• Pips: Give it to someone else to use.

Slightly less simple version:

• 3 Pips: Give it to your main
• 2 Pips: Give it to someone more important.
• Plus sign: Use it yourself.
• 1 Pip: Give it to someone less important.

Originally Posted by code65536

I'm not sure what the use case for this would be. Searching by set bonus helps solve the problem of finding a set to meet a particular need. But I don't see why someone would care about finding the recipes that use flour or honey. Searching by a food's effect--e.g., max magicka--could be useful. But ingredients?

Originally Posted by code65536

There used to be a fourth "All" option in the box in the early stages of CK's development, but it was removed:

• A combined view was unwieldy and cumbersome.
• I didn't feel like seeing a motif alongside a furnishing plan added anything really interesting because the contexts are so different.
• I might in the future add something that would only make sense for one item type, and having each type confined to its own view would make this easier.

Originally Posted by code65536

There's a lot of documentation that I need to write but haven't found the time for.

• Plus sign: The current character is the one that should learn the item.
  • Specifically, the highest-ranked character who does not know the item is the current character.
• Pips: The item should be learned by a different character, not the current character, with the number of pips denoting the relation of that character with your current character.
  • 3 pips: The highest-ranked character who does not know the item is the first character on your priority list (i.e., your main) and is not the current character. It may or may not be known by the current character.
  • 2 pips: The highest-ranked character who does not know the item is ranked higher than the current character. It may or may not be known by the current character.
  • 1 pip: The highest-ranked character who does not know the item is ranked lower than the current character. It is known by the current character.

Originally Posted by code65536

Thanks for the feedback.

First, having a single unified priority list per server is central to the design of LCK, and I have no plans to change that. In my personal case, the first three characters on my priority list are the three mains from my three accounts. And then there are some characters in my second account who take priority over some of the characters in my first account, so there's a lot of intermixing. Even for players who don't intermix as I do, a single list still has its advantages, namely that you can see which character on your other account it should go to, rather than that it should just go to someone there.

The way that ordering happens right now, with priority classes and seniority, is in part the result of the toolkit that's available to me via LibAddonsMenu. The feedback that I got during the closed beta is that it's a bit clunky and limited, and I agree that it is. The problem is that a more robust approach to setting character order would mean designing and creating a UI entirely from scratch, without using the LAM toolkit, and that's more work than what I'm willing to put into this project at the moment.

The intent that I had with the current system was for character age to do the heavy lifting (since in most cases, players give older characters priority) and then use the priority classes as a way to do spot-fixing. In my case, for example, my main isn't my oldest character, so I manually promoted that character with its own priority class. And then the mains of my other two accounts were promoted as well to the second and third place spots in the list, and then I left pretty much everything else alone, and I imagined that this sort of thing would work for most players. But for players who want to make lots of changes, then the whole priority class system--even if I were to expand it beyond 13 classes--is clearly inadequate and cumbersome. But, again, changing this would require a fundamentally different approach and an entirely new custom UI, and that's a bit too much wheel-reinvention than I am willing to do at the moment. Sorry.