Custom Schematics on Servers Are Not Being Sent to Clients
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 55
- Forks
- 53
- Avg merge
- 20m
- Merged PRs (30d)
- 1
Description
Prerequisites
- I am running the latest alpha version of MineColonies and Structurize for my Minecraft version.
- I checked the MineColonies/Structurize wiki and made sure my issue is not covered there.
- I made sure that this issue is not a duplicate of any existing issue.
Context
- Minecraft Version: 1.18.1
- MineColonies Version: minecolonies-1.18.1-1.0.328-ALPHA
- Structurize Version: structurize-1.18.1-1.0.319-BETA
- Related Mods and their Versions:
Expected behavior
I would see my custom blueprint as a preview on the client.
Actual behavior
The default schematic is shown as a preview on the client. However, when actually built, it uses the custom schematic.
Steps to reproduce the issue
- Extract a schematic for a building from the jar file.
- Place the schematic in a creative single player world using the "Keeping Placeholder Blocks" option.
- Modify something visible, scan, and save the new custom schematic (using the original name of the building).
- Verify the schematic was changed properly by building it in a new location. The new schematic will be in the "My Schematics" section in the UI.
- Copy the custom schematic from the "new" folder to the server into the correct folder using ftp or similar.
- Connect to the server in-game.
- Use the build tool to preview the building you modified. It should now be in the standard location in the UI.
Optional: Instantly build the building using creative mode to see what version gets built. It will build your custom building correctly. It's just the preview that is wrong.
Logs
N/A
Notes
The client's structurize/ServerUUID/schematics/ folders have no blueprint files in it. So I am guessing that are just not being sent to the clients.
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.
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
Start with the reproduction steps and trace how custom schematics are synchronized from the server to the client for build previews. Compare the schematic data used by the preview with the data used when the building is constructed. Done means a client receives the server's custom schematic and the preview matches the structure that is built.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100