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

[Bug Fix] Bandolier didn't recognize source weapon on cursor #2026

Merged
merged 2 commits into from
Mar 7, 2022

Conversation

noudess
Copy link
Contributor

@noudess noudess commented Mar 3, 2022

If you activated a bandolier set and one of the source weapons was on your cursor, the code didn't see it.

For whatever reason, m_inv.GetItem(EQ::invslot::slotCursor)->GetCharges() was returning 0 when the source weapon was on the cursor, bypassing the code that was written to handle this case.

@noudess noudess requested review from Uleat and KimLS March 3, 2022 19:52
@mackal
Copy link
Member

mackal commented Mar 4, 2022

I guess we should figure out why cursor slot returns 0 here, I would assume that's not right :P

@noudess
Copy link
Contributor Author

noudess commented Mar 4, 2022

I guess we should figure out why cursor slot returns 0 here, I would assume that's not right :P

I agree. I don't know what's going on there. Should we not merge this? I feel like maybe this spot doesn't need the check since we know the item is there, so maybe this is ok anyway.

@mackal
Copy link
Member

mackal commented Mar 4, 2022

I guess we should figure out why cursor slot returns 0 here, I would assume that's not right :P

I agree. I don't know what's going on there. Should we not merge this? I feel like maybe this spot doesn't need the check since we know the item is there, so maybe this is ok anyway.

no, but maybe we should add a TODO comment noting that we had to remove it, just so someone doesn't have to look through commit history/PRs to find discussion about it

@noudess
Copy link
Contributor Author

noudess commented Mar 4, 2022

I guess we should figure out why cursor slot returns 0 here, I would assume that's not right :P

I agree. I don't know what's going on there. Should we not merge this? I feel like maybe this spot doesn't need the check since we know the item is there, so maybe this is ok anyway.

no, but maybe we should add a TODO comment noting that we had to remove it, just so someone doesn't have to look through commit history/PRs to find discussion about it

Normal comment or do we have an agreed upon keyword to key on for TODO items?

Added comment, let me know if it looks ok.

@Akkadius Akkadius merged commit c4eb1f8 into EQEmu:master Mar 7, 2022
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.

4 participants