Closed KioProject123 closed 2 years ago
Already generated blocks won't revert back to their vanilla blockstate attributes. You have to regenerate the end world.
Anyway (personal opinion) I think no one would really care about a seeing few chorus blocks with this blockstate, I don't think it would affect your users experience that much.
Note: this is the only way to create transparency supporting custom blocks with hitbox, there is no other way to do that, it's a limitation of the game.
Already generated blocks won't revert back to their vanilla blockstate attributes. You have to regenerate the end world.
Anyway (personal opinion) I think no one would really care about a seeing few chorus blocks with this blockstate, I don't think it would affect your users experience that much.
Note: this is the only way to create transparency supporting custom blocks with hitbox, there is no other way to do that, it's a limitation of the game.
Thank you for your reply.
I have a pre-generated TheEnd world before installing the plugin,all chorus plant blocks are normal. After I installed the plugin, chorus plant blocks was changed to an abnormal state. When I disable fix-glitched-blocks, I find that chorus plant blocks will not be changed. (it also affects the mushroom blocks)
Is there a way to keep chorus plant blocks unchanged alone? (I can understand what you said, but I don't need any transparency blocks, so I want to minimize unnecessary changes)
My statement may not be accurate. In general, how to prevent changing existing chorus plant blocks, but keep fix mushroom blocks and note block blocks. All worlds are pre-generated before installing the plugin.
You must disable disable-REAL_TRANSPARENT
blocks in config.yml and regenerate the end world.
It's the only way to revert this behaviour.
Wait...
Are you saying that fix-glitched-blocks
option will always change chorus blocks even if disable-REAL_TRANSPARENT
block is set to true
?
This is not intended if the answer is yes, let me know
You must disable
disable-REAL_TRANSPARENT
blocks in config.yml and regenerate the end world. It's the only way to revert this behaviour.Wait... Are you saying that
fix-glitched-blocks
option will always change chorus blocks even ifdisable-REAL_TRANSPARENT
block is set totrue
? This is not intended if the answer is yes, let me know
Yes. disable-REAL_TRANSPARENT
is set to true and fix-glitched-blocks
also set to true.
Normal chorus blocks will be changed into abnormal ones.
Thanks, I'll try to find a solution for the next update
Discord tag (optional)
针织薄外套#0277
What happened?
I have disabled REAL_TRANSPARENT, but when fix-glitched-blocks is enabled, model will still be broken. Is there any way to keep the chorus_plant model intact when fix-glitched-blocks is enabled?
Steps to reproduce the issue
Go to The End to view
Server version
I can't connect well to foreign networks
Current: git-Purpur-1814 (MC: 1.19.2)* Previous: git-Purpur-1809 (MC: 1.19.2)
ItemsAdder Version
ItemsAdder version 3.2.3-r9
ProtocolLib Version
ProtocolLib version 5.0.0-SNAPSHOT-b600
LoneLibs Version
LoneLibs version 1.0.21
ItemsAdder config.yml