You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In 4.40, HG removed the MissionBoardRewardOptions enum, so we have no clear way of knowing what each array item means. This specifically affects the DEFAULTREALITY.MBIN file, where this array is used.
Describe the solution you'd like
Hardcode the enum members back in, like we have done with other enums as well.
Additional context
Needs verification whether the array members actually correspond to the names we want to give them.
Here's a diff between 4.38 (left) and 4.43 (right) DEFAULTREALITY.EXML:
The text was updated successfully, but these errors were encountered:
For context, the reason they were removed is because the enum we hard-coded to be associated with this array became a few elements bigger, and so no longer was able to be used with the array due to the size mismatch.
So, could be added back in, BUT, oldschool style, would need to test what each enum element now does/changes, in order to hardcode labels back in for them.
Is your feature request related to a problem? Please describe.
In 4.40, HG removed the MissionBoardRewardOptions enum, so we have no clear way of knowing what each array item means. This specifically affects the DEFAULTREALITY.MBIN file, where this array is used.
Describe the solution you'd like
Hardcode the enum members back in, like we have done with other enums as well.
Additional context
Needs verification whether the array members actually correspond to the names we want to give them.
Here's a diff between 4.38 (left) and 4.43 (right) DEFAULTREALITY.EXML:
The text was updated successfully, but these errors were encountered: