Jump to content

Recommended Posts

Posted

I'm creating a chunk pre-generator and I'm running into trouble with "Already decorating" exception. I figured it was because I was calling the methods to populate and generate chunks too fast. To fix it, I put a delay before each call (about 250ms works for me). However, I don't want players having to decide how fast they would allow for terrain to generate.

 

So my solution to this would be to have somkind of a fast benchmark which would be ran everytime before I try to generate, to see what their computers are capable of, and that use that info to set the appropriate delay. But I have no idea what method I could use or call that wouldn't really affect anything, and would be intensive enough to have a somewhat reliable results.

 

On a related note, whenever I generate a chunk, I immediatley save it, drop it, and unload it (unloadQueuedChunks()) . Could it be im getting the error because I'm (in theory) having no adjacent chunks loaded? I know  Minecraft loads chunks when decorating cross-chunks, but I'm just no that familiar with the mechanic.

 

Help please?

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.