Jump to content

Recommended Posts

Posted

I've encountered a weird generation issue with my custom gems' ores. When I first added them, I used an array of Block to initialize them and a 'gemNames' string array, with the names of each gem in it (like this). Then I just added the WorldGenerator code, with the same parameters for every gem (with the exception of the Block parameter).

 

This made only the first one generate. I was puzzled, so I removed the ruby generator (commented it out). Then only citrine generated. So I changed the parameters of each generator to be different (here), and then they worked... sorta.

 

The problem is that they generate on the same X and Z coordinate, but different Y. This is strange because my other generators (this) work just fine and don't stack vertically.

 

Anyone have any idea what's going on?

Posted

It's time to set a breakpoint and walk through your generator in the debugger. See what's happening with your randomizer (you may want to articulate your code so you can examine subexpressions). Also find out where the random is coming from.

The debugger is a powerful and necessary tool in any IDE, so learn how to use it. You'll be able to tell us more and get better help here if you investigate your runtime problems in the debugger before posting.

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.