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)
Nevermind, I just discovered that the files require to be placed on a folder called "minecraft". I thought that it was broken because of a missunderstood with putting the .jsons on different folders. It works.
Still waiting for a response of the last comment...
Okay, thanks
Can someone take a look at this again? I updated the description and added a video evidence, as I think that this was misunderstood with a relative issue.
Since I saw that his bug was categorized as "Works as intended", I uploaded a video of the issue as I think that it still doesn't have any sense, so maybe this could have been misunderstood with some relationed issues.
Violine1101 no, in 1.15.2 I get damaged as I think it's supposed to work.
This bug is not caused by this behavior, but maybe it's very likely to be confused with it. I just shooted one arrow as fast I could and it just pierce me without any damage. I wans't taking any damage so I doubt that it is related with that behavior.
Yes, it just happened to me.
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).