-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
Distribute collective resources in scenario rewards #456
Labels
enhancement
New feature or request
Comments
Totally makes sense! Will add this! |
Should be implemented in v0.83.6. |
Lurkars
added
to test
Should be fixed, but needs proper testing
and removed
in progress
Currently working on this
labels
Dec 9, 2023
It is possible in its current implementation to distribute more resources than rewarded if you type in a number. This could cause some issues with negative numbers if distributed more than is available in frosthaven supply. |
Thanks for noticing this. Should be fixed in v0.83.7. Happy if you can test again. |
Fixed. |
rdoll
pushed a commit
to rdoll/gloomhavensecretariat
that referenced
this issue
Dec 31, 2023
…Lurkars#455, Lurkars#456, Lurkars#457, fix scenario data, fix item rewards
rdoll
pushed a commit
to rdoll/gloomhavensecretariat
that referenced
this issue
Dec 31, 2023
rdoll
pushed a commit
to rdoll/gloomhavensecretariat
that referenced
this issue
Dec 31, 2023
rdoll
pushed a commit
to rdoll/gloomhavensecretariat
that referenced
this issue
Dec 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
After finishing a scenario including collective resources in the scenario rewards, these resources can be distributed among the players or put in the frosthaven supply. These resources are now automatically put in the frosthaven supply. Maybe there could be an option to distribute these among the players in the scenario summary screen.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
No response
The text was updated successfully, but these errors were encountered: