Skip to content

Conversation

@artynova
Copy link
Contributor

Priority on non-static media holder items was incorrectly hardcoded to 40 instead of the ADMediaHolder constant, 4000, so phials were being targeted last instead of first.

Priority on non-static media holder items was incorrectly hardcoded to 40 instead of the ADMediaHolder constant, 4000, so phials were being targeted last instead of first.
Copy link
Member

@SamsTheNerd SamsTheNerd left a comment

Choose a reason for hiding this comment

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

seems like it will fix the issue on forge, however it still hardcodes it so that all phial-like items will have the same priority. This may be a good opportunity to expose getConsumptionPriority() as a part of MediaHolderItem, so that addons can more easily change the priority of phial-like items. Ideally it'd be defaulted to ADMediaHolder.BATTERY_PRIORITY so that we don't break existing items.

@object-Object up to you if you want to merge this in for the fix. I can do the API changes once I'm home and have some time to set up the hex repo locally.

@object-Object
Copy link
Member

let's do it separately. thanks for the PR @artynova!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants