Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue when exploding custom logs/leaves #34

Open
Cryxow opened this issue Sep 1, 2023 · 4 comments
Open

Issue when exploding custom logs/leaves #34

Cryxow opened this issue Sep 1, 2023 · 4 comments

Comments

@Cryxow
Copy link

Cryxow commented Sep 1, 2023

When exploding custom logs, they drop the default log material (OAK_LOG here). Same for custom leaves, they drop the default leaves' saplings (AZALEA here). And the custom logs near the explosion resets their state.

image

In the image above you can see the drops & the noteblocks that was custom logs before the explosion.

@Fisher2911
Copy link
Collaborator

Are you using a custom world type? The more information you give in these bug reports the easier it is for me to fix them

@Cryxow
Copy link
Author

Cryxow commented Sep 1, 2023

Well, there isn't a lot of informations to give. I am using the default world generator, normal type. I am sure you can reproduce this issue yourself. It did this even in a fresh installation with only HMCLeaves & ItemsAdder installed.

@Cryxow
Copy link
Author

Cryxow commented Sep 1, 2023

And for the log state reseting, I think that is only client-sided. When we click on it, the texture reappears.

@Cryxow
Copy link
Author

Cryxow commented Sep 1, 2023

Okay, before explosion, my log state is [instrument: banjo | note: 2], but after the explosion, it is [instrument: bass | note: 2]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants