Provide extra information YAFC now requires. #58
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shpaass
added a commit
to shpaass/yafc-ce
that referenced
this pull request
Nov 18, 2024
This is some more parts of #316. I think it covers all location information required by dependency/milestone analysis, except space-connections (which don't add any additional unlocks): It knows that lava isn't accessible until you get to Vulcanus and knows that Promethium science pack is accessible. It is happy loading new and existing pY and SA projects, though the pY projects [need a change to pypostprocessing](pyanodon/pypostprocessing#58). In order to not break Space science when fixing Promethium science, I had to implement these, both internally and in the UI:   The vertical bar will connect as many horizontal OR bars as necessary. Lists that are not separated by an OR bar (almost all of them) use the standard AND behavior. I also decided this (1364 pixels high) was bad  and changed it to this instead (down to 970 px) 
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I just made a PR in YAFC that means it now needs to know what surfaces each entity can spawn on. This change provides enough information that YAFC can correctly spawn pY entities.
controls that give more accurate information about spawning density might be preferable, but YAFC doesn't currently handle that information.