I believe today's stats aren't added to the weekly stats until after today is over.

I only could optimise a little bit, so far, so good coding! And I also noticed that this is about as fast and as smooth as a Gameboy game I played one

I started to learn because I was just intrigued. I had no intention of getting as far as I have, I just wanted a fast way to make and compute algorithms. I think the first thing I wanted to do was make a prime tester, but I cannot remember. I still use my calc often to compute algorithms, but I obviously do more than that, now ♥

In any event, it is very likely not the fault of the OS or the program That is the best part about BASIC-- you usually have to know some really advanced stuff to make it cause a glitch or a crash

What assembly programs or apps did you run?

DJ_O used to make some pretty amazing/fast BASIC programs that could rival Axe Although generally it is slower People love the challenge of BASIC

Have you ever used Repeat loops? They are very lovely for these kinds of loops. Repeat will kepp repeating the loop until the condition is true. It does not test the condition before entering the loop (a while loop does). For example, this code will move a pixel around on the screen in a 16x16 area:
3→X
3→Y
Repeat A=45     ;Later I will store the key value to A. This means repeat until clear is pressed.
pxl-Test(Y,X→C
9→B
Repeat A          ;getKey will be stored to A, so this repeats until a key is pressed
B+1
If Ans>9
Then
Pxl-Change(Y,X
0
End
Ans→B
getkey→A
End
If A=105     ;Enter
1→C
If A=23       ;Delete
0→C
If A=21       ;2nd
not(C→C
Pxl-Off(Y,X
If C
Pxl-On(Y,X
Y+(A=34)-(A=25
If Ans<0
15
If Ans>15
0
Ans→Y
X+(A=26)-(A=24
If Ans<0
15
If Ans>15
0
Ans→X
End
I may have mistyped something, but that should give you an idea of how to make things work
You can press clear to exit, 2nd to invert the pixel, Enter to turn the pixel on, and Del to turn the pixel off.

EDIT: I love Repeat loops I actually learned them long before I understood While loops. It think this is more useful...

I was using DelMem inside a parser hook and directly after that, I tried finding the updated position of a program. For some reason, bcall(_CheckFindSym) returned the old pointer (even though I watched the program data get shifted down in Wabbit's debugger).

So does anybody have any insight as to why this is and how it can be fixed?

EDIT: The code:
     bcall(_DelMem)
     ld hl,9652h          ;This is the pointer to the name of a currently executing program
     rst 20h               ;Copies 9 bytes at HL to OP1
     bcall(_CheckFindSym)   ;
     inc de \ inc de
     ld hl,(965Bh)       ;start of the currently executing program
     ld (965Bh),de
     ex de,hl
     sbc hl,de
     ld de,(progPtr)     ;a pointer inside the program
     add hl,de
     ld (progPtr),hl
     ret

EDIT2: Problem fixed