Ok so when score reaches 10000 it increases the second variable? Sounds interesting. I wonder how do you display them? I think I tried such thing before and failed. File size seems pretty nice so far. Keep up the good work and I hope you can solve the issues you are having.
Well thats why it increases the second variable when it hits 10000 instead of 65535 or 60000.
:.blocks :{B-3}->U :For(D,1,C) //for each block :D*3+L2->A //get pointer to block info : If Z+1 //every other frame... : irrelevant code here : End : If the ball hit block D : do stuff with the ball's velocity and the score : 0->F->N->V : C->{L2} :Lbl DX : If {A-2}=0 or ({A-2}=8) or ({A-2}=9) //destruction routines for different blocks : ... : ElseIf {A-2}=10 //start of problem code : C*3+L2->D //I need to keep track of the block's info : Exch(D-2,A-2,3) //so I use Exch : C-1->C //to destroy the block : For(E,1,C) //for each block : E*3+L2->A //get block info : If the blocks are close enough : N+1->N+({L2}*3)+L2->F //pointer to open table space : E->{F} //store a link : End : End //the destruction routines can mess up my links : SortD({L2}*3+L2+1,N) //so I have to go in order. : For(D,1,N) //for each table entry, : If {{L2}*3+D+L2}*3+L2-A //If it doesnt link to the same block as the last one : +A->A //store the link in A : V+1->V //tell the destruction routine we need to return : sub(DX) //I know it all works at least to here : End : End : 0->D //no idea as to which blocks it has & hasn't hittested... : ->N //list is empty : ElseIf {A-2}<=7 : ... : End : If V //If we need to return : V-1->V //then we return : Return : End : End :End
We observe the mentality of pushing you in the right direction and then letting you gain some experience yourself Of course if you are totally lost or if we can give a few more pointers, we'll be happy
well then who wants to optimize some code I don't have any experience in it, and my minor attempts so far have failed dramatically.
I actually have very little data in here. Most of my graphics are Rect(/RectI( commands.
Just a couple tips for anybody who wants to take this on: It's mostly uncommented. All I have are section headers. The Output( statement immediately after the second DispGraphr was for debugging, it's what pushed me over the limit
!If I-1 and it'll save several bytes. (I think there were certain conditions where you couldn't do that, but I don't remember what. They're not important, anyway )
Actually I was thinking about asking if that would be better. Condition where you can't do that: When you're using ElseIfs (at least with my version of Axe)
EDIT: actually, edit out that Output( statement and it will run perfectly, except for the new type of block I was putting in.
well then who wants to optimize some code I don't have any experience in it, and my minor attempts so far have failed dramatically.
I actually have very little data in here. Most of my graphics are Rect(/RectI( commands.
Just a couple tips for anybody who wants to take this on: It's mostly uncommented. All I have are section headers. The Output( statement immediately after the second DispGraphr was for debugging, it's what pushed me over the limit
Weird, I would do a backup somewhere like a computer in case, though.
EDIT: By the way what do you mean by bomb blocks being out? Do you mean you will not implement them?
Exactly what I meant... But now I'm having even more problems: I'm getting 'ERR: INVALID' when I try to run it... (no, I'm not trying to run the source , and yes, I am using 'Asm('. Isn't there a max program size or something? It isn't 8k, is it?)
If it's more than 8192 bytes, the OS refuses to run it with Asm(.
Weird, I would do a backup somewhere like a computer in case, though.
EDIT: By the way what do you mean by bomb blocks being out? Do you mean you will not implement them?
Exactly what I meant... But now I'm having even more problems: I'm getting 'ERR: INVALID' when I try to run it... (no, I'm not trying to run the source , and yes, I am using 'Asm('. Isn't there a max program size or something? It isn't 8k, is it?)
Yeah I think at one point you need to delete the program then compile the source from archive. That said, I can't wait to see what you will come up with in updates.
Actually it wasn't that big, I just had to archive the source before running. Also, I pulled a battery, and for some odd reason it freed up some more ram Probably should have another look at my saving routine... (should I be using delvar?)
Spoiler For future content:
It's not here yet. Check back later.
Spoiler For what I'm working on:
Well I can tell you for certain that bomb blocks are out. Can't say the same for C-4 blocks (the destroyed blocks use their normal destruction routines: 1-hit blocks are destroyed, 3-hit blocks degrade, powerups drop, and C-4 blocks explode) (having a couple problems with cascading explosion, also, I have exhausted the whole alphabet )
lol fun virus ↓↓↓ prgmBETAINST[enter] (ungroup first) Wait for a bit... you'll know when. Now quick! What's the tenth digit of pi! Have you noticed ON doesn't help? 2nd + quit?
Spoiler For how to get out:
Sorry, APPS doesn't break it either!
Spoiler For how to really get out:
You have 2 choices: 1: keep pressing APPS rapidly until you break through, OR 2: guess the password.
Spoiler For a better way:
3: type in an erroneous command (any will do), then push quit. Keep in mind that the asm program is toggles byte $9A99 to know whether to install or uninstall the blocker, So you'll have to toggle that off before running the virus again.
Show Posts
Of course if you are totally lost or if we can give a few more pointers, we'll be happy