Prevent placed features from generating

[edgy basin]

I'm trying to prevent PHC2 from generating trees in the world. I've made other data packs that prevented structures from generating, but I don't know how to deal with placed/configured features. I'm on version 1.20.1

[worn verge]

Overwrite those placed features so they just have a single placement modifier that sets the count to 0

[edgy basin]

Like this?

{
  "feature": "pamhc2trees:acorn",
  "placement": [
    "count" : 0
  ]
}

[worn verge]

Close, I recommend using Misode

[edgy basin]

I have no idea how to use that lmao

That's a very nice tool goddamn

it still wont work, even though it looks right and everything

  "feature": "pamhc2trees:template",
  "placement": [
    {
      "type": "minecraft:count",
      "count": 0
    }
  ]
}```
And I'm using a script to replace template with the name of the tree for all the files

Still getting a datapack error

@worn verge is there any reason it would fail to validate?

also is pinging discouraged here?

[worn verge]

If you did it wrong

[worn verge]

Just please don't be frivolous about it

[edgy basin]

Well yeah, but I did it the way you said it

[edgy basin]

Is this not what it should look like?

[worn verge]

You made this modification the way I said, but you may have affected something else

[worn verge]

The file contents are correct assuming that configured feature it's referencing actually exists

You need to check logs

[edgy basin]

does it log whenever you fail to validate a datapack? right now I'm creating a new world with the datapack in it to see if there are no trees

[edgy basin]

I've got the mod installed so they should exist no?

[worn verge]

Seems like you changed it from acorn to template, so if there is no feature called template, then that would cause a validation error

[edgy basin]

It doesnt say that in the files, i'm using a python script to change that word to the kind of tree I need

[worn verge]

No I told you to check the logs because it doesn't show any errors in logs when you fail to validate a data pack.

Yes, it will show there

[worn verge]

Okay, well I can only comment on what I can actually see, so

[edgy basin]

You're right my bad

@worn verge I got the error. If you search for "guava" the error starts there

[worn verge]

I don't recommend using the latest logs, you should just look at the live logs window

[edgy basin]

Like when using Prism? I can copy it out of there

[worn verge]

Gonna be way easier to see the relevant error, and you can just copy over the non-indented lines

Like when using any client that includes a live window of the logs

[edgy basin]

Sorry for the silly questions, I like confirmation

[edgy basin]

Here ya go:

[worn verge]

Yeah I mean this reads pretty simply as the configured feature pamhc2trees:guava not existing

Or itself is failing to validate for another reason

[edgy basin]

strange, because I'm pretty certain there's a gauva tree, but I'll check that now

If it's for some other strange reason how would you go about figuring that out?

[worn verge]

Well I can't really speak to hypothetical problems that would cause phantom errors, because that's not a thing

We have an error here that is telling us what the problem is. It wouldn't be wrong or lying

[edgy basin]

I just checked, all things gauva are in the files and in-game

I decompiled the mod and gauva is in the configured feature folder, and guava_placed is in the placed feature

[edgy basin]

I'm aware, but clearly it's not seeing the guava tree for some reason even though related files are present in the mod files

[worn verge]

I can only interpret what the error is telling us

Sorry

[edgy basin]

Maybe they have the files but just forgot to include anything that actually generates them, could that be what happened? Maybe the trees already don't generate?

[worn verge]

That wouldn't produce this error

You can certainly try removing your guava placed feature and see what happens

[edgy basin]

That's what I'm trying to, remove all the trees, and for some reason that one is throwing an error

If the files are there for it, why would it throw an error? Would it not throw an error for the other trees as well if it were the same issue?

Omg, I see what the problem is

@worn verge, it was a classic kind of error, they misspelled guava as gauva in the files

good thing I noticed that

[worn verge]

Which is another way of saying there is no configured feature called guava 🙂

[edgy basin]

I'll close this if/once the datapack works

[edgy basin]

yeah, just gotta change it to gauva for the mispelling