ldtteam / ldtteam/Structurize

Console error regarding missing level 0 blueprint

Open
#841 3 comments 1 reaction 0 assignees View on GitHub

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 beta/release 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?
  • I checked the MineColonies/Structurize Wiki or I asked on discord.
Minecraft Version

1.20

Structurize Version

1.20.1-1.0.816

Related Mods and their Versions

Forge 47.4.0
Minecolonies 1.20.1-1.1.1240

Problem description

I am showing a few errors in my server console for child huts, saying that the level 0 blueprint is not available. But we're specifically told not to include the level 0 huts in the schematic pack. Is this a change, or has something been overlooked, and these errors should not happen?

Image
Anything else?

latest (15).log

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the console errors with Minecraft 1.20.1, Structurize 1.20.1-1.0.816, Forge 47.4.0, and MineColonies 1.20.1-1.1.1240, then inspect latest.15.log for the missing level 0 blueprint message. Trace where child hut blueprints are requested and determine whether the console error is expected; done means the behavior is corrected or the expected handling is covered by a test.

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
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.