INVESTIGATING-

RESOLVED-

Problem has been resolved in v1.31 (which is pending review, should be up by tomorrow.)

Thanks for being patient

I will update the text to be more accurate/correct.

What you would want to do is enable both settings to display both names. The second option (display player name) is a complement to the first option (display char name). At the time of implementation LibAddonMenu-1.0 (and possibly LAM2 as well) was not advanced enough to toggle the availability of one option based on the state of another, in a perfect world I would have the second option disabled unless the user enabled the first option.

TL;DR?

1. If the first option is disabled, the second option is ignored.
2. If the first option is enabled, the second option is evaluated.
3. If both options are enabled, both the character name and the player name should appear in guild chat.

I'll address this and two other options related "UX bugs" in the future. In the meantime it should be workable per the above, and I'll update the descriptions for clarity.

Well, I've poked at this as much as possible, seems to work for me. Changes always save, and abbreviations appear in chat output when I enable the option. This was recently fixed, I verified the current download matches what I have in source control (and locally) and it matches. If you're using the current version and it's not working you may need to wipe the savedvars file for the Chat addon (only), beyond that I'm stumped.

Hmm, no. I went through and found a bug, fixed it, verified the saving. I hate to think somehow I managed to miss something, but there isn't anything else you need to do to persist settings. You do have to enable the guild abbreviation option for guild names to appear abbreviated in chat, but I don't believe that's the issue here to be honest.

I'll take another look tonight after work and get it fixed.

Thanks.

Nope, communication is key to improvement. Plus, for every one question someone asks, there are 10 other people who had or will have the same question. Everyone wins.

Intentional, I try and work out default configs that fit my intentions and also make sense (or are at least recoverable and obvious, in the case of laundered goods you can sell them to recover the launder expense, and then change the patterns.)

Examples of your "For Keeps" patterns could be:

MOTIF
motif.*primal
RECIPE

These "upper case" tokens are matching the "Canonical identifiers" (which are not localized in ESO) used in Lua. For example; in ESO UI there is a Lua constant "ITEMTYPE_RACIAL_STYLE_MOTIF" and you only need to include the string "MOTIF" (since motifs have their own item type).

If you wanted to match against the "item name" (which may be localized depending on your ESO client), or a portion of the item name, you would want to use "lower case". In the example above I have a pattern "motif.*primal" which will match all primal motifs. In this case it is matching by name.

There are other special identifiers including L## for item level, STOLEN for stolen items (it always appears first when performing matching.)

EDIT: I took a look at this and could not reproduce the issue.

Will look for this as well, sounds strange, but I won't assume anything.

Thanks!

WILL FIX- Chat and Guild Abbreviations

Not by design, no. Should stick until you change it again.

I went through and switched Chat addon over to use the 'new' shared settings code last week, looks like I goofed on the abbreviations settings and a typo is preventing them from saving. I'll have a fix up later today, and will take a moment to review all the settings code for all the addons when I do (to make sure I didn't make the same mistake elsewhere.)

Thanks again