Bio scan tracking and codex entries #2568
Closed
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
|
Needs rebasing and finalizing. |
bcthund
force-pushed
the
feature/2212_exobiology_enhancements
branch
from
6dc6d91
to
49c66b3
Compare
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.
Added a basic and functioning system for scanning biologicals and keeping track of how many samples and total are left to scan on the planet. Also keeps track of distance from previous samples to assist in not violating previous sample range. Codex information added for biologicals and so the CodexEntry event was also implemented to make use of this data. Descriptions are all currently hardcoded in english.
Resolves #2212
Looking at ticket (#2455) it suggests putting the biologicals into the Body object. When I first started I wasn't sure how to access it but I think I understand it now.It is also constantly polling latitude and longitude and enqueueing events but there is probably a cleaner internal way to handle this. It was difficult to figure out a way to calculate distances from within the cottle script and is not completely accurate, but very close.