Skip to content

Conversation

BunkBunker
Copy link
Contributor

When someone updated the yaml to match 0.6.1 they did not update the missions properly. I personally submitted a custom SA2B last time so I didn't notice. This has allowed missions that were not enabled in previous Big Asyncs to be turned on. I have adjusted the yaml to be in line with what the previous settings were supposed to reflect

When someone updated the yaml to match 0.6.1 they did not update the missions properly. I personally submitted a custom SA2B last time so I didn't notice. This has allowed missions that were not enabled in previous Big Asyncs to be turned on. I have adjusted the yaml to be in line with what the previous settings were supposed to reflect
@ScootyPuffJr1
Copy link
Collaborator

Near duplicate of #296. Which is better?

@BunkBunker
Copy link
Contributor Author

Mine more accurately matches what the mission distribution was before the update to 0.6.0

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.

2 participants