readme refresh 2 #1256
Merged
readme refresh 2 #1256
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
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.
This PR brings the project's README more in line with the current status.
The changes I've made are mostly in regard to the reality that we unfortunately cannot guarantee byte-for-byte matching binaries at this point in time. These parts of the README were written very early on in the project, when we didn't fully understand the concept of compiler entropy and were still under the assumption that having complete
LEGO1headers would guarantee identical binary output. Because of the uncertainness and complexity of the situation with the compiler, I have put a bigger focus on functional accuracy instead.I have also made changes to the
LEGO1.DLLstatus description now that the game is fully playable when built from our source code. As far as we know, there should be no more inaccuracies regarding save data either, so I have taken that part out.