Core: apworld metadata and versioning #3809
Draft
+172
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this fixing or adding?
Adds the ability to include an optional metadata file that defines specific information about a given apworld. These include
Additionally, exposes the ability to require a certain world version from within a player yaml.
It should be noted that the ExportWorld.py is used (with permission) from @zig-for 's apworld manager with minor changes.
How was this tested?
Manually, via attempting to reach every codepath with customized metadata/yaml. No automated testing was added.
Opening as draft for additional testing and other missed locations (such as docs updates).
Some points of discussion:
min_generator_version
andmax_generator_version
If this makes graphical changes, please attach screenshots.
Example metadata: