Sudden issues with worldgen datapack | Datapack Hub | Page 1

knotty flare Jan 8, 2025, 1:43 PM

#

Heya, so basically I have two blocks that are duplicated—aloe vera, to be specific. Both mods have worldgen JSONs that I can reference; but unfortunately, when I attempted to edit the JSONs, I get an odd "invalid player data" issue.
Here's what I've attempted so far:

Create my own configured feature data in data/mypack/worldgen/configured_feature (two files)
Replace the JSON data of the mod with the aloe which I want to replace in data/biomeswevegone/worldgen/configured_feature/aloe_vera.json
Replace the JSON data of the mod with the aloe that I want to spawn in data/biomeswevegone/worldgen/configured_feature (two files)
As for the error itself, it looks something like this:

[08Jan2025 08:30:42.954] [Server thread/ERROR] [net.minecraftforge.eventbus.EventBus/EVENTBUS]: Exception caught during firing event: Trying to access unbound value 'ResourceKey[minecraft:worldgen/configured_feature / bloomingnature:mangrove_swamp_cattails]' from registry net.minecraft.core.MappedRegistry$1@6fe64839

After which I immediately log out due to "invalid player data".

(on a separate note, I don't actually know why that feature in the log is erroring—it's a placed feature that I edited, not a worldgen one

also, I'm adding this data via KubeJS)

deft heathBOT Jan 8, 2025, 1:43 PM

#

knotty flare Heya, so basically I have two blocks that are duplicated—aloe vera, to be specif...

#

<@&1201956957406109788>

Someone will come and help soon!

💬 While you wait, take this time to provide more context and details.

🙇 If nobody has answered you by <t:1736345616:t>, feel free to use the Summon Helpers button to ping our helper team.

✅ Once your question has been resolved (or you no longer need it), please click Resolve Question or run /resolve

knotty flare Jan 8, 2025, 1:44 PM

#

Here's one of the two JSONs that I edited for the mod with the aloe that I want to generate:

{
    "type": "minecraft:random_patch",
    "config": {
      "feature": {
        "feature": {
          "type": "minecraft:simple_block",
          "config": {
            "to_place": {
              "type": "minecraft:simple_state_provider",
              "state": {
                "Name": "atmospheric:aloe_vera",
                "Properties": {
                  "age": "5"
                }
              }
            }
          }
        },
        "placement": [
          {
            "type": "minecraft:block_predicate_filter",
            "predicate": {
              "type": "minecraft:all_of",
              "predicates": [
                {
                  "type": "minecraft:matching_blocks",
                  "blocks": "minecraft:air"
                },
                {
                  "type": "minecraft:matching_blocks",
                  "blocks": [
                    "minecraft:red_sand",
                    "atmospheric:red_arid_sand",
                    "biomeswevegone:cracked_red_sand",
                    "biomeswevegone:red_quicksand"
                  ],
                  "offset": [
                    0,
                    -1,
                    0
                  ]
                }
              ]
            }
          }
        ]
      },
      "tries": 96,
      "xz_spread": 7,
      "y_spread": 3
    }
  }

#

Here's the JSON of the mod with the aloe that I want to replace:

{
    "replace": true,
    "type": "minecraft:random_selector",
    "config": {
      "default": "atmospheric:patch_short_aloe_vera",
      "features": [
        {
          "chance": 0.5,
          "feature": "atmospheric:patch_tall_aloe_vera"
        }
      ]
    }
  }

#

Oh wait a second

#

the configured feature of that one log that I posted doesn't exist

#

so then that means it's similar to the other ones

#

hmmm

#

now I'm having troubles just getting into a world, which might be unrelated to this

#

:////

#

alr I can make a new world and enter it no problem

#

Let me try one more thing...

#

YAY IT WORKED! But there's just one tiny issue

#

Right now, I'm replacing already-existing configured feature data (replacing Atmospheric and BWG). Atmospheric's aloe configured feature data is set to 96 tries, while BWG originally has 6 tries, as seen below. is it possible to create my own configured feature and replace BWG's?

#

I think before, my configured features weren't being detected before BWG's data was changed.

#

that's disregarding the bloomingnature error

short knot Jan 8, 2025, 2:22 PM

#

There's a lot here, I'm pretty lost

short knot Jan 8, 2025, 2:22 PM

#

knotty flare Right now, I'm replacing already-existing configured feature data (replacing Atm...

Yes, of course it's possible, that's what it sounds like you already did above

#

Make sure you're actually replacing configured features and placed features correctly. They are not interchangeable, and they are both worldgen files

knotty flare Jan 8, 2025, 2:23 PM

#

short knot There's a lot here, I'm pretty lost

I was encountering two different issues at the time of making the ticket lol

#

but I solved the one that was unrelated

short knot Jan 8, 2025, 2:23 PM

#

Ok

#

Well yes, you can replace/overwrite configured and/or placed features from a mod

knotty flare Jan 8, 2025, 2:24 PM

#

ah I shouldve been more clear

#

yeah I know I can replace already-existing data

#

but if I create a new configured feature, if I replace existing data to reference the brand new configured feature, will it detect it?

#

just found the answer to my own question

#

oop

#

thats a no

short knot Jan 8, 2025, 2:26 PM

#

If you make a placed feature reference a different configured feature, sure

#

I think the source of your confusion is a semantic one

#

You keep calling everything data, but not everything is data

knotty flare Jan 8, 2025, 2:26 PM

#

uhhhh

short knot Jan 8, 2025, 2:27 PM

#

You can replace an entire existing configured feature file, and have a placed feature reference that configured feature file instead of the original

knotty flare Jan 8, 2025, 2:27 PM

#

I'm referring to all JSONs under the data pathway when I mean data :p

short knot Jan 8, 2025, 2:27 PM

#

knotty flare I'm referring to all JSONs under the `data` pathway when I mean data :p

But that isn't a useful or meaningful distinction

#

Everything in a data pack is necessarily in that directory

short knot Jan 8, 2025, 2:27 PM

#

short knot You can replace an entire existing configured feature file, and have a placed fe...

You cannot make an existing configured feature file reference a different one for only some fields

knotty flare Jan 8, 2025, 2:28 PM

#

yeah right now here's my issue

#

gonna say it again in hopefully more clear terms

#

I'm creating two brand new configured feature files in data/mypack/worldgen/configured_feature, and I'm overwriting a configured feature file data/biomeswevegone/worldgen/configured_feature/aloe_vera.json to reference my two files

#

wait

#

WAIT

#

HOLD ON A SECOND

#

the configured feature is supposed to reference a placed feature????

short knot Jan 8, 2025, 2:30 PM

#

A configured feature file (at least, for most feature types" can't reference another configured feature

knotty flare Jan 8, 2025, 2:30 PM

#

OH

#

IM SO STUPID LOL

short knot Jan 8, 2025, 2:30 PM

#

A placed feature can (and typically does) reference a configured feature

#

As I've said thrice now

knotty flare Jan 8, 2025, 2:31 PM

#

what you said wasn't registering with me then

short knot Jan 8, 2025, 2:31 PM

#

🤷🏼‍♂️

knotty flare Jan 8, 2025, 2:31 PM

#

idk why or how but regardless

#

I now understand :p

short knot Jan 8, 2025, 2:31 PM

#

Ok

knotty flare Jan 8, 2025, 2:31 PM

#

ok so the solution here would be to create two NEW placed features to reference my configured features

short knot Jan 8, 2025, 2:32 PM

#

Yes

knotty flare Jan 8, 2025, 2:32 PM

#

then have aloe_vera.json reference the two placed

#

ok

#

got it

short knot Jan 8, 2025, 2:32 PM

#

But just making new places features won't make them spawn

knotty flare Jan 8, 2025, 2:32 PM

#

The aloe_vera.json configured feature is being referenced by other placed features within the BWG mod

#

or whatever

#

idk

short knot Jan 8, 2025, 2:33 PM

#

Yes, that would be required

#

It doesn't change what I said

#

If they aren't replacing/overwriting existing ones, you need to then reference those placed features in the biomes you want them to spawn in

#

Biomes list the placed features that can spawn in them which then references the configured features that they place

#

Biome -> placed feature -> configured feature

#

Have you checked out our worldgen guide?

knotty flare Jan 8, 2025, 2:34 PM

#

I have not

eager muskBOT Jan 8, 2025, 2:34 PM

#

Worldgen guides

About

Guide on making custom world generation using datapacks

Link

https://www.planetminecraft.com/blog/custom-world-generation-documentation/

knotty flare Jan 8, 2025, 2:34 PM

#

I'm just learning at each road block lol

short knot Jan 8, 2025, 2:34 PM

#

I strongly recommend it. Worldgen is a very interconnected set of files. It's very hard to learn just one thing, because most things reference or get referenced by other things in order to work as expected

knotty flare Jan 8, 2025, 2:35 PM

#

yeah seems to be very similar to structures in that regard

#

eghhgh

#

I'll make sure to check that out later, tyty!

deft heathBOT Jan 8, 2025, 2:36 PM

#

knotty flare I'll make sure to check that out later, tyty!

🎗️ Is your question resolved?

If your question is resolved, that's great to hear! Make sure to run /resolve or click the Resolve Question button. Otherwise, feel free to continue asking for help! :D

knotty flare Jan 8, 2025, 2:38 PM

#

Gotta test this out first to make sure it works 100%

#

IT WORKED! :D

#

Simply put two placed feature files referencing the configured feature files in data/mypack/worldgen/placed_feature, then I made the aloe_vera.json configured feature reference those placed features, and let the mod's other feature files handle the rest!!

#

Now, out of curiosity, before I close this ticket: right now, I put this as the code for the BWG biome mod's configured feature file:

{
    "replace": true,
    "type": "minecraft:random_selector",
    "config": {
      "default": "ourpack:patch_short_aloe_vera",
      "features": [
        {
          "chance": 0.5,
          "feature": "ourpack:patch_tall_aloe_vera"
        }
      ]
    }
  }

does this mean that there is a 50/50 chance for one of the placed features to be chosen for each try?

#

actually I'll just open up a separate ticket for this

deft heathBOT Jan 8, 2025, 2:57 PM

#

Question Closed

Your question, #1326546851209412679 (Sudden issues with worldgen datapack), was resolved!

Original Message

#1326546851209412679 message

Duration open

1h13m

#Sudden issues with worldgen datapack