Considering that vanilla methods of chunkloading since 1.13 got between impossible and very cumbersome, I'd like a more 'poor man's' method to transfer a signal:

I want redstone signal to reach the distant destination before the player does. E.g. I flick a lever at a 'control center', then fly on Elytra along the wire to a distant farm (say, 100 chunks away) that is started by that lever; and I want it to start as soon as possible after its chunks load.

Normally, the redstone signal stops at the border between loaded and unloaded chunks and freezes there - after loading subsequent chunks it won't resume, redstone on one side lit, on the other unlit, until the blocks at the old border receive an update. I wonder what sort of contraptions along the line would make it resume automatically - e.g. some sort of clocks that would automatically update the connections on chunk borders, or 'resend if not acknowledged' repeater devices so that as soon as farther segments of the line load, the signal could resume.

Was anything like that invented?

  • I take it to mean you want to do this without commands, which IIRC can force chunks to be loaded? – MBraedley May 17 '19 at 16:31
  • @MBraedley: Yes. Moreover I don't want to influence the chunk loading process by any means other than vicinity of a player. I want the signal to resume travel as more chunks load, not to cause more chunks to load by other means than just player flying there. – SF. May 17 '19 at 22:14

You can't.

Remote chunk loading is entirely broken in 1.13+, it's one of the main reasons why I don't recommend updating beyond 1.12.2. My bug report about it is here, sadly it gets mostly ignored by Mojang. You can try voting for it, but I don't have much hope that it will be fixed soon.

  • 1
    What do you mean? Upon arrival of a player chunks in 1.13 load just fine and most contraptions fully contained within a chunk resume from when they stopped when unloaded just fine. I'm not asking about remote chunkloaders, I'm asking about updating the redstone line as its loaded by presence of a player. – SF. May 17 '19 at 22:11
  • That's exactly the point: if it's contained within a chunk, it sort of works, but only if a player is nearby. As soon as something crosses a chunk border, it can and likely will break when the player leaves or comes back. – Fabian Röling May 18 '19 at 9:10
  • ...and I think a contraption that at its core is contained within a chunk, but can influence the chunk border to repair/restore the connection should be possible. I can think of a fairly complex version: a device that takes slow clock input = 0, fast clock input = 1, constant 0 input and constant 1 input = hold previous state; stores the state in memory and outputs slow/fast clock output depending on memorized state. Using these as repeaters less than chunkloading distance apart should work. – SF. May 19 '19 at 3:30
  • ...but I hope there may be an easier way, e.g. triggering block updates on chunk borders. – SF. May 19 '19 at 3:35
  • Apparently I never responded to your last comments here: No, remote chunk loading is absolutely impossible in 1.14+, except by continuously dropping items back and forth between portals. And I'm pretty sure even that breaks when reopening a Survival world or restarting a server. – Fabian Röling Feb 28 '20 at 3:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.