Open
Conversation
Member
|
No yaml files for the wage tables. In essence the wage table files will be similar to the jobs one, but in the end it will be a bit different on how it works internally. Each wage file will be json files with the main profession being the first table, then any other wage table specifics will be the tables beneath the main table just like the miner_wage.json |
This file contains hidden or 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
2 participants
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.
Misplaced the notes I took on the specifics of what you wanted to happen with the wage files. Think I remembered you mentioning making them mirror what the jobs configs are like. Couldn't remember if you wanted everything as a json or yml file in the end. Just did both for the lumberjack job as that is probs the shortest one.