Split player functions into appropriate .inc files #47
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.
The map file indicates where certain file splits are and the fact that these are source-included.
The ".inc" suffix comes from strings that are present in asserts:
.string "d_a_player_dproc.inc".string "d_a_player_bow.inc".string "d_a_player_hook.inc".string "d_a_player_fan.inc".string "d_a_player_hammer.inc".string "d_a_player_sword.inc"The rest of the inc file names are created by me. But thankfully all the functions have common naming schemes that makes it very easy to figure out what it likely was :)
Each inc file has a block comment at the top that explains whether or not the filename is original or made up