Ok thanks
I'll *try* to learn from it/understand it.
Wow, normal speed...

@scout
It's possible that I could make it an option to change whether the bottom is floor or instant death, tho it would necessitate a format change b/c the bottom row isn't poart of the level data.
Another thing.   These friends of yours (that decided upon things in the editor), see if they could like to contribute.  So far, i have one non-developer-made level (ashbad's) but a level pack of just one level isn't a lot...an editor's built in, they might want to make some of their own.


EDIT: ERR:PARENTHESIS when I try to compile...methinks it's stuck at the realloc thing
EDIT2: changed #Realloc(12,to#Realloc(12) and it worked fine, except for the menu

Yeah, about that.  It doesn't seem to detect the bottom row, the character just falls through it nvm had to delete the old appvar, size is different now
Also, how significant is the #Realloc(12) ?  It seemed to break the main menu (I made them comments, disabling them, and it worked fine)
btw check edit2 above

Just noticed, the loops go to 360, which is 24*15.  I'll try changing that to 384, 24*16 and I'll see if it detects the bottom row then. see above

So I guess there's >52 bytes free after byte 12...at least hopefully

IDK, you'd have to ask squidgetx
I took it out and it works fine...
This is the way he put it in, IDK if a comma works different .

I'm not sure, I don't want to take any risks on hardware right now (not with Tio coming this far and fast), and I don't have my flash drive with wabbitemu on...

Well, I have msd8x but still
Anyway, it seems to work fine w/o it.

I guess so, but the way I wrote it any variable pretty much to E or something gets recycled continuously
You could call Tio environmentally friendly I guess

I don't know, there were two of them, both saying #Realloc(12, ...
I guess that settles it
Do you know what was supposed to be in it's place?  There was one on like the second line and one just before the menu, each one the same.

A question about the tile detection.  Before, all the player had to do was touch a bouncy block with even a pixel and the character would jump.  Is there an optimized way to do that?  The same was for the finish and enemy blocks.

Quote from: Darl181 on February 11, 2011, 10:57:42 am

Quote

so that if I try to draw a certain type of block over the same type of block, the one below won't be deleted?

So, you mean nothing would happen, it would just skip over it?

And take out the wraparound, I can do that.  Maybe when I split the game and level editor apart, I can make an options menu for each or something.

Actually, come to think of it, in the next release i can put comments in the source telling what part does what, say instead of If X>>24:0→X:End it would be If X>>24:24→X:End

Yeah, skip it would be perfect!

I also think that we could be able to make maps without the black blocks below. Not sure if others agree, though. What I think is, if you fall, you die.

Also, the wrapping around would be perfect too.

If I take out the bottom row, is there a way for it to detect if it's on the ground, Y=60?  Before, the bottom row was needed for pixel testing, but now...
Actually, The level stores in L1 right? If it does that, i can just add ones (floor blocks) or sixes (enemy blocks) to the end of it...nvm