Jump to content

Recommended Posts

Posted

Cheers.  Just finished porting to forge (a minimap) and updating to 1.14 and discovered this (that you can't).  Well, code at least runs (sans updates) and will be ready to go if that ever becomes possible.  In a non-forge environment I can get this info by mixing in to WorldRenderer.func_215319_a() and be made aware of any chunk that is scheduled to be processed so I can at my leisure read terrain data from that chunk. 

 

Alternatively one could just periodically read terrain data for every chunk in range.  This'd cause a lot more overhead, and would miss changes that happened before a sweep.

 

Anyway, it would be nice to have a way of knowing which chunks have changed.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.