-
-
Notifications
You must be signed in to change notification settings - Fork 205
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
Fix: Item Value Estimation Coloring #3061
Fix: Item Value Estimation Coloring #3061
Conversation
in the tooltip i dont think the "base item" should reflect recomb |
either add reforge name to the item name, then we can simply use the real item name again, or dont show recomb. |
unrelated: the data in the repo pr is used to move existing logic outside of live code. this is fine. but this has noting to do with this pr's title or description |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Im not very happy with this design change. I agree, before it was missing the recomb color entirely, and this was confusing as well, but at least the design was clear.
how about we add the display name of the item at the first line, then a empty line, then the base item + everything else? just for the estimated chest value, not touching the actual estiamted item value logic here.
additionallly, the changelog wording is not precise. this affects only the estimated chest value, not the estimated item value.
/** | ||
* Returns the item name with its full color, i.e. after recombobulation | ||
*/ | ||
val ItemStack.itemNameFullyRarityAware: String |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what is the difference between this and the display name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if the purpose is to remove the reforge name, maybe its better to have the function be called nameWithoutReforge
instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please also mention the "item calculation stuff moved to repo" part in the changelog/pr desc, as this is arguabily the bigger part of the pr
@@ -700,7 +700,7 @@ object EstimatedItemValueCalculator { | |||
} | |||
} | |||
|
|||
val name = internalName.itemName | |||
val name = stack.itemNameBaseRarityAware |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we dont want to show the recomb color here, and since the reforge name is also not part of the clean item name, i dont see why this line change is necessary
@@ -49,6 +50,9 @@ object EstimatedItemValue { | |||
var bookBundleAmount = mapOf<String, Int>() | |||
private var currentlyShowing = false | |||
|
|||
lateinit var itemValueCalculationData: ItemValueCalculationDataJson |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should be null, not lateinit. starting with a outdated repo will cause ugly errors instead of clean repo errors
Dependencies
What
Fixes an issue with items not showing their correct colors, both due to varying name, and recombobulation not being accounted for. If this was intentional let me know and I'll make it a config option.
Images
Before
After
Changelog Fixes