Skip to content

fix: trying to reset fields on potentially unadded skills from weapon#480

Merged
LordMidas merged 2 commits into
developmentfrom
fix-add-check-for-skill-added-before-resetting-fields
Dec 13, 2025
Merged

fix: trying to reset fields on potentially unadded skills from weapon#480
LordMidas merged 2 commits into
developmentfrom
fix-add-check-for-skill-added-before-resetting-fields

Conversation

@LordMidas

Copy link
Copy Markdown
Member

Non-stacking skills are not added to a skill_container that already has a skill with that ID. So if a weapon tries to add such a skill, it will not get added to the container. Therefore, we add a guard statement and return early in this case.

Non-stacking skills are not added to a skill_container that already has a skill with that ID. So if a weapon tries to add such a skill, it will not get added to the container. Therefore, we add a guard statement and return early in this case.

@TaroEld TaroEld left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Should the same not be done for the equivalent shield hook?

@LordMidas LordMidas requested a review from TaroEld December 13, 2025 19:20
@LordMidas LordMidas merged commit 1049b73 into development Dec 13, 2025
@LordMidas LordMidas deleted the fix-add-check-for-skill-added-before-resetting-fields branch December 13, 2025 19:24
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.

[BUG] Duplicate Item-Granted Skill skips setContainer, triggering MSU reset warnings

2 participants