Adding some settings to the dimension.json, like a structure list, gives an error. Here is the error that I had on the console register:
No key name in MapLike[{"structures":{"structures":{"minecraft:jungle_pyramid":{"spacing":15,"separation":4,"salt":14357619},"minecraft:endcity":{"spacing":10,"separation":5,"salt":10387313},"minecraft:village":{"spacing":15,"separation":4,"salt":10387312},"minecraft:ruined_portal":{"spacing":20,"separation":7,"salt":34222645},"minecraft:igloo":{"spacing":15,"separation":4,"salt":14357618},"minecraft:stronghold":{"spacing":1,"separation":0,"salt":0},"minecraft:bastion_remnant":{"spacing":15,"separation":2,"salt":30084232},"minecraft:desert_pyramid":{"spacing":15,"separation":4,"salt":14357617},"minecraft:nether_fossil":{"spacing":2,"separation":1,"salt":14357921},"minecraft:mansion":{"spacing":20,"separation":5,"salt":10387319},"minecraft:shipwreck":{"spacing":10,"separation":2,"salt":165745295},"minecraft:monument":{"spacing":15,"separation":2,"salt":10387313},"minecraft:swamp_hut":{"spacing":15,"separation":4,"salt":14357620},"minecraft:fortress":{"spacing":15,"separation":2,"salt":30084232},"minecraft:pillager_outpost":{"spacing":15,"separation":4,"salt":165745296},"minecraft:ocean_ruin":{"spacing":10,"separation":4,"salt":14357621}}}}]
I will provide the datapack that I used for this. Also tested this on 20w28a, but it gave more errors than 20w29a, I don't know why.
Attachments
Comments 8
Can confirm this error in 20w28a and 20w29a, as well as with sliced_lime's example code, both tweaked and left unchanged.
This error can easily be fixed by including a "name" tag within the "settings" field of the json file e.g. "name": "custom_dimension" or "name": "custom_settings".
"settings": {
"name": "white_concrete_forest",
"structures": {
"stronghold": {
"distance": 32See my comment in bug report MC-195871 for ressolving this error with configured features.
Ok, I realized that the way that the noise parameters were working changed in 20w29a. On 20w28a they worked fine if the were put on the dimension.json, but in 20w29a Mojang added a new settings on the worldgen folder called "noise_settings", which is used on 20w29a and 20w30a to put those parameters on a different json instead of putting them on the dimension.json . So it seems that with the lack of information that mojang provided of those changes, me and some people misunderstood the errors that we get due to new changes as a bug. Also there is a "bug" that is related on the comments below, which is caused by not putting a new parameter called "name", that it placed under the "settings:" (basically another lack of information of new changes) on certain .json of a datapack.
So yes, basically those "bugs" aren't bugs since they were caused byt he things I related below. Then this report should be marked as "invalid".
(Also it would be nice that mojang let us know possible future changes like this, as doing that will prevent reporting bugs that are a misunderstood, like this).
So for a custom feature modeled after the vanilla pile_hay, where would the "name": "pile_hay" go, since the json has no "feature":{ section in which to add name:?
Thanks.
{
"config": {
"state_provider": {
"state": {
"Properties": {
"axis": "y"
},
"Name": "minecraft:hay_block"
},
"type": "minecraft:rotated_block_provider"
}
},
"type": "minecraft:block_pile"
}
I tested a datapack that slicedlime made but also it don't seems to work on 20w29a and 20w28a. I used exactly this in the dimension.json: https://github.com/slicedlime/examples/blob/master/so_lime.json (it still gives an error related with the settings)