Luis_ST

change the ClipContext.Block, since OUTLINE use the default VoxelShape, if you want to ignore non-solid Blocks you can use COLLIDER it use the collision VoxelShape

first of all please use the code feature to post code show more of your code, are the methods called?

did you looked at the BambooBlock? but basicly you need to check inside Block#tick if the Block can stands on the current positon via Block#canSurvive. if the Block can't stand at the current positon, you need to remove the Block via Level#destroyBlockLevel Note: Block#canSurvive retruns true by default, if you want custom logic you need to overwrite the method

then unfortunately I have no idea, you could check an even larger area

you can set these with ModelBuilder#transforms and then TransformsBuilder#transform with Perspective you want to set, you could use this as and example

do not use the auto completion of your IDE

in how many chunks have you checked the ores generation? Question for me, how did you check the Ore generation?

Post full log

take a look into the Item.Properties class, check if there's a method called fireResistant -> if there is one add the method manually to the Properties -> if not then look for a method called immuneToFire, (or smoething like this)

the error has nothing to do with the tree feature, you have an error in a LootTable Couldn't parse loot table prehistoricnature:blocks/lepidodendron_leaves update your repo, since there is no data folder

in your version it should be fireResistant and not immuneToFire, try with fireResistant

then it's isImmuneToFire, but i don't know why since with this mappings in my project: mappings channel: 'official', version: '1.16.5' public Item.Properties fireResistant() { this.isFireResistant = true; return this; }

then the method is called Item.Properties#fireResistant

post debug log

post the line in your build.gradle file which looks like: mappings channel: '***', version: '***'

first of all codes are not from Forge it's from vanilla (mojang), you could start here: https://forge.gemwire.uk/wiki/Codecs

Error in journeymap, make sure you use the latest version of the Mod, if you already use the latest version, report the bug to the Mod author.

which version and which mappings did you use?

yeah should be

so in summarize you want to extends the vanilla Doors to a height of 3 Blocks? am I right?

unfortunately it doesn't work for me either, the reason for that is that skipRendering is not called but i have no idea why

you find it in .minecraft/logs/debug.log

i'm not sure what you mean they also have to use the vanilla Tag, you just have to make sure that your mod is loaded after all other mods. then loop through the tag values and remove yours and the vanilla doors, then you have the Doors from other mods the class is used in the Data Genaerator (for generationg the models) and inside the DoorBlock these is handelt by DoorBlock#setOpen

why did you not create the Features (ConfiguredFeature and PlacedFeature), in the same way how vanilla does it? you don't need to extends/overwrite something also the classes i told you above has a lot of examples

the Villager interaction on Doors is handelt via the DoorBlock and the WoodenDoors Tag, a custom DoorBlock which does not extends the vanilla DoorBlock would break the Villager interaction you need to overwrite the complete behaviour, create custom Enums for BlockStateProperties, ... replace it with a custom one if you want to do it like that then yes, since you overwrite the block completely it doesn't matter But I would recommend you to use UPPER, MIDDLE, LOWER. it would make the whole thing clearer