Instant turnoff. Why do developers do this to each other?

Not sure what the second link is, but you are indeed right: jMonkey has voxel support. So I might have to look into this... Thanks!

They generally don't. He made the engine for himself using his own personal programming "style", and so didn't consider making the code understandable to anyone but himself. He then decided to share the source code, but it wasn't made with that in mind. He's obviously at least partially self-taught, as I don't think any real developer who's had to work with other people's code for a living, would ever make something that looked like that.

You have chose the worst POSSIBLE approach to learn anything at all. Just trust me on this one, ok? Go ahead and try to understand an engine, but only start learning voxel engines when you comprehend a) complex 2D engine and b) at least a bit complex polygon engine.

Fenix... I've been programming since I was 12 years old. I taught myself. I got my dad's old QBasic textbook, skipped to the end, and started trying to figure out how all the examples worked. In fact, almost everything I know about coding I learned by diving right in head first. That's just how I work. The few times I tried to learn things the "correct" way, I ended up getting bored and moving on to something else. EVERY TIME. It simply doesn't work for me to do things methodically. So in this case, I either do it the supposedly "worst possible way," or I don't do it at all.

Oh go ahead, do dive in, but dive into something that's comprehensible - you know, at the very least 3D polygon egine. Voxels are just as hard to understand as you can get. When you red the examples in the book (and I understand, that's usually how I teach myself - I can't for the life of me understand most tutorials,) it has been written for you to understand. Voxel engines are most probably as far as you can get from that, they're not even supported by most libraries so they tend do be coded from the scratch. You have two things to understand properly: 3D engine and voxel engine - and you'd have to do that ANYWAY, it'd just be combined. Mixing that and trying to learn it with no previous understanding of the language is like pounding your head against a wall. If you actually do manage to learn coding from a voxel engine, I'm going to ... Well I won't be that impressed since I'm a stoic, but I will slightly bow my head in your general direction.

It's very possible that I might roll back to simply making use of polygons, depending on whether or not I feel that I can get what I want out of them. Perhaps a combination of the two. Voxel-like construction for environments to allow destruction, and traditional polygons for everything else.

Oh, apparently I can't even run the engine. My graphics card doesn't support OpenGL2.

I am SO SICK of not having the money for decent hardware. Lately it's thwarting me at every turn, like a trusty silent movie villain. Want to play any games newer than 2003? Well too bad, because none of them will run. Want to play games OLDER than 2003? Half of them either bluescreen, crash, or inexplicably lag. Want to play an old favorite through DosBox? 'fraid you'll need a better CPU for that, buddy. Want to download the Blood Launcher? Not with your connection, you won't! Want more than 70 GB worth of games installed? Well, I suppose you'll need a better harddrive, won't you? Need to have videos of your games to be able to host them on Desura or submit them to the Humble Bundle or be taken seriously period? No, that would require a videocard that wasn't build during the industrial revolution, you fool!

GAAHH

/firstworldproblems

Don't you have some friends or family members with better equipment? For the video part of your problem.

Believe it or not, no.

What if I record my playthrough? Would your pc be capable of editing the video?