0.5.1e - Deployers placing blocks in incorrect blockspaces
AquatikJustice opened this issue · 24 comments
Describe the Bug
I'm playing on a server that just updated to 1.19.2-0.5.1e. I have run into a bug that I have tested in a clean install w/ only Create 0.5.1e, so this isn't caused by an interaction w/ another mod.
Reproduction Steps
Deployers on a contraption (in this case a mining machine) will place blocks in the blockspace where the hand/arm are if they are unable to place a block in the correct blockspace (the blockspace in front of the hand). This does NOT happen when it tries to do so either facing up or down. It does happen in all other directions (N, S, E, W).
Expected Result
The deployer should only place blocks in the intended blockspace. If that space is filled, it shouldn't place a block anywhere else.
Screenshots and Videos
No response
Crash Report or Log
No response
Operating System
Windows 10
Mod Version
0.5.1e
Minecraft Version
1.19.2
Forge Version
43.2.23
Other Mods
No response
Additional Context
No response
Can also confirm this issue on 0.5.1f, Minecraft 1.19.2; using stationary, horizontal deployers to place copper blocks.
Interestingly, while I was testing stuff in a creative world, I discovered that it seems to happen faster and more frequently at higher tick speeds; at 3 ticks, it tends to take several minutes, but at 300+, it happened within a few seconds.
Edit: After some testing, it seems to happen when the block in the spot the deployer is trying to place in changes into a different block (ex. copper oxidizing, logs being stripped, mud drying). My guess is that the deployer incorrectly assumes that since the block in that spot isn't the same as the original block, that the block has been removed completely.
I've also just experienced this issue.
MC 1.20.1
Create 1.5.1f
When a Deployer on a Minecart Contraption is pointed in a cardinal direction (not Up or Down), and the space it would normally place a block into (2 spaces in front) is already occupied, AND if the existing block does not match the block that it is attempting to place, it will instead place the new block 1 space in front of the deployer. If the existing block is the same as the block it's attempting to place, then it behaves as expected (does not place the new block).
I also experienced this issue. It is not limited to minecart contraptions. Here is a short video showing a minimal reproduction with a mechanical piston on MC 1.20.1 and Create 0.5.1-f
Anyone able to sort this issue. Having the same issues in 1.20.1 create 0.5.1.f
it seems to work fine when there is no blocks. But when I sent my contraption down my tunnel underground to fill in holes it placed incorrectly as mentioned above.
deployer is set to place in one block (torch level) but places out of no hole to fill
I am also having this same issue, MC 1.20.1, Create 0.5.1f. This bug broke my tunnel bore :(
I am also having this same issue, MC 1.20.1, Create 0.5.1f. This bug broke my tunnel bore :(
I found a temp solution, make your drills one block wider than you need then it will place blocks as intended
Maybe you should build the whole thing? Could that many deployers complicate things, but lower numbers don't?
5x5
Drills in front, Deployers behind them placing cobble IN FRONT of the drills, then 5 deployers facing up and 5 facing down to create roof/floor, then 3 deployers facing to each side (rows: 1, 3, 5), then finally 2 deployers facing each side (rows: 2, 4).
I have no clue why you're not seeing it as there's video proof on the test world that only has Create and Freecam (Freecam added after initial testing to get a better view of what was happening).
i cannot reproduce the problem you describe. can you please crash your game by holding F3+C for 10s then attach the crash report
Attached.
crash-2023-10-25_03.20.51-client.txt
i have the same install (even added freecam like you have) but i cannot reproduce the issue:
- please provide a screenshot of the contraption you used that misbehaves
- what launcher do you use?
Video: https://youtu.be/HhdllfmYUW0
I am using GDLauncher.
As you can see, the deployers start off fine, but as soon as they hit a spot where the wall is already there things start to go south. Eventually, even the deployers facing forward break down and the contraption can no longer continue.
Schematic attached. Retested this version on the survival server where I originally noticed the issue and it's still doing it.
https://drive.google.com/file/d/1yFWeV96oGSI68jEtHgLLltLvz_6jIDQy/view?usp=sharing
i tested in creative and cannot reproduce the issue. at this point, i am wondering if somehow your launcher is causing the issue (that's happened before). I am using prism.
Recreated the modpack in Prism. Logged into the server. Used the machine from the schematic. Same result.
I can confirm this is reproducable as I am having the exact same issue. Building a tunnelbore (contraption) with deployers in front and on the sides will only work occasionally, as they will place a block directly in front of the deployer instead of placing it with a space in front as they are meant to. I'm playing on All The Mods 9. I will attach video files later if I remake the tunnelbore.
I can confirm this is reproducable as I am having the exact same issue. Building a tunnelbore (contraption) with deployers in front and on the sides will only work occasionally, as they will place a block directly in front of the deployer instead of placing it with a space in front as they are meant to. I'm playing on All The Mods 9. I will attach video files later if I remake the tunnelbore.
Issue reproduced. Strangely, it seems this only happens to deployers that are placing blocks in cardinal directions, and does not affect deployers that place blocks up or down. https://www.youtube.com/watch?v=Ef2_2WTEwmA
I've got the same problem and found out that when the block is placed there before and doesn't match the filter on deployer then deployer places incorectly. also its minecraft 1.20.1 and mod version is 0.5.1f. bug exist from version 0.5.1e
The bug also occurs for me in Minecraft version 1.20.1 and mod version 0.5.1f when playing on a server.
Same bug here, with 0.5.1f on an 1.20.1 Forge server and native launcher. We already had the problem with 0.5.1e.
Just bumping this to say that I've encountered this issue on Create 0.5.1f exactly as highlighted by katewyen's video above.
If there is a block in the deployer's "place-space" that do not correspond to the filter it will place a block in an adjacent space instead of not placing anything.
I also did not encountered the bug with the previous version of Create I was using before updating. (Unfortunately I could not find which version as i did not realized the bug was here before using one of my old machine weeks after updating).
In the meantime for those who don't want to be stuck in their progression : When designing contraptions, try to always make sure that the deployer deploy on an empty blocs, by placing an extra drill in front of it for exemple. It's not ideal, but at least it should make your contraption future proof while waiting for a potential fix.
EDIT : After some more testing it appears that if there is no adjacent space available to place the unwanted block the deployer does nothing (which is normal). I was worried it would break the core of drill contraptions where you need to place block in front of the tracks but it don't, so that's somewhat of a relief.