Some semi-random thoughts on terrain generation

[NiLSPACE]

Anyone who likes my big oak tree?

[tonibm19]

Its right, but a little "blocky" (yes, in Minecraft) and its shape seems square.

[NiLSPACE]

It's not that bad:
[spoiler]





[/spoiler]

[xoft]

I think it's weird. The central trunk should be higher, after all it's the dominant apex.

[NiLSPACE]

Then how about this:

[NiLSPACE]

The branches seem a little too long. I'll adjust it.

[NiLSPACE]

I uploaded my first implementation to github.

[xoft]

Interesting. Why the floating-point directions, can't you work with regular ints?

[NiLSPACE]

Because if I use ints I can't place a block on the same height:

Code:

---XX
XX---

instead of

Code:

----X
--X--
X----

(If that makes sense)

EDIT:
Now compare my code to the vanilla tree: https://gist.github.com/grum/62cfdec0537...-java-L145

[xoft]

Make the code lerp between startpoint and endpoint, then, you can have branches at any angle, and still keep int coords. Look up Bresenham algorithm if you need to.