Repository navigation
[Resource Loader] Server resources and data packs in 1.3-1.12 - #114
Open
SpaceWalkerRS wants to merge 4 commits into
Open
SpaceWalkerRS wants to merge 4 commits into
SpaceWalkerRS wants to merge 4 commits into
Conversation
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
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.
datapacks/directory in 1.3-1.12/datapackscommand has been added in these versions yetServer Resources
Server-side resource loading works much the same as client-side resource loading. Server resources should be placed in
/data/<namespace>/directories, from where they will be loaded automatically. You can retrieve server resources through the server resource manager.Similarly, you can query all loaded data packs through the server pack repository.
Data Packs
Data packs will be loaded from the
datapacks/directory. Similarly to 1.13+, any data packs found will be enabled by default. At this time there is no/datapackscommand in 1.3-1.12 where users can control which data packs are enabled, but thelevel.datfile is extended to include lists or enabled and disabled packs, and packs can of course be enabled/disabled programmatically.Loot Tables, Advancements, and Command Functions
In 1.9-1.12 loot tables, advancements, and command functions, are loaded from the
data/directory. This is not changed, and resources discovered from there have precedence over resources loaded from data packs. In a way, thedata/directory acts as a data pack that is fixed at the top of the list.