Block Replace not setting leaf blocks as persistent.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 55
- Forks
- 53
- Avg merge
- 20m
- Merged PRs (30d)
- 1
Description
Is there an existing issue for this?
- I have searched the existing issues.
Are you using the latest Structurize Version?
- I am running the latest alpha version of Structurize for my Minecraft version.
I am also running the latest versions of other mods that are part of my problem.
Did you check on the Wiki? or ask on Discord?
Minecraft Version
1.20
Structurize Version
737-beta
MineColonies Version (if related bug)
n/a
Related Mods and their Versions
n/a
Current Behavior
replacing any block with a leaf block is not setting the leaf block as persistent.
Expected Behavior
well..the opposite of what it is doing. replacing a block with a leaf block should set the leaf block as persistent.
Reproduction Steps
go to dark oak treehouse dyer/tavern on schem server. replace leaf blocks with bedrock, replace bedrock with leaf block and see they are still not persistent.
Logs
n/a
Anything else?
n/a
Footer
Viewers
- Add a thumbs-up to the bug report if you are also affected. This helps the bug report become more visible to the team and doesn't clutter the comments.
- Add a comment if you have any insights or background information that isn't already part of the conversation.
n/a
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce this on the 1.20 schem server using the dark oak treehouse dyer or tavern: replace leaf blocks with bedrock, then replace the bedrock with leaf blocks. Trace the block-replacement handling and verify that the resulting leaf blocks are persistent; confirm the behavior after repeating the reproduction steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100