Supply Camp Placement Bug
Moobien opened this issue ยท 1 comments
Is there an existing issue for this?
- I have searched the existing issues.
Are you using the latest MineColonies Version?
- I am running the latest beta/release version of MineColonies 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 Wiki and made sure my issue is not covered there. Or I was sent from discord to open an issue here.
What were you playing at the time? Were you able to reproduce it in both settings?
- Single Player
- Multi Player
Minecraft Version
1.21
MineColonies Version
1.1.819
Structurize Version
1.0.756
Related Mods and their Versions
No response
Current Behavior
I suspect some of these may be more structurize bugs but am not 100% sure.
when attempting to place the steampunk supply camp via the item at the correct height, it refuses to place and demands a block check. The area was correctly prepared and was nice and flat. In order to get it to place, I was forced to lower it 2-3 blocks INTO the ground. Schematic has been checked and GL tag is in correct location and the SC places as expected in 1.20.1
Expected Behavior
the supply camp to place correctly as it always has done.
Reproduction Steps
1: Clear an appropriate area to place the steampunk supply camp
2: position the supply camp so the bottom stair of the staircase is sitting on the ground
3: attempt to place
Logs
https://gist.github.com/Moobien/9a1f34f9a9cd79b8f6eb673e1d1c9727
Anything else?
Logs included: debug, latest and crashlog.
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.
Closing this. seems this might have been a me derp. it had an additional GL tag in it that wasn't on any block inside the schematic and that caused the issue. have fixed and sent to @MotionlessTrain