JSON Mappings#47
Merged
Merged
Conversation
onebeastchris
approved these changes
Dec 20, 2025
Novampr
force-pushed
the
feat/mappings_abstraction
branch
from
c00da11 to
5bed685
Compare
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.
Turns TextureMappings into JsonMappings which abstracts this system out to allow other asset types to take advantage of the JSON mapping system. This also brings some nice changes which makes working with the mappings easier, notibly, the JSON mapping is "compiled" before hand, which means while the JSON can have objects, at the end, you just need to input a path:
{ "block": { "test": "success" } }turns into
{ "block/test": "block/success" }For textures, the sub directory changing is handled after the fact still (
block->blocks), so this has been handled.