#Lava Geode Stack Not Placing?

1 messages · Page 1 of 1 (latest)

spiral raven
#

Hi, all, again. I have my marker block spawning for my feature stack. I'm trying to get my "geode" to spawn but I am encountering some issues.

Problem is, I don't know what the issue that's preventing it from spawning is. I did check the error log for this, but there's no errors listed, so I've come here. I've attached screenshots of the relevant files to help.

I've tried block columns and simple blocks as well, so I know it's probably not the type of feature that's the issue.

I did get disks working the other day, so I'm not certain why I'm having trouble here.

spiral raven
#

I've also referred to my previous thread with stacking features, and unfortunately I can't figure out from it what went wrong here.

hasty cove
#

It's a lot to parse through, but some areas that catch my attention:

  • Your biome seems to list the geode feature, not the vegetation patch feature that places the geode
  • Your placed feature for the vegetation patch is whack. You should know where the marker block is, so you don't need 20 spawn attempts per chunk and you don't want it to project to a heightmap. You want it to generate right below that marker block's position with a height range placement and a biome placement
  • Geode features consider the location of their spawn attempt to be their lowest coordinate corner, not the center. So if you want it to be kinda in the ground, you need to use a random_offset placement after the heightmap to move it on the negative Y axis
spiral raven
#

It is a bit confusing but "place_inc_exp_lava_geode" calls "inc_exp_lava_geode_veg", which is the vegetation patch. The veg patch calls "inc_exp_lava_geode", which is the custom geode feature. I hope that's the correct order...?
I had the 20 spawn attempts for testing purposes to make sure it could spawn. 😅 Would the existing geode feature conflict with it?

you need to use a random_offset placement after the heightmap to move it on the negative Y axis
That's in the placed feature file, correct?

hasty cove
#

Oh good, okay. Just poor naming got my confused

#

What would the existing geode feature conflict with?

#

And no, that's not in the placed feature file, it's in the vegetation patch configured feature

#

Since that's what places the geode

spiral raven
#

Hm. Well, after trying negative and positive y-values, I'm still not getting this to spawn, somehow.

#

Okaaay... I made a test file to place the geode that doesn't call the vegetation patch, and calls the geode file directly, and that works. It must be something with the vegetation file.

#

Going through and testing manually for the geode file currently.

#

Well, I've at least narrowed it down to the vegetation file. 😅

hasty cove
#

Indeed

spiral raven
#

Yeah, this is a bit strange. thinkthonk

#

My current guess is that it's somewhere here.

#

Would both of these heightmaps be needed...?

#

It has occured to me just now that not once did I reference the marker block except for in the marker block placement... but wait, isn't that what the ground state calls for?

#

From what I can see from testing, the placement feature always fails. Now why would that be? thinkthonk

#

A: inc_exp_lava_geode
Is the custom geode.
B: inc_exp_lava_geode_veg
Is the vegetation patch.
C: place_inc_exp_lava_geode
Places the vegetation patch.

A exists; B Calls A; C calls B.

#

I'm at a loss to why the vegetation patch itself is failing.

hasty cove
#

Honestly I'm incredibly lost by your implementation

#

It's impossible for me to tell what you're even doing enough to identify what individually specifically is wrong

spiral raven
#

Would renaming the files help? 😅

hasty cove
#

It's certainly a sticking point

#

But I think what's making things difficult is you're just not understanding the fundamental relationship between the features, and I don't know how to explain it any more plainly

spiral raven
#

I am definitely dense. That's one reason I ask so many questions. I often forget what features do so I am constantly looking things up. I've also been using Misode's generator frequently, but one thing I wish it had was better explanations for what things actually do.

hasty cove
#

Well that's what the wiki is for

#

It's okay to look things up

#

And even to ask questions

spiral raven
#

Yeah. One thing I wish json had is the ability to use comments, too.

hasty cove
#

Yeah they did remove that recently

spiral raven
#

That's a shame. It would have been a lifesaver for referencing 😓

spiral raven
#

I have an update. It was related to block tags, so I did manage to get it spawning after all.

#

Well, let me ask this - I changed the "replaceables" block tag. Will this have any effect on other dimensions?

#

Turns out, it wasn't just air that was my problem.

spiral raven
#

The second vegetation feature is its own file, correct?

spiral raven
#

Oh my god I managed to do it. 😄

#

Using lapis here as a test.

#

Now I just need to figure out how to get rid of the leaves. I know it's vegetation, I'm just not sure what kind of config to call for it. What would it be?
Side question: How many errors is too many when doing this?

Either way, I'll resume on this tomorrow...

hasty cove
spiral raven
# hasty cove Once again, you just make the ground state air instead of leaves

Apologies, I worded that poorly. I moreso meant what vegetation feature would I call for this? The other two eventually made sense to me, as I did realize those were what was being spawned in the first place. The first was a geode type, then the second was a block column type. The third however is confusing me.

Would this be the marker block that gets referenced, or a completely new feature entirely?

hasty cove
#

None, you can just have the vegetation patch itself do it

#

Just make the vegetation patch that places the block column (what sounds like the last feature in the feature stack) have a ground state that is air

spiral raven
#

Like this, correct?

#

Second image is in the vegetation file, first is what is called for replaceable.

#

Or, did you mean the vegetation feature below this?
If it is like in the image, I'll have to find what I did that is making the leaf blocks persistent.

hasty cove
#

I mean the vegetation patch feature, as I have always referred to it

#

Why is it not able to replace leaves?

spiral raven
#

I'll have to look into it when I get back tonight. I'm getting features placed from the leaves, but the leaves themselves aren't getting replaced there. I definitely overlooked something.

hasty cove
#

Yeah if you're doing marker block feature stacking, each vegetation patch feature should be placing where the marker block is, replacing the leaf block, with the ground state set as the same leaf block, except for the final vegetation patch that will have the air ground state

#

If your vegetation patch that places the block column is just getting placed where the geode is directly, then you don't need the marker block at all

spiral raven
spiral raven
hasty cove
#

No you'd still use a vegetation patch, just have it generate in every chunk, project to a heightmap and be floor, and only able to replace the blocks in the geode

#

Which is what I did for the Dry Midlands in my Dwarfhollow video. It's an example of the "level 1 feature stacking" I talked about in the patches video

spiral raven
# spiral raven Oh. So literally the "replacable" would just be a cherry leaf block in my case, ...

Ok, clearly and unfortunately, I am way over my head with feature stacking at the moment, so I'll have to come back to it at some point once I am more experienced with datapack stuff. I attempted to have "replaceable" just be cherry leaves and... well the whole thing broke and will not spawn the feature for the step it's used in, so I'll be looking tomorrow, again, at why this breaks - and in my defense attempting this at 2am doesn't help. 😅

In the meantime, is there a way to have leaves just outright be replaced with air via blobs or something once it is done generating?

hasty cove
#

Technically, but doing so effectively is still gonna mean doing the same thing as getting your vegetation patch to do it, placement-wise

spiral raven
#

I ultimately did manage to solve it!

The issue was twofold: One, the marker block had a heightmap in its placement features. Secondly, my other issue was in the first vegetation patch. For whatever reason, it had been set to cherry leaves in the ground state. Just setting it to air fixed it!