Account for newly-added entry in the rows of _assetmanifest files #10
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
|
So sad i saw this after fixing it myself but thanks |
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've found that the extractor is failing when it tries to assign a specific entry from any asset manifest's rows to a size variable. This worked fine in the past, but a recent update to Priconne's manifest row format added a new entry before that of the byte size, causing the extractor to throw the following error:
I've added a new allocation to the manifest scripts (the \src\manifests\ ones that assign each row's entries to something else). I've dubbed the entry "evertutocom" since the _assetmanifest files either use 'every', 'tutorial0/1', or 'common', but it could really be anything you want.