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

Fix rare bug affecting allocating imported cluster nodes #6701

Merged

Conversation

Wires77
Copy link
Member

@Wires77 Wires77 commented Sep 16, 2023

Description of the problem being solved:

Mastery nodes always get and index of 0. Some nodes on cluster jewel could also have an index of 0. Rarely, if Lua happened to iterate through the nodes and reached the mastery node first, it'd try to allocate it and fail, exiting the loop entirely. Imported nodes should never contain a mastery node for a cluster jewel, so this check was just checking the wrong node for if it's a mastery or not. This PR corrects that change.

Steps taken to verify a working solution:

Link to a build that showcases this PR:

No link applicable, because it only happens on character import. This was one example, but you may have to ask them to reallocate nodes, as their character has changed since testing: gladvold -> diyu_chiefGoBoom

@Wires77 Wires77 added the bug: behaviour Behavioral differences label Sep 16, 2023
@LocalIdentity LocalIdentity merged commit bc2f756 into PathOfBuildingCommunity:dev Sep 17, 2023
shafouz pushed a commit to shafouz/PathOfBuilding that referenced this pull request Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug: behaviour Behavioral differences
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants