You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, my issue is sort of similar to [1.16.5] Can't disable charred tree. #310
The reason I would want to keep the trees from spawning is that the charred trees have purple/black boxes as a texture.
I already contacted the guys from dynamic trees on the discord and they are looking into being able to keep trees from spawning individually.
However they said it would be better to fix the underlying issue of the missing texture.
I am using a big modpack including dynamic trees so i am not sure if anything else could cause this issue.
The text was updated successfully, but these errors were encountered:
@noobanidus
The block state and model files here aren't being read because the blocks are now using the dynamictrees namespace rather than mysticalworld because of the omission of this line after porting to 1.18. I'm guessing that's because you ported before we did.
@noobanidus The block state and model files here aren't being read because the blocks are now using the dynamictrees namespace rather than mysticalworld because of the omission of this line after porting to 1.18. I'm guessing that's because you ported before we did.
Adding back this line should fix this issue.
Yeah, I completed the port several months ago, I just only released it recently.
Hello, my issue is sort of similar to [1.16.5] Can't disable charred tree. #310
The reason I would want to keep the trees from spawning is that the charred trees have purple/black boxes as a texture.
I already contacted the guys from dynamic trees on the discord and they are looking into being able to keep trees from spawning individually.
However they said it would be better to fix the underlying issue of the missing texture.
I am using a big modpack including dynamic trees so i am not sure if anything else could cause this issue.
The text was updated successfully, but these errors were encountered: