[Bug] CustomOre not generating with cofh

Question

[Bug] CustomOre not generating with cofh

Slater022 opened this issue 8 years ago · 15 comments

Slater022 commented 8 years ago

with this config :


{
  "populate": {
    "osmiumVein": {
      "distribution": "uniform",
      "generator": {
        "block": [
          {
            "name": "base:osmium.ore",
            "weight": 50
          },
          {
            "name": "base:osmium.poor_ore",
            "weight": 50
          }
        ],
        "material": "stone",
        "cluster-size": 17
      },
      "cluster-count": 20,
      "min-height": 0,
      "max-height": 128,
      "retrogen": false,
      "biome": "all",
      "dimension": {
        "restriction": "blacklist",
        "value": [
          -1,
          1
        ]
      }
    }
  }
}

Not working at all ^^"

SkySom · Answer 1 · 2017-04-10T18:37:55.000Z

http://teamcofh.com/docs/cofh-core/features/custom-world-generation/#template-types
According to this, the issue is with your script. You need minHeight/maxHeight, not min-height/max-height

Slater022 · Answer 2 · 2017-04-10T18:41:01.000Z

Wrong : According to the 1.10 wiki :
https://github.com/CoFH/cofh.github.io/tree/1.10-updates/docs

No more Camelcase ...

covers1624 · Answer 3 · 2017-04-10T18:42:36.000Z

The wiki is currently being updated and basically everything has been moved from "cammelCase" to "snake-case"

Slater022 · Answer 4 · 2017-04-10T18:43:41.000Z

Example of working file :
https://pastebin.com/GWifHATY

Result :

SkySom · Answer 5 · 2017-04-10T18:44:57.000Z

Fair enough, but still it's the script failing to parse? I'm not sure how this is our issue?

Slater022 · Answer 6 · 2017-04-10T18:47:25.000Z

I think that is the name of the block : you use base:osmium.ore, for railcraft for example it's :
"name": "railcraft:ore",
"metadata": 5

Can't try with base:osmiumore for example. it's maybe the dot that cause the parsing to fail

SkySom · Answer 7 · 2017-04-10T18:49:29.000Z

Well yes you can't try with base:osmiumore, because that's not it's registry name.

Slater022 · Answer 8 · 2017-04-10T18:53:46.000Z

Exactly what i'm saying xD the problem can came from the registry name ^^

SkySom · Answer 9 · 2017-04-10T18:54:26.000Z

So if you replace the name (With some other random block) in the erroring script, does it work

Slater022 · Answer 10 · 2017-04-10T19:01:33.000Z

yep :


{
  "populate": {
    "osmiumvein": {
      "distribution": "uniform",
      "generator": {
        "block": [
          {
            "name": "minecraft:redstone_ore",
            "weight": 50
          },
          {
            "name": "minecraft:lapis_ore",
            "weight": 50
          }
        ],
        "material": "stone",
        "cluster-size": 17
      },
      "cluster-count": 20,
      "min-height": 0,
      "max-height": 128,
      "retrogen": true,
      "biome": "all",
      "dimension": {
        "restriction": "blacklist",
        "value": [
          -1,
          1
        ]
      }
    }
  }
}

Slater022 · Answer 11 · 2017-04-10T19:42:16.000Z

Custom ore gen say me that :
------ Error Message ------

java.lang.IllegalStateException: Ore block descriptor for vnlaOsmiumVeins is empty or does not match any registered blocks.
with the block : "<OreBlock block='base:osmium.poor_ore' weight='1.0' />"

Lanse505 · Answer 12 · 2017-04-10T19:43:36.000Z

We're dealing with the bug atm, please do not open up issues or poke people about it unless sufficient time has elapsed. We're working as fast as we can to resolve the issue so please be patient.

Lanse505 · Answer 13 · 2017-04-10T18:17:58.000Z

Could you post your latest log so I could have a look?

Slater022 · Answer 14 · 2017-04-10T18:30:21.000Z

Yes :

[20:30:52] [Server thread/INFO]: Found 3 World Generation files and 0 folders present in C:\Users\Touhma\WebstormProjects\callistopack\config\cofh\world.
[20:30:52] [Server thread/INFO]: Reading world generation info from: cofh\world\vanilla.json:
[20:30:52] [Server thread/INFO]: Finished reading cofh\world\vanilla.json
[20:30:52] [Server thread/INFO]: Reading world generation info from: cofh\world\vanilla_poor.json:
[20:30:52] [Server thread/INFO]: Finished reading cofh\world\vanilla_poor.json
[20:30:52] [Server thread/INFO]: Reading world generation info from: cofh\world\vanilla_regular_gems.json:
**[20:30:52] [Server thread/ERROR]: Invalid block entry!**
[20:30:52] [Server thread/WARN]: Invalid generator for 'osmiumvein'!
[20:30:52] [Server thread/WARN]: Template 'uniform' failed to parse its entry!
[20:30:52] [Server thread/ERROR]: Error parsing generation entry: 'osmiumvein' > Please check the parameters.
[20:30:52] [Server thread/INFO]: Finished reading cofh\world\vanilla_regular_gems.json
[20:30:52] [Server thread/INFO]: [Touhma: Successfully reloaded World Generators.]
[20:30:52] [Client thread/INFO]: [CHAT] Successfully reloaded World Generators.

For the short version :)

For the complete :
https://pastebin.com/11r9q1rs

COFH_core : CoFHCore-1.10.2-4.1.1.156-universal

SkySom · Answer 15 · 2017-05-31T14:14:53.000Z

Closing this, as there's no real way to change the . to a _ without breaking prior registry names for V1, feel free to try with the new V2 of Materials that is now part of ContentTweaker. See https://github.com/The-Acronym-Coders/ContentTweaker/wiki/Materials-V2-Test for an example.

Share to