Hello. I Decided that I needed a Lua help topic too. Plus, Kerm suggested it.

This is my port of Bloxorz. I used lines instead of filled polygons because you haven't implemented that yet. You can move the block around and stuff, but if you fall off, it has a never ending loop of red flashes(here is what it is supposed to do:http://www.ticalc.org/archives/files/ss/827/82718.gif) Also, if you're playing and you hit enter it, goes back to the prompt with an error. Plus, at the level selector screen, the block and "Moves:" flickers, and when you are playing they flicker also. If you can help with any of these, it would be greatly appreciated.

http://www.mediafire.com/download.php?nwx5dt33jq13ly2

:: For the flickering, you fastcopy halfway through drawgame(), then at the end of drawgame(), so it's going to flash the partially-drawn version before the completed version that includes the "Moves:" text. You should probably remove the first fastcopy.

:: For the infinite red on death, here's the code that is supposed to handle things:
Code:
The alpha variable is used as a sort of counter until the red fade is finished. It should go from 255 down to 0, then you either win or lose. Without inspecting your code closer, I can't tell you why alpha doesn't get decremented. Make sure it gets decremented once per drawgame() if done == true and alpha > 0.

:: [Enter] goes back to a prompt with an error: What error?

Error is:


Code:

*Bump*

New code:
http://pastebin.com/nS7qNdFU

Now the "Level:" and the map are flickering. I'm still trying to figure out the death redscreen.

Edit: I still can't find what's wrong with pressing EXE while playing.

Error:

Code:

Take a look at line 414 in the code: var.store and all that fun stuff. No such thing in LuaZM, remember?

I already commented that out. Now it goes to the next level when you press exe. Every time you press exe. It won't put the block at the starting point of the next level.

Edit: Some things are still flickering, and when you keep pressing exe to go to the next level, when you get to 16, it freezes, and I have to reset my calc. I don't know what to fix, but here is my code:


Code:

Just so you know, [ON] and [MENU] are two possible options when LuaZM programs are frozen. I'd try [ON] first, as it works when the program is stuck in an infinite loop (or should; that's the way I coded LuaZM). Does the [ENTER] behavior you're describing only happen after you've defeated at least one level?

I've tried both of those buttons Kerm. It's frozen. After you finish the first level and press enter, you can freely press EXE to skip levels until you get to level 16. The block position doesn't change when you press enter. It just stays in the same spot and you can't move it.

When you advance levels, you need to reset done, win, and alpha. I presume that that's not happening.

Newest code:
http://pastebin.com/R5xDHqtm

Kerm, it worked, but the block isn't going to its new starting position. Any ideas?

You'll need to reset blockpos at the start of each level, whether it's a new level or a reset level. This line looks like it:

Code:

New code:
http://pastebin.com/YjvMashi
Now that that is fixed, all I really need to do is the Red deathscreen(or I can take it out), and fix the blinking of the "Level:" and the map. Also, it doesn't seem like the Level Selector screen is displaying right. Do you see anything wrong with that?

Edit: Kerm, I can't seem to get it to restart the level after it falls off. Any suggestions?

Does it detect that it has fallen off, ie, start triggering whatever you have in place of the red deathscreen? Is the issue that the red deathscreen never starts, or never finishes and restarts the level?

Most recent code:
http://pastebin.com/UXBxghDe

I know that it doesn't reset the variables, but when I actually tried, it didn't reset the block position at all.

Just a quick question: when I run this, it seems like it does not recognize keypresses very fast. Maybe using zmg.keyDirectPoll and zmg.keyDirect would fix this?

Part of the problem is the repeated user of zmg.keyMenuFast(). A better solution would be local key = zmg.keyMenuFast(), then use the value key. That's the more correct solution anyway.

Spence: Then perhaps there's a more fundamental problem of it not going to the code that resets win, done, and the block position, since you said all three of those aren't resetting?

I will do that Kerm.


I really don't know. I put them before the "drawselector()" and it didn't change anything.

That code only runs "if !game", or if a game hasn't started yet. Game doesn't get unset if the user dies; instead, done gets set and win gets unset. Before line 578, try inserting:

Code:

Error:

Code:


New code: http://pastebin.com/2YK6sTfU

No no, // is a comment in C. That was a comment to you; it wasn't supposed to be part of the code.