I don't know if this is the appropriate topic to post here, but I'm creating something that requires a clock, and I also want people to import this as a schematic. I heard the only way to do this is with a hopper clock, which works perfectly fine until I import it, which it freezes (not the game, but the clock). Can anyone help? Thanks
Minecraft doesn't know how to act to a imported redstone circuit because you can't do that in vanilla Minecraft. Mods that allow copying, pasting etc. only copies the state of each redstone piece, but not the state of the whole circuit. The circuit will remain frozen until something in it updates. Just like how floating sand works when the world is generated; It'll float until something near it updates and causes the sand to update too and fall. Probably easiest way is to use normal Redstone clock and attach start up button in it so people can start it up themselves after importing instead of it already begin on.
I know that.... but I'm using a hopper clock and hoppers are supposed to work when you import it...
I know that.... but I'm using a hopper clock and hoppers are supposed to work when you import it...
Have you checked the available filters for mcedit?; perhaps one exists for this task. I only say this because sethbling made a filter for moving circuits (not for schematics) but the pain with that is that it updates/changes coordinates in blocks after said move, which in some cases (like my own) is a major pain in the butt, why can't it just copy the damn thing and not change it!!?!! grrr!!! ...
I know it's possible to retain text based data in a schematic or even action/animation based data (in the off state) simply because it works with no issues at all for noteblocks and the noteblock studio when moving schematics from it.. though what was said about redstone updates is the truth and even if a schematic were to retain "everything perfectly" all tile entities etc, if it's made when the circuit/device is in use, the moving action of the schematic would be frozen until the user changes/replaces/updates a block or possibly all the blocks within it, in some cases you may end up having to change them all because they wigg out and stay frozen on or off.
Aoccdrnig to a rscheearch at Cmabrigde Uinervtisy, it deosn't mttaer in waht oredr the ltteers in a wrod are, the olny iprmoatnt tihng is taht the frist and lsat ltteer be at the rghit pclae. The rset can be a toatl mses and you can sitll raed it wouthit porbelm. Tihs is bcuseae the huamn mnid deos not raed ervey lteter by istlef, but the wrod as a wlohe.
I found out why it wasn't working... I built the hopper clock wrong! Once I fixed it, it worked perfectly when I imported it! Let me show you what a hopper clock is...
So, this is a hopper clock. It is 2 hoppers conjoined together, making them pass off the same item rapidly. The comparator sees if the transfer was successful, and passes the redstone signal to the repeater, blah blah blah, making a clock. But when you import it as a schematic, the clock freezes up on the "on" state, making the repeaters on the right power the hopper on the right, starting the clock back up. Well anyways, thanks for the answers guys!
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I know that.... but I'm using a hopper clock and hoppers are supposed to work when you import it...
Have you checked the available filters for mcedit?; perhaps one exists for this task. I only say this because sethbling made a filter for moving circuits (not for schematics) but the pain with that is that it updates/changes coordinates in blocks after said move, which in some cases (like my own) is a major pain in the butt, why can't it just copy the damn thing and not change it!!?!! grrr!!! ...
I know it's possible to retain text based data in a schematic or even action/animation based data (in the off state) simply because it works with no issues at all for noteblocks and the noteblock studio when moving schematics from it.. though what was said about redstone updates is the truth and even if a schematic were to retain "everything perfectly" all tile entities etc, if it's made when the circuit/device is in use, the moving action of the schematic would be frozen until the user changes/replaces/updates a block or possibly all the blocks within it, in some cases you may end up having to change them all because they wigg out and stay frozen on or off.
Aoccdrnig to a rscheearch at Cmabrigde Uinervtisy, it deosn't mttaer in waht oredr the ltteers in a wrod are, the olny iprmoatnt tihng is taht the frist and lsat ltteer be at the rghit pclae. The rset can be a toatl mses and you can sitll raed it wouthit porbelm. Tihs is bcuseae the huamn mnid deos not raed ervey lteter by istlef, but the wrod as a wlohe.
So, this is a hopper clock. It is 2 hoppers conjoined together, making them pass off the same item rapidly. The comparator sees if the transfer was successful, and passes the redstone signal to the repeater, blah blah blah, making a clock. But when you import it as a schematic, the clock freezes up on the "on" state, making the repeaters on the right power the hopper on the right, starting the clock back up. Well anyways, thanks for the answers guys!