Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Builder Immediatly stops running #130

Open
Helcostr opened this issue Mar 26, 2024 · 3 comments
Open

Builder Immediatly stops running #130

Helcostr opened this issue Mar 26, 2024 · 3 comments

Comments

@Helcostr
Copy link

I am on day 402, and this is my 3rd or 4th time using the Builder to quarry. However, I have discovered that It stops immediatly after running it. No error messages pop up, and nothing shows up in the Minecraft logs. It manages to get some random progression into it's quarrying before stopping.

This is my current configuration:

  • Builder+Tesseract (Tesseract mod) combo with storage (AE2's interface) on the other side of the Tesseract (and Forge Energy being piped in)
  • Clearing Silk Quarry card:
    • Shape: Box (Solid)
    • Dim: 203,121,180
    • Offset: -102,58,91
  • Filter: 45 items set in whitelist mode

Version Stuff:

  • Minecraft: 1.20.1
  • Forge: 47.1.3
  • RFToolsBuilder: 6.0.4
  • Modpack: FTB Unstable 1.20 Forge

Any thoughts on what can be causing it? Without an error log, it's hard to tell.

@McJty
Copy link
Collaborator

McJty commented Mar 26, 2024

Chunks are not claimed? Builder is a player too. A fake player. It needs permission in claimed chunks

@Helcostr
Copy link
Author

Helcostr commented Mar 26, 2024

I had the builder in a claimed chunk, and thought that claim protection was an issue. Removing it had no effect. (I am also the only player on this single player world)

Moving the builder to a different location and setting my intended dimensions didnt solve anything.

@Helcostr
Copy link
Author

It seems like having Tesseract's Tesseract next to RFToolsBuilder's Builder is causing it do something funky. Originally, I thought it was AE2's ME Controller was causing some kind of "forcing the block to reload" issue, (I had a builder placed within a 4x4x4 wireframe of AE2's ME Controller blocks earlier, and thought it was AE2 that was causing the builder to reload in some shape or form).

I have no idea how this issue/relationship work, or who's end needs to be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants