The physics are kind of basic, and just the y-velocity (7 different y speeds: from -3 to 3). In trying to keep the "arcade" feel, the x coordinate is controlled directly by the keys. What I'd like to do with this is smooth scrolling...but as of yet i've no idea how to do that
later edit: okay, I have a few smoothscrolling tilemappers to attempt to learn from on my msd8x drive, but any others would be appreciated
Tio, the platformer. The controls are simple enough. In the editor, 2nd/alpha toggle frontbuffer/backbuffer. Frontbuffer makes platforms/walls, backbuffer makes 'bouncy' tiles, kind of like the block in mario with the note on it. Del deletes a block, mode allows one to clear all. For now, only one level at a time. Clear goes to main menu. In game: left/right move, 2nd jump, down go down a hole or off an edge (if you're partly above one) clear quit. You try to get to the right side of the screen on the bottom. There are no preset levels, you'll have to make one first.
This took me about a day, but more is probably to be added.
Is it a game where you must turn OFF all blocks successfully?
Yes. Tio stood for turn it off. I actually kind of liked the sound of 'tio' (say it out loud, it just sounds like a good game name) so I changed this one to lightoff. Tio the platformer is somewhat physics-based. So far I have rudimentary gameplay and a level editor. And only about 3.5K
What I did for TWHG is it checks 4 places (the corners of the sprite), and it only reacts for one. It's possible to make it react to one tile over another. Then you deflate the coordinates, taking advantage of how axe always rounds down, to find the pointer the tile is in. ie if the tiles are 8*8 and there's 12 columns you can do (Y/8)*12+(X/8)→[pointer]
Theoretically, C should change. ++ every box every time a box turns black, -- for every box turned white. Thing is, a good part of the time it doesn't. C is the remaining number of black blocks to be turned off. Clearly, it's not accurate. I think there's a problem with it storing in L1. but it's always worked fine before If you hold 2nd, data comes up. C is explained above, and the game ends when getkey(15) or C=0[zero]. D is the pointer's location. The formula is Y*24+X→D. ie if the selector is in the 9th row and the 3rd column, D is 3*24+9=81. The xy coordinates are next. (When drawn to the screen, they're inflated by 4.) "L1+D" should be the status of the block beneath the selected square. 1 is off, 2 is on.
Hopefully somebody notices it here...I'm pretty sure it's an axe bug b/c pretty much the exact same thing worked before (in TWHG). Ever since I've updated to Axe 0.4.8, I've been having one problem after another of this nature, also with some problems with RotC( and RotCC( which didn't work when I tried to use them. So, I was wondering...what changed? Because data storage to lists and external appvars wasn't failing like this before, and now it fails more often than it works.
This is kind of my last-ditch attempt to find out wtf is going wrong, after this I'm downgrading back to 0.4.5. Can't seem to find another solution, unless I find this out.
EDIT: I'll apologize in advance if this sounds sort of rude or whatever, I'm in kind of a tense mood today
"appvWHGLVL1"[00]"prgmWHGLVL1"[00]->Str0X .L is the level, P is whether or not it's a program. We put its pointer in X. L+48->{P*9+Str0X+7} GetCalc(P*9+Str0X)->XThe line "L+48->{P*9+Str0X+7}" stores the correct digit in the right place. So, if L=6 and P=1, then the data at Str0X now looks like this:
"appvWHGLVL1"[00]"prgmWHGLVL6"[00]The 48 is necessary because the character '0' equals 48, '1' equals 49, etc. 7 is the offset to the first '1', and 9 is the difference between the offsets to the first and second '1's.
Its easy Just go to options, and select Application under 'shell'. The only difference between apps and programs is you can't modify any data that you create in your program. ie: you cant do this:
Theoretically, C should change. ++ every box every time a box turns black, -- for every box turned white. Thing is, a good part of the time it doesn't. C is the remaining number of black blocks to be turned off. Clearly, it's not accurate. I think there's a problem with it storing in L1. but it's always worked fine before If you hold 2nd, data comes up. C is explained above, and the game ends when getkey(15) or C=0[zero]. D is the pointer's location. The formula is Y*24+X→D. ie if the selector is in the 9th row and the 3rd column, D is 3*24+9=81. The xy coordinates are next. (When drawn to the screen, they're inflated by 4.) "L1+D" should be the status of the block beneath the selected square. 1 is off, 2 is on.
Can't make screenie now, if someone can make one it would be great.
[note to concerned people: yes, twhg is in the works. it's not going very well, though] [note/edit/whatever2: 8xp removed due to similar names]
also I think this level difficulty needs to be toned down or the level needs to be moved last, because I played at 1% wabbitemu speed and I still couldn't beat it...
I just had a flashback to MFQT, and just like mfqt I can do it fairly easily What I meant by level select is it keeps track of which levels you've beaten. When you press clear and quit, it should a) go to the level you last beat or b) allow you to choose which level to play. Think like thepenguin's game z-rox. (b is preferred. )
I think I found something that's both an incompatibility issue and a feature request. Can the instant goto be made compatible with CalcUtil's "save screen" option? The save screen is when you quit out of the program editor it asks if you want to save changes or not, very useful but it causes crashes with axe
This project kind of died for some time, but I always had the source as Axe backup files and on my msd8x drive... I was just trying to change some of the pixel-detection between the block and static parts (which, ideally, should change when an enemy goes over it) but the code is just too unorganized to add much more without destabilizing the whole thing. Also, i wrote it probably when Axe was like version 0.3.3, so yeah
Quote
Which leaves open how I'm going to write the GUI. Suggestions will be appreciated
Just played the new release, and was wondering: would it be possible to have saving/level select? It's kind of annoying after you take 5 minutes to beat a level you have to do it all over again. Other than that, great job.
Yeah, it's so random and hard to read the source [of TWHG] that I think I'm just going to re-write it. Which leaves open how I'm going to write the level select GUI. Suggestions will be appreciated.
Show Posts
Just go to options, and select Application under 'shell'. The only difference between apps and programs is you can't modify any data that you create in your program. ie: you cant do this:
