Feature/templates #399
Open
Feature/templates #399
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.
Extension of #398 with block.properties templates
I started to hate PoTaTer, not only it has less base functionality then iProperties it also has stupid limitation with what it has
I need to finish iProperties to work with items and entities, then I would love to see an iProperties switch
The PoTaTer template file has 1406 lines and 1236 KB
iProperties template file has 1349 lines, but only 112 KB!!!
It has much less diuplicates of data, making the file: smaller and easier to manage. Adding new wood type support is as easy as adding if to a main wood types variable instead of searching for every sign, stair and everything else to add it manually