Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Library updates, include FlameLeviathan bonus itemlevels + Herald Check in character sheet #246

Merged
merged 10 commits into from
Feb 25, 2023

Conversation

Road-block
Copy link
Collaborator

@Road-block Road-block commented Jan 17, 2023

As seen on the commit list for this pull request it already includes the work done in develop branch by Tanner up to this point.

Additions on top of that include

  • using the computed averageitemlevel and cache of libgearscore and only falling back to groupie own ilvl/cache implementation if that's not available for some reason
  • adding flameleviathan (vehiclescore) and herald check to character sheet and adjusting appearance
  • adding a tooltip that shows on mouseover what message the LFG button will send if pressed.
    LFGButtonTooltip
    CharacterSheet

@Gogo1951
Copy link
Owner

Let's do this without the Tooltip changes. The {rt3} Looks ugly in the tooltip. Nobody should ever see that written that way. @TannerShmoog @Road-block

@Gogo1951
Copy link
Owner

Also what is the "Leviathan 91" I don't get the 91 part.

Let's leave Levithan and Herald out... seems like something that's better left to weak auras.

@Road-block
Copy link
Collaborator Author

91 is the itemlevels above baseline for vehicles. The players that care about optimizing for vehicle encounters (like Flame Leviathan) will know what it represents. 😄
Alternatively the library also can provide a percentage increase (in vehicle health or ability damage) which might be more user friendly.

@Road-block
Copy link
Collaborator Author

Road-block commented Jan 18, 2023

About the tooltip hint.
Personally I don't like user elements that are opaque in function, ie I can only understand what they do after I already used them.
The target charm escape sequence can be stripped if that's the problem, but I don't think [LFG] lets the player know what the button does. [Respond] / [Reply] ? I could guess this button will send a message if that was the label. [LFG] tells me nothing about what it does.

The first time I hit it I thought it was going to do a C_PartyInfo.RequestInviteFromUnit()

@Road-block
Copy link
Collaborator Author

I am just explaining the motivation btw, I'm fine with cherry picking anything that aligns with the design and leaving other stuff out 👍🏻

@Road-block
Copy link
Collaborator Author

Road-block commented Jan 18, 2023

Does this make more sense for the vehicle?
"Forgot to equip pants"
Levi1
No longer being pants
Levi2

That's how people are going to use it to optimize their kit for vehicles.

@Gogo1951
Copy link
Owner

Gogo1951 commented Jan 18, 2023

It's fine, you're probably the last person left using this. Might as well get what you want. (=

Beggars can't be choosers. There's stuff I wouldn't agree with, but at the end of the day however it gets done, it gets done. I'm not helping this add-on sticking around.

@Gogo1951
Copy link
Owner

% are better. And it's all vehicles, so better to say "vehicle" vs leviathan. So like drakes in Occ, and Eye. Yeah?

@Road-block
Copy link
Collaborator Author

% are better. And it's all vehicles, so better to say "vehicle" vs leviathan. So like drakes in Occ, and Eye. Yeah?

Mostly correct and yes I had my internal dialog about "Vehicles:" instead of Leviathan. It's more future proof.

Would this be more acceptable as a tooltip hint? (color coded by the chattype and with marker placeholders stripped.
Clipboard 1

Again I'm fine with this being left out, I interpreted the critique as "it's ugly" not "it's useless" 😝

@Road-block Road-block merged commit 81e3046 into Gogo1951:main Feb 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants