You seem to be misunderstanding the purpose of the currently implemented Low Level rule. It's not flawed at all, it's just an entirely different rule than what you were looking for. It matches all gear <CP160 because due to the nature of ESO, that gear is generally of little value.

I understand your desire for a different rule, but you're replacing a rule that a lot of people will use with one that has much more of a niche use case. Can you remove the patch? It's somewhat misleading since it implies that there is something wrong with the default low level gear rule.

I will definitely implement the two new functions that are needed for you (or anyone else) to implement this type of custom filter, I still plan to do that tonight or tomorrow.

I missed your comment here. I've already done it and submitted it as a 1.22 patch. Feel free to inspect and include it in the next update.

One reply to one of my posts for help got a straight-to-the-point reply:So the short story is that indeed I've been using the wrong API functions. I've switched to using GetUnitChampionPoints and GetUnitLevel. I haven't tested it rigorously yet, but the change resulted in level 50 CP120 items that were previously "low level" for both my CP200+ and level 43 characters now only being low-level for my CP200+ character, and those items match other rules instead for my level 43 character. It seems to be working now as it should have always worked.

I submitted my modified file as a patch specifically for 1.22.

Howdy, Love the addon, everything works great... Except the Alchemy station on the GamePad UI, kinda broken...
I'll attach a screenshot of what I mean.

As you can see it just throws everything everywhere, splits up the waters, oil, and reagents.
Anyway to just turn this off for alchemy stations? As the default alchemy station works just fine...

Thanks!

I added the functions back and added aliases for them in that block, then modified the Low Level rule to use them again... but it still doesn't work and fails in the same way: even items that were in that Category already get relegated to Other instead. Nothing matches the modified conditions. I need to investigate that API call, what it's really supposed to do, its usage, and what data types it returns. It may not behave as I guessed it does. I know nothing of the data typing in LUA, but if I'm expecting integers and it's returning strings that aren't type-converted, then that could explain it. If it's entirely the wrong API call then that would also explain it.

I've asked for help elsewhere in the forum about that API function and data typing.

That should do the trick. You just want functions to return char level and char CP? I can add those in, I will probably push an update tonight or tomorrow.

No, I didn't! I didn't know about that section of code or what it does. After the failure I quickly backpedaled my addition. Looking at that code section, it's what my intuition whispered might be needed in addition to the function definitions themselves. It's establishing aliases of a sort, it appears.

I've added the functions back and added aliases for them in that block. Fingers crossed.

In addition to creating the new function, did you add an entry in AutoCategory.Environment at the end of that same .lua file? I started working on Set Tracker support tonight, and was able to get it working without much issue.

That isn't the discussion. The discussion is about a rule of this mod that doesn't work correctly, and my attempt to fix it, an attempt which happens to require some LUA and an API call. That might ultimately benefit from what you suggest as a supportive tactic, but it's not off-topic. The only and entire point is to make that rule function as intended.

Not to sound rude, but discussions about the inner working of LUA and development should generally go to the Lua/XML Help or General Authoring Discussion forum sections here on ESOUI, which exist specifically for that purpose, and not individual author's support threads.

You will probably find more feedback and useful support there.

My first attempt to use these, by modifying the Low Level filter, was a failure. It caused certain CP160 items to appear uncategorized as Other and did not have the intended effect. I suspect that my attempted functions are not even being recognized and trying to call them silently causes an error. The modified Low Level rule:
(The keepresearch() exclusion was an earlier modification to prevent low level research items from being snagged by this rule and never appearing as Researchable.)

How is data typed in LUA? A type mismatch could also be at issue. I have no specifics of the API function GetLevelOrChampionPointsString() or its proper use, only the function name and its arguments. For that matter, it could be the wrong function for the job entirely, since I have no documentation what it does.

The Low Level rule was always misleading for any character that isn't already veteran level. The addition of a character level test is crucial to making it applicable for any character and not just veterans. While many or all of my other many rule and precedence changes are a matter of personal taste, this one is not. If a means to add a character test to it can't be found, then I would recommend removing the rule entirely.

Honestly, I haven't attempted to add rules yet. I'll be digging into that soon because I want to add Set Tracker support. Give it a try though!

My intention was to show you what you can do about your suggestion to get it done. I proposed you a way to contact others. And believe me we are in contact and create library's where possible already since years.
You either need to respect this and if there is no library doing what you want already it's either not possible or Noone thought about it.
That's why I told you about the Gitter channel.

If you are not able to code, ok. You can try to learn it. If you're not interested, ok. But please don't blame the devs then. I think Phinix described it pretty well.
And forgive me if you thought it's sarcasm. You don't know me. I am this way, simple, direct. It was a kind of hint (source code, Gitter) why there is no such library which you have thought of.

But this got nothing to do with lone wolves. We are in contact, several devs on this and other channels

Is this about right to add new filter functions to return character level and CP?
If so, do I just add them to AutoCategory_RuleFunc.lua, or must they also be registered or declared elsewhere?

I agree about not discussing this here anymore. However, I think if most addon authors didn't believe in doing something for the sake of doing something that needs doing as you say, they probably wouldn't be posting all these cool free addons here. They would just make it for themselves and keep it to themselves. The fact they choose to share freely with the world shows by their ACTIONS they are pretty darned enlightened, if you ask me.

Another aspect of enlightened thinking is EMPATHY, and knowing how to treat others with respect and kindness in one's words and deeds. Whether we realize it or not, and whether it is even our intention, the way we come across often fails to convey this simple Golden Rule. Peace.