great looking game
though i wish can slowly progress for infinite worlds
oh i started minecraft just to help u in your programming

@jh0421: Thanks for this information, I changed some parts of the menu activation/deactivation and I am confident that I have finally fixed that bug

@AnToX98: I've seen it but unfortunately I don't understand much french. However, it seems like you are doing a good job there at TI-Planet

@hking1: Most parts of the game would be able to handle infinite worlds, but the world generator isn't at all: Surface, caves, ores, plants and, for the next update, dungeons are generated from left to right once when starting a new game. That technique could be used for infinite worlds, but there would be much difficulties like later generated caves, which could make a turn and spread into already generated parts of the map and destroy everything. And as long it's just a non commercial game for a calculator, I think a 400*100 block world is enough to overcome a boring history lesson
The item dragging does already work with furnaces. An advanced crafting system would be very complicated to make and very laborious to use, especially for clickpad users.

PS: I'm making great progress with update 0.11! Planned features are marked on first post. \/ Screenshot \/

Well, that's freaking nice

Oh yeah and I forgot to say, but there are quite a lot of optimization that you can make to the code.
It's quite huge already, so, it's going to be hard, but I believe everything would have been simpler with a [better?] screen +/ layer manager.

When/If I have some time, I'll try to take a look at the whole code in general and propose some optimization ideas


For now, I have seen things like :

objFallingBlock=class()
function objFallingBlock:create(x,y,i,ID)
    ...
end

objList[index]=objFallingBlock()
objList[index]:create(bx,by,index,updateBlockID)

Why not simply use a syntax like :

objFallingBlock=class()
function objFallingBlock:init(bx, by, index, ub_ID)
...
end

objList[index] = objFallingBlock(bx, by, index, updateBlockID)since :init(...) is the constructor, made for that

oh, don't get me wrong, it's really a wonderful project you've done so far Not a lot of people could have done that

General and specific advices /tricks for optimizing [Nspire] Lua scripts are available here : http://adriweb.free.fr/t3/ (either the powerpoint or the PDF - both are in English)
(Edit : well, this is also a reference ^^ : http://www.lua.org/gems/sample.pdf)

About the lava, oops, I forgot about the fact that it was an image....
I guess it'll have to stay like that if no more images are created (not sure if it is a good idea, just to get inclinations....), but in 3.6, there may be advanced images APIs, so maybe there will be something useful about that...

@adriweb: Thank you very much for that link!! That's exactly what I needed! I'll read it carefully and then try to do some optimizations myself (so better wait to look through the code until the next update!)

No problem Feel free to ask any questions

And about 3.6: I've already read that it will include new API features, is there already some information about the lua part somewhere?

Well, there is going to be a 3.6 Lua changelog... so, when the actual public 3.6 OS comes out, we shall see in detail

@Lionel Debroux: Yes, of cause! I've noticed that commotion about 3.6 and that it blocks ndless; therefore many peoply obviously won't install it. If 3.6 brings some useful features, I will only use them for cosmetic purposes, such as inclination for lava

i think you should check this out:
http://ourl.ca/17003

 this shows many possible items for minecraft
   it can also show basic outline for what items should out together in a version of your game
its in basic though


-------
ps

keep that good work up