Skip to content

Conversation

@acikek
Copy link
Collaborator

@acikek acikek commented Jan 5, 2024

For supporting usage over multiple events (see discussion in Discord)

@acikek
Copy link
Collaborator Author

acikek commented Jan 5, 2024

Also fix some stuff we missed in porting to 1.20.4

FabricLoader.getInstance().getModContainer(ID).ifPresent(mod -> {
ResourceManagerHelper.registerBuiltinResourcePack(ScatteredShards.id("test"), mod, ResourcePackActivationType.NORMAL);
ResourceManagerHelper.registerBuiltinResourcePack(ScatteredShards.id("bc23-assets"), mod, ResourcePackActivationType.NORMAL);
ResourceManagerHelper.registerBuiltinResourcePack(ScatteredShards.id("bc23-data"), mod, ResourcePackActivationType.NORMAL);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Synthetic respacks should be registered on the client side

Copy link
Collaborator

@falkreon falkreon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I definitely said in discord that there is an opportunity to load ShardTypes from data, but it needs to only happen for new worlds that have no ShardType data - otherwise data clobbers the (not-yet-extant) ingame editor, and that's no good. ShardTypeLoader should hold its own counsel about what the data-defined default types are, and only pour them into the server library if ShardLibraryPersistentState detects a fresh world / library and calls addDefaultShardTypes.

There are also quite a few extra diffs here that I don't understand the need for.

@acikek acikek merged commit b77bc61 into 1.20.4 Jan 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants