Lua Programming Help Thread

thats ok i get you perfectly. You can still use it though. You just have to adjust the movementsytem:
instead of "screen:blit((playerX - 1) * 16 - 4, (playerY - 1) * 16 - 4, figure, 1 + 25 * animation, 1, 24, 24)",
just say "screen:blit(playerX, playerY, figure, 1 + 25 * animation, 1, 24, 24)".
Now it makes steps of 1 pixel if you leave the rest of the tut the same.
The collision is harder though. For that i think the best is to have a seperate table which holds the coordinates.

I'm trying to integrate it to simply display the map, without any collision or user interaction. another question: do the letters have to be named a-p

wait don't answer that i understand why. the code reads it as a-whatever is the last tile.

man i think im a hell of a programmer for only being a young teen!


PS: here is the link to Orbs:

Here's orbs

When I first looked at that code i didn't quite understand it, its pretty difficult I think.
You're right it doesn't have to be a-p, but its just a way to identify each tile in the image "tiles". Every letter stands for a different number. YOu can get this number with this command: "string.byte (s [, i])"

Zitat:

---

string.byte (s [, i])
Returns the internal numerical code of the i-th character of s, or nil if the index is out of range. If i is absent, then it is assumed to be 1. i may be negative.
Note that numerical codes are not necessarily portable across platforms.

---

With the numbers you can calculate which part of the image to blit.

OMGH! i did it! i managed to simply draw the screen and it looks like an exact clone of the pc version! http://i5.tinypic.com/20qjqzq.png

omgomgomg im so happy! im going to try to impliment collision detection somehow. Now i want to make it so that when it does:

Code:

---

function drawTile(tile, x, y)
        local tileX = math.mod(tile, 4)
        local tileY = math.floor(tile / 4)
        screen:blit(16 * x, 16 * y, tiles, 17 * tileX + 1, 17 * tileY + 1, 16, 16, false)
end

---

THAT is writes into and updates the X and Y of each, but that'd be hard with the different tiles. okay i want to make (literaly)

Code:

---

function drawTile(tile, x, y)
        local tileX = math.mod(tile, 4)
        local tileY = math.floor(tile / 4)
        screen:blit(16 * x, 16 * y, tiles, 17 * tileX + 1, 17 * tileY + 1, 16, 16, false)

"if tile is 'a', then
AX[current a tile]=the x being written
AY[current a tile]=the Y being written

if tile is 'b', then
BX[current a tile]=the x being written
BY[current a tile]=the Y being written

if tile is 'C', then
CX[current a tile]=the x being written
CY[current a tile]=the Y being written"

end

---

and now all i have to do for the player collision is

Code:

---

function collision(x1, y1, w1, h1, x2, y2, w2, h2)
        if (y2 >= y1 and y1 + h1 >= y2) or (y2 + h2 >= y1 and y1 + h1 >= y2 + h2) or (y1 >= y2 and y2 + h2 >= y1) or (y1 + h1 >= y2 and y2 + h2 >= y1 + h1) then
                if x2 >= x1 and x1 + w1 >= x2 then
                return true
                elseif x2 + w2 >= x1 and x1 + w1 >= x2 + w2 then
                return true
                elseif x1 >= x2 and x2 + w2 >= x1 then
                return true
                elseif x1 + w1 >= x2 and x2 + w2 >= x1 + w1 then
                return true
                end
        end

return false
end


if  collision(playerX, playerY, 32, 32, AX, AY, 16, 16) then--will the AX and AY work for every single a tile?

        "vspeed=0
        hspeed=0
or
playerX=xprevious
playerY=yprevious"

end

---

right?


and since the blue objects are all destroyed when you get a blue key, how can i make the program skip the blue tiles and leave em as blank when gotkey=true ?

Where ever your checking for the blue tiles, hav an if statement saying if blue_key==false then do collision, else dont.

Oh and it sounds like your asking us to make your game a little... Watch it ;)
P.S. Watch what you say around here... Im sure the LUA Help Thread its fine since only young novices actually DO code in LUA, but if you step it up to C and start announcing your age and junk, youll be quickly looked down upon for acting high and mighty. I for one am 14 and know both LUA and C so I get the best of both worlds, and have seen the differences. But none the less, good luck on your Chips Adventure port ;)

i tried it with the engine itself and it's really slow! is there a way to make it faster?

blit as little as possible.

In LUA itll no doubt be slow, for its both interpretting the input to output + tiling over and over again will take for ever, that is why you should arrange it to load all the tiles at once. Make a huge 1000x1000 thing of tiles that fill those spots up at start and then itll just take one masive loading time instead of small individual ones.

very smart idea, maybe i can make it check only the blue tiles every step, and all the absolute tiles at the start.


oh no i tried that it won't work unless i clear the screen 1st and draw again cause it gets all glitchy. i did get all my fps back, though, but...yea. i'll see if i can only clear the moving objects. is that possible?

You should use different layers. Like blit all the moving parts on the screen for example and the absolute stuff on a different image. Then first blit the background and then the moving/changing stuff.