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

The order in which items are shown in grid-loot will now depend on item type or its parameters. #1613

Merged
merged 2 commits into from
May 9, 2023

Conversation

GajuszZOrod
Copy link

Motivation: some items are likely to be always looted (e.g. gold, gems) and when looting is performed (usually automatically e.g. by Razor macros, but also manually by other players) it makes other items to move in a grid making it harder to browse their properties. Hence, items like gold should be at the end of the grid. Stackable items have no custom properties, so displaying them at the bottom of the grid is beneficial for players: it is more convenient to browse the loot and allows saving the time.

type or its parameters.
Motivation: some items are likely to be always looted (e.g. gold, gems)
and when looting is performed automatically (e.g. by Razor macros) it
makes other items to move in a grid making it harder to browse their
properties. Hence, items like gold should be at the end of the grid.
@GajuszZOrod
Copy link
Author

Please let me know in case if I need to raise an issue ticket first, in order to agree upon the feature implemented in PR.


y += gridItem.Height + 20;
if (it.IsLootable)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probably better to invert the if statement and continue [readability stuff]

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@andreakarasho andreakarasho merged commit 0ee9883 into ClassicUO:main May 9, 2023
3 checks passed
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.

None yet

2 participants