-
Notifications
You must be signed in to change notification settings - Fork 3
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
[Forge][1.18.2][0.2.9] How do I pick up a circuit? #14
Comments
Hey there! Sadly this is not a feature just yet. v0.3 will be adding blueprints, which will allow you to copy an entire circuit design and place down any number of copies of it (and later on, share that design with others). At that point, you can just get a blueprint of your circuit, break the old one, and use the blueprint to place it down again at its new location, which will also allow you to rotate it (which is not currently possible either). I'll leave the issue open until v0.3 comes out. |
Hi there, |
when is v3 coming out? and will it be available for 1.18 |
I second this. |
If you have considered using an external mod to allow for picking up and moving the circuits around, don't. Server I'm on had the Carry On mod (lets you pick up and move single block tile entities like chests) and we had to blacklist SuperCircuitMaker in Carry On because I accidentally picked up a circuit board one time too many, ruining my work (it does NOT transfer the contents of the circuit when you move it). |
Also does not work with the mekanism carboard boxes, a blank circuit is placed :( though when you break the block under it, part of the circuit is put back(??) im not so sure its a good idea however. Make sure you back up your saves before trying to mess with inter-mod solutions though. |
Hi there,
I can break a circuit by crouching and mining (with a pickaxe), but it is broken into its constituent parts, rather than yielding the circuit in its entirety. Is there a way to keep the circuit intact so that I do not have to rebuild it each time?
Thanks.
The text was updated successfully, but these errors were encountered: