What I mean is that it's not code that you're linking with, sorry if the wording was bad.

Yup, download the ConvertImg tool I posted here earlier, compile it using the Qt SDK, run it, replace the terrain.h file in the crafti directory and rebuild it.
Alternatively you can also send it to me. A texture loader is on my TODO list.

Quote from: Vogtinator on April 17, 2014, 06:15:25 pm

Quote

Also do you think, grass, water and lava (including their flow/physics) would be hard to implement?

Grass flow? Do you mean grass spreading onto nearby dirt blocks?

THat would be nice, although just at least having grass at all would already be cool as well (since now it's pretty much desertic lol)

? I added grass blocks in 0.7 IIRC.

When i try to compile using the source from Git, it says that nucleus.h is not found.

New feature release: v0.8!
New features:
- Crafti now uses block data (8 bits per block), which means your save files won't be compatible
- Torches in all directions (even upside-down)!
- Flowers!
- Mushrooms!
- Spider webs!
- Cake!
- Faster chunk culling!
- Ability to load external textures ("/documents/ndless/crafti.ppm.tns") in PPM format (24bit binary)
- A splash screen (From the internet, I only added the text "crafti")!
- Message "Loading" now shown when crafti is doing some heavy processing
- Disabled the mode with textures disabled, it was too ugly and slowed down the startup somewhat

Bugs fixed:
- Clock on screen

Known issues:
- With HD textures the block selection menu becomes unusable (but 1 and 3 still work)
- Front side of blocks is fixed (all furnaces face the XY-Plane)
- CLIP_PLANE too close
- Can rotate more than 90° horizontally, which turns the screen upside-down
(I'll probably fix all of them in v0.8.1, but that'll likely take a while)

Screenshots (BTW, hd textures don't make the game slower  ):
     
     

What should I implement next?

And BTW, I'd be very glad if anyone could design a better menu or "Loading" message for me, I suck at art 

Oops, I just found a typo in the ppm loader: "0x11111" instead of "0b11111". The result is green all above the texture atlas...
I fixed it in the attachment above, that fix doesn't deserve a version number

That looks really awesome! This is the first time I tried it on a real calc, and the speed is really decent.
I think it's a little weird that it says "loading" when exiting, though.