Prepared a builder process for generate the packs directly from the project #283
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
# Conflicts: # README.md
|
I think this is an excellent idea and has been something that I have been meaning to revisit after my original attempts to automate the creation of |
|
Closing due to how old this pull request is. |
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.
DO NOT MERGE THIS YET
So I wasted some time doing the javascript process that creates the packs directly from the project files. This should speed up the release process.
The script works even if a bit crude and is limited for now only to the 5e folder.
The description of the process and the setting can be found in the readme of this PR.
This is just to give you an idea, but I think it is something to be taken into consideration.
Let me know .