#Worldgen Datapack Issue

15 messages · Page 1 of 1 (latest)

hazy fulcrum
#

I hate worldgen stuff sadcat

frozen mothBOT
#

Once your ticket has been resolved, please close it with </ticket close:1054771505520717835> command!

hazy fulcrum
#

basically I created my own configured features and put them in kubejs/data/ourpack/worldgen/configured_feature, made sure they were all correct and stuff, then overwrote another mod's configured feature in the file path kubejs/data/biomeswevegone/worldgen/configured_feature/aloe_vera.json, which cited my configured features

#

This is one of the two custom configured features

{
    "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
    }
  }

This is the configured feature I attempted to overwrite

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

sounds like I might need the Cyanide mod 😭

#

I tried overwriting the files from which the aloe JSON originates instead of creating a new filepath using my modpack name, aaaaaand same thing

#

.._..

cedar geode
#

look in data/minecraft/worldgen/placed_feature. what/where is ourpack:patch_short_aloe_vera value being set?

#

oh wait ok you have a configured feature but no placement feature for ourpack, minecraft cannot find it

#

data/ourpack/worldgen/placed_feature/patch_short_aloe_vera is required for what you have referenced in data/minecraft/worldgen/placed_feature

#

worldgen / datapack stuff is easy once you understand how to use.

hazy fulcrum
#

I was using a mod's worldgen as reference, so I thought the configured feature file was referencing other configured features, not placed features

#

hence the second JSON

#

then I learned you can just do this with placed features:

{
    "feature": "ourpack:patch_short_aloe_vera",
    "placement": []
  }