PaperMC / PaperMC/Paper

Plugin worlds ignores data pack settings

Open
#13,111 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: needs triage
Dominant language
Java
Stars
12.7k
Forks
3.5k
Avg merge
3d 13h
Merged PRs (30d)
11

Description

Expected behavior

Setting cloud_height, natural, ambient_light and other settings described in https://minecraft.wiki/w/Dimension_type will apply to the corresponding world which is loaded by plugin via Server#createWorld.

Observed/Actual behavior

The JSON file is just ignored.

Steps/models to reproduce

Create a data pack which contain data/minecraft/dimension_type/test_world.json file.
Load a custom world w/ namespaced key minecraft:test_world using Server#createWorld (WorldType = NORMAL, Environment = NORMAL).

The World will load, but all settings from JSON file is just ignored.
But if you rename the file to overworld.json, then everything from it applies to main world w/o issues.

Plugin and Datapack List

Only test plugin which calls Server#createWorld and test data pack which contains valid JSON dimension_type file.

Paper version

Paper 1.21.8-60

Other

I'm not completely sure if this is a bug, but it will help me a lot if anyone can figure out this bug and fix it...
Thank you in advance for your time.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Server#createWorld entry point and trace how a namespaced dimension_type such as minecraft:test_world is resolved when the world uses NORMAL type and environment. Compare that path with the working overworld.json case and verify the data pack at data/minecraft/dimension_type/test_world.json is read. Done means the JSON settings apply to the custom world created by the plugin.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.